Data modeling and extraction
Monthly reporting / reviews
As an SAP Basis administrator, you are faced with the challenge of balancing acute daily business and recurring routine tasks. As the complexity of the systems and the interdependencies tend to increase, the challenges are great and the requirements are growing. Daily and at the same time business-critical routine tasks are SAP job control and regular data backups. Automating these tasks can free up time for the day-to-day business of maintenance, servicing, support and troubleshooting. Clear monitoring and alerting in the event of an error help to maintain operational reliability and meet corporate compliance requirements.
This opens up new possibilities for SAP administration. Basic services, for example, can also be rented from SAP or obtained from an external service provider as part of managed services.
SCC8 Client export
Different events can be used to change to the new or changed role concept. Among other things, the introduction of new technologies can be used to establish, for example, the characteristics of the SME or technology architect. But also fluctuation or new hires are suitable for the conversion and establishment of the new roles. In principle, it is recommended that the new rollers be introduced and implemented successively parallel to the existing operating model.
Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
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.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
In terms of the SAP basis, the Outside-In process plays an essential role in generating ideas within the framework of the Open Innovation approach.
For storage management alone, there are 20 different parameters that can be changed at different points in the SAP system.