SAP Basis SQ02 InfoSet maintenance

Direkt zum Seiteninhalt
SQ02 InfoSet maintenance
SE38 ABAP Editor
Since innovations through IoT (Internet of Things) or big data scenarios not only affect the SAP basis, but also highlight products and services for customers of their own company, the role of the SAP basis in relation to these scenarios and services must be clearly defined. In general, the SAP basis sees its responsibility here in the connectivity to the corporate network or the enterprise systems, which lie in the responsibility of the SAP basis. The support of the applications, based on the technologies as well as the associated services, is the responsibility of the respective department that offers this service. A SAP-based support service must be agreed and regulated during the conception.

In order to provide individual SAP or non-SAP developments and to link them to your SAP ERP system, we provide you with the necessary SAP NetWeaver application servers. We offer the following services in this area:

On www.sap-corner.de you will also find useful information about SAP basis.
STMS Transport Management System
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 second component of the application layer is the message server. It acts as a kind of "mediator" between the services and the applications.

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

In particular, the implementation, set-up and configuration of the systems and security concepts must be harmonised or returned to the SAP standard.

To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.


SAP Basis is responsible for the smooth operation of the SAP Basis system.
Zurück zum Seiteninhalt