GADOS: THE W-Questions in the World of SAP Authorizations
The authorizations for SAP products such as SAP S/4HANA are often perceived as a complex subject – a perception which, in terms of the technical aspects that need to be considered, is not entirely unjustified. On an abstract level, however, the topic can be presented and explained very easily with the help of the GADOS principle.
| GADOS |
|---|
| Grouping of users |
| Application scope |
| Differentiation of access |
| Organizational structures |
| Software solutions and methodology |
The acronym GADOS stands for the 5 dimensions that are of central importance when implementing SAP authorization concepts. The GADOS principle makes no claim to completeness and does not cover this topic completely, given that it only considers elementary core aspects in order to derive the relevant fields of action. This diminishing and the associated exclusion of technical complexities create a generally understandable and vendor-independent basis for addressing general challenges in the planning and implementation of SAP authorization projects. Essentially, the GADOS principle can be reduced to the following central question.
«Which user (WHO? User grouping) needs which applications (WHAT? Application scope) with which restrictions (HOW? Differentiation of access) for which areas (WHERE? Organizational structures) and with which tools (WITH WHAT? Software solutions and methodology) can these core topics be handled in SAP authorization projects as efficiently and purposefully as possible?»
As an abstract orientation guide, the GADOS principle thus creates a common and uniform understanding of the tasks and issues to be solved when implementing SAP authorization concepts (see Figure 1). With the XAMS (Xiting Authorizations Management Suite) software solution and the associated project methodology, we act as an anchor point and contribute to the successful implementation of SAP authorization projects on both a conceptual and a technical level. We are aware that a good software solution with all its functions is no guarantee for a successful project implementation. That is why we are consciously addressing this topic and offering appropriate assistance through the XAMS, in order to make sure that all tool functions and application scenarios are used as intended, in the correct order and in a methodically correct manner.
Guided Procedures: The XAMS Compass for the World of SAP Authorizations
More specifically, our approaches to the implementation of SAP authorization projects are documented in detail within the XAMS. In addition to tools and technical documentation, we also provide our customers with the necessary knowledge to implement SAP authorization projects methodically, based on the tried-and-tested procedure we recommend (Best-Practice approach). Through our main menu (transaction: /n/XITING/ALL), customers can access these project guidelines, which are referred to as “Guided Procedures” in XAMS. With the help of the Guided Procedures, we ensure that the project is implemented in a structured and goal-oriented manner by dividing the overall project into appropriate project phases and work packages and so that work steps are not carried out in a haphazard and random way. In terms of project management, the specified structure consisting of project phases and work packages represents the operational framework for the project and the basis for carrying out a reliable cost estimate, which is essential for the project budgeting and helps to determine the time and the associated resources required for the project.
For the configuration of the XAMS functions, such as our productive test simulation (PTS), we already have numerous guided procedures which accelerate and facilitate the project implementation. With this project approach, we draw a distinction between Guided Procedures for redesigning the SAP authorizations for dialog users (redesign/initial implementation), Guided Procedures for the optimization of the RFC interface architecture and Guided Procedures for the S/4HANA authorization migration (Brownfield and Greenfield). The project-specific guidelines guide authorization administrators step by step through the upcoming work steps of the respective project phase. The guidelines do not only refer to the activities to be carried out, but also provide important explanations and recommendations as well as references to relevant SAP notes and standard tools in order to ensure a standard-compliant and sustainable implementation of the SAP authorization concept. If a work package is in progress or has been completed, this can be specified via the integrated status management in order to document the general project progress accordingly (see Figure 3).
In addition, we can offer our customers, if required, additional training activities, such as the Best Practice Workshop (BPW) and make the transfer of knowledge to our customers even more targeted and interactive.
Conclustion: The difference between software product and software solution
The XAMS is not only a powerful software product with numerous functions, which enables a more efficient SAP authorization management during projects or operation, but is rather a holistic framework which, apart from sophisticated tools, also considers methodological aspects and knowledge management as important elements of a holistic software solution, unleashing the full potential of technology and people. Contact us to learn more about our field-tested solutions!
- About the complexity of authorization management in SAP Fiori - 26. July 2022
- GADOS: THE W-Questions in the World of SAP Authorizations - 2. March 2022
- Next Generation Role Testing – Reduce Time and Effort with Xiting Times - 29. January 2018
