OTHER SERVICES
SU21 Maintenance of authorization objects
At the same time, there is a need to return the solutions to the SAP standard. A collaborative approach between departments and IT technology is required to assess IT technical and business benefits. It is also necessary to check whether the adaptation of business processes to avoid modifications to the implementation may be more effective and therefore more cost-effective. This must be evaluated and decided jointly. As a result, we recommend defining and implementing business standards for creating and maintaining solutions.
You trust in the availability of your SAP systems. Our specialists are happy to support your team in all phases of your SAP projects. We support your SAP HANA systems. And stand by your side during a platform or release upgrade.
Operation of your ERP landscape on SAP on HANA
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.
Job scheduling: your system needs to run various automatic background jobs that consume resources. Your administrator must carefully schedule these tasks when user demand is low so they don't impact performance.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
DISASSEMBLE In this step, the data files are unpacked from the corresponding EPS packages and placed in the transport directory.
Job scheduling: your system needs to run various automated background jobs that consume resources.