8/11/2019 Step-By-Step Process of Importing Support Packages Into ECC6 EHP4 System _ SAP Basis Netweaver http://slidepdf.com/reader/full/step-by-step-process-of-importing-support-packages-into-ecc6-ehp4-system- 1/19 8/11/2014 Step- by- Step pr ocess of Impor ti ng Suppor t Packag es into EC C6 EH P4 System | S AP Basi s N etweaver http://s apbas is netweaver.wor dpr ess .com/2011/09/26/step- by- step- pr oces s- of- impor ti ng - suppor t- packag es- into- ec c6- ehp4- system/ 1/19 Posted by Murtuza SAP Basis Netweaver All about SAP Basis projects & administration Step-by-Step process of Importing Support Packages into ECC6 EHP4 System SEP 26 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 i mportant 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). Ano ther point I want to highlight is in this scenario, we are simply updating a subset of Support pac kages i.e HR support packages and not the Support Pack ‘Stack’. Whilst it is recom mended to app ly the stack, this is not always practical and feasible due to resources, availability to test and other com plexities in large SAP landscapes. 1.1 Check all pre-requisites are met, e.g file system space, S AP 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)
Transcript
8/11/2019 Step-By-Step Process of Importing Support Packages Into ECC6 EHP4 System _ SAP Basis Netweaver
Step-by-Step process of Importing SupportPackages into ECC6 EHP4 System
SEP 26
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 i mportant 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 (seeappendix). 99% Preparation, 1% perspiration!
Remember you can only download SP’s from Solution manager (well sort of). What SolMan reallydoes is generate the link for you to download the SPs. Once you have the link generated, you can justcall 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 Supportpackages i.e HR support packages and not the Support Pack ‘Stack’. Whilst it is recom mended toapp ly the stack, this is not always practical and feasible due to resources, availability to test and othercomplexities in large SAP landscapes.
1.1 Check all pre-requisites are met, e.g file system space, S AP 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 SAPMarketplace and have been unzipped/uncarred into the …./EPS/in folders.The process of identifying which SP’s to load and the interdependencies isa 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 *.SAPCARfiles and extract it in …usr/sap/trans/EPS/in
1.5 Define Queue. – Essentially what you are doing here is telling SAPwhich SPs you want to import. It is intelligent enough to calculateinterdependencies.
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 areimporting SP for different modules e.g HR, Finance, etc, then you may need to build the queue andchange the settings to “Calculation for a Vector of components”.
Queue calculation for a vector of software components:
These are the various phases the SPAM goes through during the import process. You will see thephases change in the ‘Status’ section in tcode SPAM:
reparation Module
…
1. PROLOGUE
This phase checks whether you are authorized to import Support Packages.
2. CHECK_REQUIREMENTS
This phase checks various requirements for importing a Support Package, for example, whether thetransport control program tp can log on to your system.
3. DISASSEMBLE
This phase unpacks files from the appropriate EPS parcels and saves them to the transport directory.
4. ADD_TO_BUFFER
This phase places the queue in the transport buffer of your system.
5. MODIFY_BUFFER
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 systemchecks whether there are objects that are in open repairs and that are overwritten during the import, orwhether other conditions prevent the import of an object.
7. IMPORT_OBJECT_LIST
This phase imports the object lists for the Support Packages in the queue into the system.
8. OBJECTS_LOCKED_?
This phase checks whether there are objects that are overwritten by the import, and that are still inunreleased requests.
9. ADDON_CONFLICTS_?
This phase checks whether there are conflicts between objects in the queue and any installed add-ons.
10. SCHEDULE_RDDIMPDP
This phase schedules the transport daemon (program RDDIMPDP).
mport 1 Module
11. CREATE_VERS_BEFORE
This phase generates versions of the objects that are contained in the Support Packages in the queue (ifthis option is set).
12. SPDD_SPAU_CHECK
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 callingtransaction 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)
8/11/2019 Step-By-Step Process of Importing Support Packages Into ECC6 EHP4 System _ SAP Basis Netweaver
This phase imports program code and program texts in an inactive state.
18. DDIC_ACTIVATION
This phase activates the imported ABAP Dictionary objects.
mport 2 Module
19. IMPORT_PROPER
This phase imports all the Repository objects and table entries if they were not already imported in theINACTIVE_IMPORT phase. This is preceded by actions such as table conversion and activation of thename tabs.
20. PREPARE_XPRA
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.
23. XPRA_EXECUTION
This phase executes the XPRAs and after-import methods.
24. ABAP_GENERATION
This phase generates the runtime objects for the imported Repository objects (ABAP source texts andscreens).
Clean Up Module
25. RUN_SPAU_?
This phase prompts you to adjust your modifications to Repository objects by calling transactionSPAU.
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 processedcompletely.
8/11/2019 Step-By-Step Process of Importing Support Packages Into ECC6 EHP4 System _ SAP Basis Netweaver
After the SPDD is completed, it will go through a number of phases and eventually pause at SPAUadjustment phase (RUN_SPAU). Now again, ask the developers to continue with the SPAUadjustments (This is only done in Development systems. For changes to take place in all downstreamsystems, 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 severalhours to a week or more depending on size of landscape and amount of customising), simply resumei.e Goto Support Package -> Import Queue (similar to SPDD steps)
Finally, it all goes well, the last phase is the EPILOGUE as shown below. This should not take that longand 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.
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/testteam 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 filesystem4. 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/in5. 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 % full7. 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 areupdated 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 toproject/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 yourenvironment.
