SAP Authorizations SAP Authorizations - Overview HCM Authorization Concepts - SAP Stuff

Direkt zum Seiteninhalt
SAP Authorizations - Overview HCM Authorization Concepts
Using suggestion values and how to upgrade
Standard permissions required for a functionally fully descriptive role should be maintained accordingly. It is recommended to disable and not delete unneeded permissions, or even entire permission branches. Permissions that have been set to Inactive status are not reinstated as new permissions in the permission tree when they are reshuffled, and those permissions are not included in the profile generation process, and thus are not assigned to a role in the underlying profile.

It must be clarified in advance what constitutes a recognized "emergency" in the first place and which scenarios do not yet justify activating the highly privileged user. In addition, it may only be approved and activated after a justified request and only under the dual control principle. After use, it must be administratively blocked again immediately.
Generic access to tables
Each UI component that can be clicked corresponds to an external service that must each have permission set up. UI components also include creating or calling stored searches or navigating from one record directly to another record, such as calling an appointment directly from a business partner; This corresponds to cross-navigation. All navigation options in the form of external services are defined in the customising of the CRM business role in the form of a generic outbound plug mapping to the navigation bar. Outbound Plugs (OP) define what happens when a user leaves a view in SAP CRM. Here the customising is set for scenarios that do not necessarily fit all CRM business roles. The corresponding CRM business roles have been configured to be associated with outbound plugs that are not required for the respective CRM business role scenario. This explains the large number of external services in the role menu.

"Shortcut for SAP systems" is a tool that enables the assignment of authorizations even if the IdM system fails.

You can also find some useful tips from practice on the subject of SAP authorizations on the page "www.sap-corner.de".

The password of the user can be set and synchronised via the transaction SWU3.

SAP Stuff
Zurück zum Seiteninhalt