Step-by-Step process of Importing Support Packages

In this blog we look at a step-by-step procedure to import HR support packages (HR Sp 16 to 20) & (EA-HR 16 to 20) into a ECC6 system with EHP4.

The most important part of the installation is the preparation work. This is absolutely critical that side-effect notes, relevant basis notes and patches are applied before applying the support packages (see appendix). 99% Preparation, 1% perspiration!

Remember you can only download SP’s from Solution manager (well sort of). What SolMan really does is generate the link for you to download the SPs. Once you have the link generated, you can just call the link from your browser independent of SolMan (see appendix on process).

Another point I want to highlight is in this scenario, we are simply updating a subset of Support packages i.e HR support packages and not the Support Pack ‘Stack’. Whilst it is recommended to apply the stack, this is not always practical and feasible due to resources, availability to test and other complexities in large SAP landscapes.

1.1       Check all pre-requisites are met, e.g file system space, SAP notes, locked users, etc. See appendix below for checklist of what to do.
1.2       Login to Client 000 with a Super User (SAP_ALL/SAP_NEW)
1.3       Ensure all the required SP’s have been downloaded from the SAP Marketplace and have been unzipped/uncarred into the …./EPS/in folders. The process of identifying which SP’s to load and the interdependencies is a separate task on its on and usually conducted in conjunction/direction of the application/functional team
1.4       Load SP’s from App server (you must first download the *.SAPCAR files and extract it in …usr/sap/trans/EPS/in
1.5       Define Queue. – Essentially what you are doing here is telling SAP which SPs you want to import. It is intelligent enough to calculate interdependencies.

Load the SP’s from the Application server (after you have unzipped them into the ../EPS/in folder). Pick the highest SP number. (It will automatically included other SP’s or dependencies.). If you are importing SP for different modules e.g HR, Finance, etc, then you may need to build the queue and change the settings to “Calculation for a Vector of components”.

Queue calculation for a vector of software components:

The Support Package queue calculation takes place for multiple software components based on the target Support Package level that has been defined for each software component (see Defining a Queue Based on Multiple Software Components).

1.6       Check SPAM settings:

You can schedule more parallel processes if you like and if you system can support. These are the typical settings I use when importing initially into a development system

Check if the SPAM settings are as follows :

Section Import queue

Create new datafile = Yes (only in DEVELOPMENT)

Delete data file after import = No

Section ABAP/Screen Generation

Generate screen = Never

1.7       Import Support Packages (Shift + F7)

This step onwards basically kicks starts the SP import process. From now onwards, there is no going back (well almost).

Please refer to link on SAP Help below for known errors during import:

Generally I Run phase 1 in ‘dialog mode’ and all other phases in ‘background’ mode

These are the various phases the SPAM goes through during the import process. You will see the phases change in the ‘Status’ section in tcode SPAM:

Preparation Module

1.      PROLOGUE

This phase checks whether you are authorized to import Support Packages.


This phase checks various requirements for importing a Support Package, for example, whether the transport control program tp can log on to your system.


This phase unpacks files from the appropriate EPS parcels and saves them to the transport directory.


This phase places the queue in the transport buffer of your system.


This phase prepares the transport buffer for correct processing of the following import phases.


This phase performs a test import for the queue with the transport control program tp. The system checks whether there are objects that are in open repairs and that are overwritten during the import, or whether other conditions prevent the import of an object.


This phase imports the object lists for the Support Packages in the queue into the system.


This phase checks whether there are objects that are overwritten by the import, and that are still in unreleased requests.


This phase checks whether there are conflicts between objects in the queue and any installed add-ons.


This phase schedules the transport daemon (program RDDIMPDP).

Import 1 Module


This phase generates versions of the objects that are contained in the Support Packages in the queue (if this option is set).


In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).

13.      DDIC_IMPORT

This phase imports all ABAP Dictionary objects in the queue.

14.      AUTO_MOD_SPDD

This phase checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.

15.      RUN_SPDD_?

In this phase, you are asked to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.

16.      LOCK_EU (only for import mode downtime-minimized)

This phase locks the development environment.

17.      INACTIVE_IMPORT (only for import mode downtime-minimized)

This phase imports program code and program texts in an inactive state.


