SAP Basis SCC1 Client copy - SAP Basis

Direkt zum Seiteninhalt
SCC1 Client copy
SPAM: Run Modification Synchronisation
For the SAP basis and its employees, the change in self-understanding results in an attractive, responsible and demanding working environment. Technological diversity can be controlled and kept to the minimum necessary. This includes an overview of the existing interfaces and a controllable data flow with the associated guarantee of data security.

An SAP administrator has the task of controlling a company's SAP system and ensuring its proper functioning. He/she maintains and monitors SAP applications and is also responsible for their development.
SM66 Work processes of all instances
In the initial screen, you can first use the global settings to specify whether changes should be allowed in general. Furthermore, you can define specifically for the software components and namespaces of the Repository objects whether they can be changed at all, or whether changeability should be restricted.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.

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.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.

ITIL has established itself as an international standard in the area of IT business processes.

SPDD_SPAU_CHECK This step will check if a modification match (transactions SPDD/SPAU) is necessary.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
SAP BASIS
Zurück zum Seiteninhalt