SAP monitoring
What has changed in the past decade and what can we expect in the coming decade? How will they affect the requirements profile of SAP Basis experts and how can they adapt to them?
Customers with such a case regularly contact us. Creating a Permission Concept from the ground up is often a time-consuming task. Furthermore, the know-how, which aspects should be dealt with in an authorisation concept and how the corresponding processes can look practical and at the same time audit-proof is often lacking. Our solution: tool-based generation of an individual, written authorisation concept In this situation, we have recommended to our customers the tool-based generation of a written authorisation concept directly from the SAP system. We use the XAMS Security Architect tool, with which we have had good experiences. This includes a template for a revision-proof and comprehensible, written authorisation concept. It includes established best practices for role and entitlement management. The template covers all relevant areas in a permission concept. The included text of the authorisation concept is completely customisable, so that the concept can be tailored to your situation without creating a permission concept from scratch. Dynamically update the written authorisation concept One of the biggest challenges after the development of an authorisation concept is to keep it up to date in the long term and to measure the sustainable implementation in the system. This is achieved by integrating live data such as configuration settings and defined rules directly from the connected system. For example, lists of existing roles or user groups and tables are read from the system each time the document is generated and updated in the permission concept. The following screenshot shows an example of what the appearance in the concept document might look like. Automatically check and monitor compliance with the concept To check compliance with the concept, the XAMS Security Architect includes extensive inspection tools. These cover the rules formulated in the concept and are suitable for measuring the extent to which the reality in the system meets the requirements formulated in the concept.
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.
To transport rejected transport jobs in the SAP system
ITIL stands for The IT Infrastructure Library. ITIL is a summary of "best practices" rules for professional implementation of IT service management. ITIL has established itself as an international standard in the area of IT business processes. The ITIL set of rules describes the processes, the organizational structure and the tools required for IT infrastructure. ITIL is based on the economic added value that IT operations provide for the company. itSMF Deutschland eV has further developed and improved these standards, and at the same time operates a portal for exchanging knowledge and experience.
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).
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
The following table helps you fill in: Field Description I_LOGSYS The logical name of the source system.
The transaction looks like a piece of the puzzle.