This phase activates the imported ABAP Dictionary objects.

Import 2 Module


This phase imports all the Repository objects and table entries if they were not already imported in the INACTIVE_IMPORT phase. This is preceded by actions such as table conversion and activation of the name tabs.


This phase prepares the execution of the XPRAs and after-import methods.

21.      UNLOCK_EU (only for import mode downtime-minimized)

This phase unlocks the development environment.

22.      AUTO_MOD_SPAU

This phase checks whether modifications can be adjusted automatically.


This phase executes the XPRAs and after-import methods.


This phase generates the runtime objects for the imported Repository objects (ABAP source texts and screens).

Clean Up Module

25.      RUN_SPAU_?

This phase prompts you to adjust your modifications to Repository objects by calling transaction SPAU.

26.      CLEAR_OLD_REPORTS (only for import mode downtime-minimized)

This phase deletes the obsolete versions of program code and program texts in the database.

27.      EPILOGUE

This phase completes the import. Among other things, it checks whether the queue has been processed completely.

1.8       Main Import Phases and Actions required.

In the following steps below, I  only highlight only the main phases and the necessary actions required. Generally if you have done your homework and checked and met all prerequisites, you should a relatively smooth import process.

1.8.1       SPDD Adjustment – Handover to Developer

SPAM -> Goto -> Status – Queue to confirm adjustment to proceed to next phase

1.9       SPAU Adjustment

After the SPDD  is completed, it will go through a number of phases and eventually pause at SPAU adjustment phase (RUN_SPAU). Now again, ask the developers to continue with the SPAU adjustments (This is only done in Development systems. For changes to take place in all downstream systems, transports are created and imported into e.g QA and PROD and usually after the SP’s are applied).

Once developers complete their SPAU adjustments successfully (be patience, this can take from several hours to a week or more depending on size of landscape and amount of customising), simply resume i.e Goto  Support Package -> Import Queue (similar to SPDD steps)

1.10       Tail end – EPILOGUE

Finally, it all goes well, the last phase is the EPILOGUE as shown below. This should not take that long and once completed, you proceed to confirm (or complete) the import with the next step

Once EPILOGUE completed, the Status will turn Yellow. You must then go to Support Packages -> Confirm (Shift F6) to close off or complete the SP implementation.

1.11       Lastly, CONFIRM queue

Method to confirm queue shown below.

2         Post Steps – SGEN

Once import is completed, proceed to run SGEN to recompile all the new imported objects before releasing the system. Steps shown below.

Run SGEN with options

Regeneration of existing loads

Only generate objects with invalid loads

Wait until finished !

Appendix  – Additional Info

2.1       Checklist before Import of SPs

This is my checklist but others may have more to add (or remove!)

  1. Confirm and sign-off the support pks and combination of SPs that will be applied and project/test team available for testing
  2. Verify all functional and cross-system dependencies are met. Must review and OSS note 822379 (netweaver 7 version)
  3. Enough Disk space and atleast 85% free space on sapdata filesystem
  4. Check if file system /usr/sap/trans/data and ../EPS/in  has free space, if not clean-up old support package data files or Pat files in EPS/in
  5. Post a system message & a login screen message indicating the outage (refer to procedure Applying Support Packages).
  6. Check if no tablespace is over 85 % full
  7. Verify if you have a recent backup., if not schedule a full on-line backup. If production, have a backup just before Support pkgs to be safe.
  8. Unpack all required SP’s and then load them into SPAM and verify that all queues are OK  e.g SAPCAR -xvf /sapcd/sp/XXXXXXX.CAR –V

9. Update Spam with latest version from Service marketplace. Also ensure binaries R3trans and tp are updated if necessary. If you are not sure, usually it will not hurt to update these anyway.

10. Define Queue and perform TEST import and report any SPDD/SPAU conflicts to project/developers

2.2       Using SolMan to download Support Packages

Call tcode  /nsolution Manager

Select the Solution ‘SAP Solution’ if you are going to download SP’s for ECC 6.0 SAP System for your environment.

Create a new ‘Maintenance Optimizer’ or use existing

Here you can select the SP’s to download either manually and automate i.e Let SAP decide

A Web browser window will pop up and you need to manually look for and select the e.g HR support pkgs.


