SAP Basis Attach Transport Order to Queue - SAP Stuff

The support packages were successfully fed into a system (test or development system). You performed the modification synchronisation. Procedure Load the support packages into the next system (quality or production system). You must distinguish between the following cases: Their systems have a common transport directory: Release Level 3.x: If the *.ATT files are not present, run RSEPSDOL in the source system and then RSEPSUPL in the target system. If the *.ATT files are present, run only RSEPSUPL in the target system. Release level 4.x: Select SPAM Support Package Upload in the target system. Your systems do not have a common transport directory: Release Level 3.x: Run RSEPSDOL in the source system to create the *.ATT files if they do not already exist. With ftp, transfer all files with the *.PAT extension in binary mode and all files with the *.ATT extension in ASCII mode from the /usr/sap/trans/EPS/in directory (UNIX and AS/400) or :\usr\sap\trans\EPS\in (Windows NT) of the source system to the target system transport directory. Run RSEPSUPL in the target system. Release level 4.x: With ftp in binary mode, transfer all files with the *.PAT extension from the source system's /usr/sap/trans/EPS/in (UNIX and AS/400) or :\usr\sap\trans\EPS\in (Windows NT) directory to the target system's transport directory. Select SPAM Support Package Upload in the target system. Play the Support Packages as usual. Import the Modification Balance Transport. Steps of the SPAM The SAP Patch Manager informs you about the step in progress in the status bar. If you want to know what steps are being performed for which scenario, run RSSPAM10.