SAP Basis SAP Basis in the overall system - SAP Basis

Direkt zum Seiteninhalt
SAP Basis in the overall system
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.

SAP provides support packages: in SAPNet - R/3 Frontend in SAPNet - Web Frontend on Collection CDs Requirements The Change and Transport System is set up correctly. There is enough space in the transport directory (UNIX: /usr/sap/trans). You must have the permissions [page 7] for the SAP Patch Manager. You must be registered with the company 000. You must have called the transaction SPAM. You are using the latest SPAM version. Procedure Support Packages from SAPNet - R/3 Load Frontend Before loading a Support Package from SAPNet - R/3 Frontend, maintain the network parameters for logging in to the SAPNet - R/3 Frontend. Use Transaction OSSordering the desired support packages in the SAPNet - R/3 frontend. Download the requested support packages from SAPNet - R/3 Frontend into your SAPS system with Support Package. A list of support packages appears. You can select the desired support packages before loading. The uncompressed support packages are displayed in bytes. The size of the Support Package allows you to estimate the time it takes to load. Check the progress bar to see if the load was successful. To return to the SPAM entry screen, select Jump Back. Define the queue (page 17).
Schedule and execute background jobs
If you are running a multi-system landscape with a common transport directory, it is convenient to enable this option only in the first system you are inserting support packages into, and to disable it in the following systems. Since the data files no longer need to be regenerated there, this saves time when playing in. Delete data files after inserting You can specify whether the data files should be deleted after inserting the support packages. This saves disk space and is enabled in the default setting. If you are running a multi-system landscape with a common transport directory, it is convenient to disable this option, since then the data files in the other systems no longer need to be re-created (see above Regenerate data files). Execute ABAP/Dynpro generation This option determines whether the programmes and screens shipped with the support packages should be generated during the commit. Note that generation can take a long time. Without automatic generation, the programmes and dynpros are not generated until the first call. Note that this parameter can only be affected by you if the generation is allowed by SAP during the insertion of this support package. The SPAM update does not affect the generation. SPAM Settings Option SAPM Basic Setting Transmission Monitor From Scenario Standard Rebuild Data File A data file after the example. Delete Do a Generation From Use the transaction SPAM to insert Support Packages [page 8] into your system, regardless of whether the support packages come from the SAPNet - R/3 Frontend, the SAPNet - Web Frontend, or Collection CDs. Prerequisites User: It must have the appropriate permissions [page 7] for the SAP Patch Manager. He must be registered with the client 000. He must have called the transaction SPAM. Select Tools ABAP Workbench Tool Maintenance Patches or enter the transaction code SPAM.

Support Packages from SAPNet - Web Frontend or Collection CDs are available in a compressed format. Note that you must unpack the support packages before processing. Download the support packages from the SAPNet - Web Frontend or mount the appropriate CD. Log in with the following user: Operating system users UNIX adm AS/400 OFR Windows NT adm Go to the following subdirectory in your system: Operating system UNIX and AS/400 usr/sap/trans/tmp Windows NT :\usr\sap\TRANS\TMP Unzip the archive containing the support packages with the following command: Operating system command UNIX CAR -xvf ///_CAR AS/400 CAR '-xvf /QOPT///_CAR' Windows NT CAR -xvf :\\ CHIVE>.CAR Put the unpacked support packages in the EPS inbox of your transport directory: Operating system EPS-Inbox of the transport directory UNIX /usr/sap/trans/EPS/in AS/400 /usr/sap/trans/EPS/in Windows NT :\usr\sap\trans\EPS\in Now bring the support packages into your system with Support Package Upload. You will see a list of uploaded support packages that are now known with all their attributes in the SAP system and can be handled in the right way by the SAP Patch Manager. Select Back to return to the SPAM entry screen.

Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.

The principle of consistently aligning IT services with repeatable standards is thus directly linked to the standardisation of processes and technical specifications.

We support you on-site and/or remotely in all SAP system management tasks to ensure the continuous availability of SAP applications.
Zurück zum Seiteninhalt