SAP JVM Switch with Screenshot

Starting october 1st 2012, SAP JVM 4 will be the only  supported option for SAP Web Application Server 6.40 and SAP NW 7.0 system. Therefore, we are advisable to perform the switch from 3rd party vendor JVM to SAP JVM 4.

 I believe many customers out there still reluctant to carry on the switch, due to unknown impact after the switch. Hereby, content of this blog will show how easy  the switch is and 99% of the tasks are automated.

 Reference Notes:

Note 1665953 – SAP JVM Switch Tool Composite Note

Note 1442124 – How to download a SAP JVM patch from the SMP

Note 1367498 – SAP JVM installation prerequisites

Note 1603093 – SAP JVM 4.1 parameters NetWeaver 2004 and 7.0

Note 1649026 – SAP JVM Switch tool: Configuring Replication using sapcpe

Step 1 :

 Download the latest SAP JVM Switch tool from:

SAP Technology Components -> SAP JVM 4.1 -> SAP JVM SWITCH TOOL 1.0 -> Support Package Patches -> <OS version> -> and download the latest level

 Currrent level – SAPJVMSWITCH00P_8-20008217.SAR

 and SAP JVM 4 from:

SAP Technology Components -> SAP JVM 4.1-> Support Package Patches -> <OS version> -> and download the latest level

 Current level – SAPJVM4_20-10009718.SAR

 Download the Guide from: -> SAP JVM Switch Tool -><OS version>

 Step 2 :

 Extract SAPJVMSWITCH00P_8-20008217.SAR into a temporary folder. As SIDadm, check the JAVA_HOME env.

 eg: JAVA_HOME=/opt/IBMJava2-amd64-142

Step 3 :

 Launch sapinst from the extracted folder as ROOT.

 Step 4:


i) enter your profile directory


ii) point to the location where you’ve download SAPJVM4_20-10009718.SAR


iii) enter the path to JCE_SAPCRYTO




Verify with Note 1603093 – SAP JVM 4.1 parameters NetWeaver 2004 and 7.0 and you can insert all the necessary JVM parameter here.


eg: add -XX:+UseTLAB for Server Node according to the note. Besides that, you can change and adjust the heap memory here for Server and Dispatcher Node.





v) SAPINST start running and performing the task:



vi) Below message appears after 3-5mins. Restart you SAP instance to complete the JVM switch.



vii) Check JAVA_HOME after instance restarted and it should returns as below:




viii) Open java url:: http://host:5XX00 -> system info and you’ll see version is changed to 4.1.020 for both dispatcher and server.




FYI, the whole process and downtime is less than 10 mins. Everything is so easy and automated, what you need to do is just restarting SAP instance for the switch to take effect. Besides that, if you hit any unexpected error (very rare case) you can still revert back to your previous partner vendor JVM by following the instruction in file switchJDK.txt, located in sapinst_instdir.


Please take note you need to perform additional preparation steps for Heterogeneous Systems. Please refer to SAP JVM Switch guide for detailed steps.

SMLT Language Installation

Language Installation in SAP with SMLT

Steps to install extra languages in to a SAP system.

1. Download Language DVD from SAP Service Market Place suitable to your SAP ECC version(e.g SAP 4.7, ECC 6.0 etc)

2.Place .PAT files to EPS/in folder.


3.Login to SAP in client 000 with Admin user.

4. Execute SE38

5. Execute program RSCPINST

6.Add an entry for the language you are willing to install.

7. Execute transaction SMLT

8. Create a new entry in SMLT for the required language. Give Supplementation language as English.

9.Click on the Import Language/Package symbol next to newly created entry for your language.

10.Default path is set to EPS/in folder, where it will search for the .PAT file required.

11.Found language should show either Green or Yellow button. If it is showing Red button it means you have downloaded the wrong source. Double check on SAP Service Market Place and download the right source files.

12. Press Execute to install the selected Language.

13.Monitor the import process in SM37 and Import transport logs.

14.Once installation get finished go to SE38, execute RSCPINST.

15. Click on Simulate button and copy new value for parameter zcsa/installed_languages.

16.Go back and activate the settings.

