What is SAP Basis Operation?
SUIM User information system
A trick often used by administrators is to allow for time buffers before starting the next job. The buffer times are necessary because it is not possible to predict exactly how long a job will take to complete, since the duration depends on many incalculable parameters. Since it makes little sense to run backups and SAP jobs at the same time, these tasks are usually done one after the other rather than in parallel. In more complex environments, data backup durations, time buffers and job runtimes add up to such an extent that the time available is no longer sufficient to perform all activities within the available time corridor. Tools that work with status dependencies and then automatically start the next job when its predecessor job has been processed without errors can help here.
IT professionals are taking the first steps in automation with the use of tools like RedHat Ansible. At our company, for example, Ansible is used for mass rollouts of agents in large environments.
Configuration
In order for Fiori applications to be displayed according to the calling users, appropriate Fiori permissions must be maintained in the PFCG. There are several points to consider. This article discusses the permissions required to launch a Fiori application. In addition, a short explanation is given, how the displayed tiles can be configured in the Fiori launchpad via reels. To run Fiori applications from the launchpad and the permission queries defined in the OData services, the corresponding Fiori permission objects must also be maintained in the PFCG. Here the start permissions for the application's OData service in the backend system as well as permission objects are relevant for the business logic of the OData services used in the application. In general, it is important to know that if Fiori is implemented correctly, permissions must be maintained in the front-end server (call Launchpad, start the tile, etc.) as well as permissions in the back-end server (call the OData services from the backend). This article explains this in more detail.
The SAP Identity Management System (IdM) enables centralised user and permission management in a heterogeneous system landscape. By using an IdMSsystem, manual processes can be replaced by automated workflows that are mapped and administered centrally. Examples of scenarios: 1) User and Authorisation Management 2) ESS/MSS for the management of personnel data 3) Audit and monitoring for the verification of compliance with legal regulations What should be taken into account, however, if you want to introduce an Identity Management System? In this contribution, I would like to highlight fundamental points that need to be clarified before the introduction.
"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.
Some useful tips about SAP basis can be found on www.sap-corner.de.
This means that the values for abap/heap_area_dia, abap/heap_area_nondia, ztta/roll_extension_dia and ztta/roll_extension_nondia can be set dynamically here.
A self-service application may be made with a justification and a period for allocating special rights.