SAP Basis Call SPAM - SAP Basis

Direkt zum Seiteninhalt
Call SPAM
Creation and implementation of the milieu according to the best SAP practices
SAP Basis ensures smooth operation of the SAP Basis system. The SAP Basis system is a kind of operating system of the R/3 system or SAP ERP. It includes three layers: database, application and presentation. In addition, Basis includes many SAP middleware programs and administration tools. With Basis SAP applications can be used compatible and independent of operating system and database and can be enriched with the necessary data.

In addition to purely administrative tasks, SAP administrators are also responsible for communication tasks. They work with the company's internal support services to find ways to help users solve and avoid problems and pitfalls they may encounter when using SAP solutions. For internal purposes, the SAP administrator also prepares documentation to look for errors and try to address the root causes. If necessary, he communicates with the company's decision makers so that improvements, adjustments and optimizations can be made to the SAP software.
Define Tasks and Systems
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).

In the following dialogue, select a TADIR service and the programme ID "R3TR" and the object type "IWSG". Now you can select the OData service stored on the front-end gateway. Then switch to the Permissions tab to generate the current profile of the permission objects with the new Fiori permission. Once you have performed these steps, the treated role has the necessary permissions on the front-end side. Fiori Permission to call the OData service on the backend server Now go to the role maintenance in the PFCG on the backend server. Open the appropriate role in Change Mode. Now you can repeat the steps for the frontend as explained above. However, when selecting the TADIR service as the permission proposal, you now select the object type "IWSV". Here you can select the OData service of the specific Fiori application stored in the backend.

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

After the tasks have been completed, the user is deprived of the rights.

STEP 1: DEFINITION OF PERFORMANCE This step deals with the description of the services to be offered.
SAP BASIS
Zurück zum Seiteninhalt