17. Go to RZ10 and change instance profile.Add new parameter zcsa/installed_languages and set its value as suggested in point 15 above.

18.Restart the SAP instance and try login with new Language.

19. Go to SE38


Select the newly installed language and press OK

It will show you the support packages whose language parts you want to import.

20. GO to Next screen.

Copy the PAR or CAR files to EPS/in folder for all support packages showing in RED.

This will import the language specific parts of those support packages.


Press Import Language Data and Overwrite.

It will show you the message “The Support Package Language Data was imported correctly.All system languages are up to date.

21. Next step is to copy the client specific data to required client.

Login to yr non default client or product client.


Go to SE38 and execute RSREFILL.

22. Refference Language EN

Language to be updated Newly installed one

Update Mode I

Log Directory sapmnttrans*.snd

23. Go to SE38


Select your language from drop down

Press Client Maintenance with Customizing Translations


  • The central instance is a concept that is unique to SAP. The central instance is a combination of hardware and software. It contains a physical server (the application server) and numerous software components, including a message server, a database gateway (a pre-established connection between SAP and Oracle–or another database), and various update, enqueue, dialog, and spool facility software.
  • In most generic SAP architectures, there are numerous application servers but only a single central instance. However, in addition to managing the SAP interfaces, the central instance can also serve as an application server

Basis people should be know the following topics:

Introduction to the R/3 Basis System:

Architecture/System landscape.
R/3 Client/Server Architecture.
Instance Concept
Central and Distributed Instances.
Work Process Overview.
Interaction between Work Processes.
Application Services.
Data Structure of SAP.
Client Concept
System Landscapes.
Oracle Directory Structure.
R/3 Directory Structure.

The System Kernel:

Principal Architecture of the SAP Web Application Server
WP Multiplexing
Dialog Processing in the SAP System
Communication with the Database
The SAP Transaction
Lock Management in SAP
Update Processing


Installation & Setup Of R/3 System:


Installation Checks.
Preparing for the Installation of SAP ERP Central
Installation of SAP License
Post Installation Steps.

SAP Profiles:

Different SAP Profiles.
Editing Profiles.
Creating New Profile Versions.
Imp Profile parameters

Starting and Stopping the R/3 System:

Starting the R/3 System.
Stoping R/3 system.
Command Prompt Start and Start.
Configuring the SAPLOGON.
Log and trace
Group Selection.
Troubleshoting Startup.

User Administration:

Displaying and Creating Users.
Copying, Deleting, and Changing Users.
Authorization Profile.
User Overview SM04.


Types of users
Authorization Concept
Authorization Check
Authorization Objects
Maintaning Authorizations
Role and Profiles

Operation Modes:

The Function of Operation Modes.
Redistributing Work Processes for Operation Modes.
Checking Operation Mode Changeovers.

Printing in the R/3 System:

The Spool Work Process.
Creating a New Printer.
Changing a Printer.
Access Methods in the R/3 System.
Spool Request Administration.

Background Jobs:

Scheduling Background Jobs.
Start Conditions of a Job
Status of a Job
Executing Programs as Job Steps
Checking Background Jobs.
Canceling, Changing, and Deleting Background Jobs.

DB Administration:

Using DB Calendar
Scheduling Backups.
Checking Backups.
Database Consistency Check.
All DB Administration Tasks

CTS & Transport System:

Types of Adaptation
Setting up an R/3 Transport Landscape
Configuring Transport Routes
Transport Process
Performing and Checking Transports

Client Tools:

Creating and deleting a client
Local Client Copy
Remote Client Copy
Transporting a client
Client Change Options


Monitoring Concept and Alert Monitor
Monitoring Architecture Terminology
The Alert Monitor (RZ20)
Monitoring: R/3 Servers and Instances
Monitoring: R/3 Users
Monitoring: Workload Analysis
Monitoring: Buffers
Database Monitoring

Setting Up Remote Connections:

Fundamentals and Types of RFC
Setting Up RFC Connections

Support Packages:

Importing Support Packages
Updating the Tools
Importing SAP Notes

SAP Memory Management:

Memory Areas
SAP Memory Allocation
Implementation of SAP Extended Memory

SAP Table Buffering:

Introduction to Table Buffering in SAP Systems
Analyzing Table Buffering