SAP Enhancements
Concept, planning and execution transports
In this step, a dialogue box prompts you to confirm the commit. If the user does not have permission to execute the transaction SPAM or the current queue has not yet been confirmed, the transaction stops SPAM with a message to that effect. CHECK_REQUIREMENTS In this step, different requirements for inserting are checked. There are the following reason that may cause this step to be cancelled: TP_CANNOT_CONNECT_TO_SYSTEM: tp cannot log in to the system database. QUEUE_NOT_EMPTY: There are incomplete OCS jobs in the tp buffer. You can view these jobs using the following tp command: tp SHOWBUFFER -D SOURCESYSTEMS= TAG=SPAM You cannot resume the processing of the queue until these jobs have been completely processed or deleted from the tp buffer. DISASSEMBLE In this step, files are extracted from the corresponding OCS files and placed in the /usr/sap/trans/data (UNIX) directory.
The core component of SAP Basis is the application layer. It contains one or more application servers and a message server.
Workflow
There are the following reasons that may lead to the termination of this step: CANNOT_SKIP_ATTRIBUTE_RECORD: The attributes cannot be read in the OCS file. The file probably cannot be opened for reading because it has been deleted in the meantime, or the permissions at the operating system level are insufficient. CANNOT_DETERMINE_EPS_PARCEL: The OCS file does not exist in the EPS inbox; presumably it was deleted.
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.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
Customise the Organisation Levels Now go to the "Menu" tab.
An SAP expert is always familiar with the latest technologies.