What are the areas when working with SAP systems?
Creating a basis for the SAP landscape
The application servers provide the services for running SAP applications. In practice, companies usually decide to use a separate application server for each application.
Regular maintenance tasks or the standard procedures must be described and defined to build checklists based on them and to control compliance with this standard. The SAPSolution-Manager can also support this as a tool of SAP e.g. through the Guided Procedures. In this context, it is also necessary to document the functionality of an underlying application and thereby determine what testing and monitoring activities are necessary. This is a reconciliation process between the SAP basis, other IT departments and, if necessary, the business areas concerned. The defined standard and the system's IST situation must be fully documented and regularly checked for compliance. This can be done through automated monitoring, validation using tools such as SAP-LVM (Landscape Virtualisation Management) or SAP Solution Manager, as well as manual checklists. Only the regular review of the standards guarantees their compliance. It can also support the regular use of SAP services such as Go-live Checks or Early Watch. Examples of how to standardise procedures are listed here: ・ Naming of system instances and logical hosts, or at least one central registry in a directory service, or LVM or SAP customer portal ・ Centrally starting and stopping systems, such as via the LVM ・ Categorising SAP instances by T-shirt size to define profile standards and cost them.
Missing result documentation
By using a code scanner, it is now possible for every developer to scan for complex security patterns during the extended check of his program, which tell him whether he has built vulnerabilities into his program. These vulnerabilities are detected and can now be addressed in a workflow-driven process. Currently, there are two products that can support customers in the area of scanning their own SAP programs.
The website www.sap-corner.de offers many useful information about SAP basis.
The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.
The SAP Patch Manager offers two scenarios for inserting support packages or queues: Test Scenario Use the test scenario to determine whether conflicts or problems occur (e.g., unreleased repairs) or whether a modification match is necessary before the actual insertion. This scenario allows you to estimate and minimise the time and effort required to load support packages. In this scenario, no data is imported into the system, and you can continue to play in the event of an error without the error being corrected. You must select the test scenario explicitly. Note that once the test scenario has passed, the queue is empty and needs to be redefined. You must also explicitly choose the default scenario.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
For this purpose, so-called "precogs" are used, which use precognition to predict and report murders in visions before they happen.
In the SAP product world, the presentation layer is based on several modules that are grouped under the collective term SAP GUI.