Perform user comparison manually with transaction PFUD
Problem: User matching not performed
Before the project starts, it must be clear which systems are to be connected to the IdM and which services the system is to provide. This requires close collaboration between the department and IT, as later adaptations or additional systems will extend the implementation and exceed the budget. Analysing existing data To successfully implement an Identity Management System, high quality data is essential. Users' root data must be verified, updated, or maintained. Automation with incomplete or even incorrect data is otherwise not conceivable. Rethinking the Permission Concept With the introduction of an Identity Management System and a workflow for permission granting, the existing roles should be scrutinised once again. You should ask yourself whether the user knows what role he chooses from the current catalogue and whether it is sufficient for his task. Set Role-Owner Not only the user needs to know which role to choose. There must also be a person in charge of the role who adapts or adapts the role as required or acts as a point of contact when required.
In more complex system environments, thousands, if not tens of thousands, of SAP jobs can run per day. Their interdependencies create a high level of complexity. If administrators or admin teams want to maintain an overview, they have to rely on meaningful monitoring. It must be clear at all times which jobs are running and which are not, in order to ensure proper SAP operation. Ideally, one is informed of critical errors by e-mail or SMS. The trend towards internationalization, outsourcing and mixed operation with on-premise and on-demand systems means that SAP landscapes are often widely distributed. This makes monitoring more difficult and, at the same time, clarity must be maintained. Integrating SAP job management and job requests into a central system, such as SAP Solution Manager, therefore makes sense and is useful for supplementing IT service processes in a meaningful way and accelerating process flows.
People tend to forget how important this element of the architecture is. The structure associated with it often proves to be especially important for companies that want to implement the SAP system for the first time.
As a member of the SAP Basis specialist team, your responsibilities will include the design, operation, administration, support and installation of an extensive SAP system landscape with over 50 systems for 17 universities and 2 institutions in Lower Saxony. Furthermore, you will monitor the SAP system landscape as well as its interfaces to external systems and carry out measures within the scope of software lifecycle management (e.g. note maintenance, support stacks, release upgrades) and change management (e.g. hardware migration, transport system and documentation). As part of the SAP Basis team, you will be the contact person for organizational and technical questions of the universities and in 3rd-level support for user inquiries.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
The application layer is the core of an R/3 SAP Basis system.
It is precisely these challenges that are important to me, so that I can continue to learn and develop professionally on a daily basis.