SAP Support Patches Check List

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
11. Prepare one excel sheet with component list and uncarred file name.
12. Check permission on components present in EPS/in. Pat file should have owner as sidadm belongs to sapsys group.
13. Carry out any modifications done at development for same activity. Import the transports before you start import of support packages. Once started you are not allowed to do any transports and even if you try you will end with error OCS is locked by username by transaction SPAM. In this case its very difficult to apply notes or to do any changes.