1. Change Preparation
1. The ABAP support packs to be applied should be clearly defined and justified.
2. The ABAP support packs should be extracted to ‘/usr/sap/trans/EPS/in’ of the transport system related to the SAP system being patched.
1. The ABAP support packs to be applied should be clearly defined and justified.
2. The ABAP support packs should be extracted to ‘/usr/sap/trans/EPS/in’ of the transport system related to the SAP system being patched.
3. If not at the latest version, update SPAM/SAINT by Goto ->Update SPAM in transaction SPAM.. This should be determined ahead of time.
4. Confirm if the current SAP kernel and tp and R3trans versions are adequate for the support packs being applied. (You may find it service marketplace where you download the pack)
5. Confirm with the appropriate database backup team, that a good backup exists before starting.
6. There is no downtime and monitoring should be active to catch potential database and filesystem space issues.
7. If the database is Oracle, find the tablespace containing D010TAB.
In older releases of SAP use transaction DB02, click on detailed analysis, enter object name D010TAB and hit green check. Doubleclick on the object D010TAB in the list and the indexes will be shown too. To check tablespace freespace in DB02, click current sizes button in the tablespaces section.
In newer releases of SAP use transaction DB02, expand folder tree Space –> Segments, doubleclick on Detailed Analysis. Enter D010TAB in Segment field and hit green check. Choose tab ‘Table + Indexes’ in the resulting window at the right. To check tablespace freespace, expand folder tree Space –> Tablespaces, doubleclick on Overview.
a. The tablespace containing table D010TAB should have at least 4GB of free space.
b. The tablespace containing indexes for table D010TAB should have at least 4GB of free space.
c. If table D010TAB and its indexes are in the same tablespace, that tablespace should have at least 8GB of free space.
2. Change Considerations
1. The customer should have a defined test plan and be aware of the implications the support packs will bring to their SAP system.
2. Procedure valid for ABAP support packs for all SAP releases.
1. The customer should have a defined test plan and be aware of the implications the support packs will bring to their SAP system.
2. Procedure valid for ABAP support packs for all SAP releases.
3. Known Complications
Check for issues before applying the support packages by looking up the relevant SAP Note ‘Known problems with support packages’ by release in the SAP service marketplace. This should be done well ahead of the proposed date/time because any issues may effect the build plan.
Check for issues before applying the support packages by looking up the relevant SAP Note ‘Known problems with support packages’ by release in the SAP service marketplace. This should be done well ahead of the proposed date/time because any issues may effect the build plan.
CHANGE EXECUTION
4. Build Plan
1. Log into Client 000 with a regular userid (not SAP* or DDIC)
2. Execute transaction SPAM
3. In the menu, choose Support Package –> Load packages –> From Application server
4. Apply latest SPAM update if not already done. (see change prep step 3 above)
5. Once packages have been loaded – define a queue (Warning: you will need to check the SAP note relevant for your SAP release for appropriate queue definition. If you do not choose accordingly, you may need to restore from the last database backup and start again.)
6. Once queue has been defined – click the import queue button.
7. If a transport was provided and noted in the SR to be included with the support packs, specify it in the popup window: ‘Add modification adjustment transports to the queue’.
8. Change the start options to ‘Start in background immediately’ for all 4 phases: prep, import 1, import 2 and clean up.
9. If you get an error about ‘Open Data Extraction Requests’, check with PDL on how to proceed.
10. If you get prompted about modification adjustments (SPDD/SPAU) for SAP objects that were changed, followup with ABAP team. It is recommended to revert all changes to SAP standard. The customer’s developers and functional teams need to be informed about the list of objects. They will determine how to act on each changed object and will give notice when to continue applying the support packs.
11. Check the support pack logs for any errors. Click the logs button. Return codes 0 and 4 are ok.
12. Once all the support packs have been imported successfully, click the confirm queue button.
13. Repeat steps 5 thru 12 until all the support packs defined in the SR are completed.
14. Run transaction SGEN to regenerate programs. Choose option ‘Generate all objects in selected software components’ and select the components for which the support packs were updated.
1. Log into Client 000 with a regular userid (not SAP* or DDIC)
2. Execute transaction SPAM
3. In the menu, choose Support Package –> Load packages –> From Application server
4. Apply latest SPAM update if not already done. (see change prep step 3 above)
5. Once packages have been loaded – define a queue (Warning: you will need to check the SAP note relevant for your SAP release for appropriate queue definition. If you do not choose accordingly, you may need to restore from the last database backup and start again.)
6. Once queue has been defined – click the import queue button.
7. If a transport was provided and noted in the SR to be included with the support packs, specify it in the popup window: ‘Add modification adjustment transports to the queue’.
8. Change the start options to ‘Start in background immediately’ for all 4 phases: prep, import 1, import 2 and clean up.
9. If you get an error about ‘Open Data Extraction Requests’, check with PDL on how to proceed.
10. If you get prompted about modification adjustments (SPDD/SPAU) for SAP objects that were changed, followup with ABAP team. It is recommended to revert all changes to SAP standard. The customer’s developers and functional teams need to be informed about the list of objects. They will determine how to act on each changed object and will give notice when to continue applying the support packs.
11. Check the support pack logs for any errors. Click the logs button. Return codes 0 and 4 are ok.
12. Once all the support packs have been imported successfully, click the confirm queue button.
13. Repeat steps 5 thru 12 until all the support packs defined in the SR are completed.
14. Run transaction SGEN to regenerate programs. Choose option ‘Generate all objects in selected software components’ and select the components for which the support packs were updated.
5. Back-out Plan
In the event that problems arise which cannot be resolved, then a full system restore is required to a point in time before support packs were implemented.
In the event that problems arise which cannot be resolved, then a full system restore is required to a point in time before support packs were implemented.
6. Post-test Plan
Logon to the SAP system, run Sm51, check all application servers are up.
Run transaction SICK, which should be successful.
If system is not coming up, troubleshoot.
You may contact me know if you are getting any errors.
SAP Basis Administrator 