The DI, DR, ID, IL, IO, IP, PI, PR, RD, RL, RO, RP approval procedures are used to determine the approvers through the application roles for role approvers and role approvers (IT). These application roles can to assigned to hierarchical roles (departments, locations, cost centers, business roles). If no application role is assigned to the hierarchical role or this application role has no members, the approvers are determined according to the following principle.
Example: Determine the approvers using the RD approval procedure (Role approvers of the recipient's primary department)
-
This determines the request recipient's primary department (UID_Department).
-
The application role (UID_AERole) is determined through the department’s role approver (UID_RulerContainer).
-
Determine the secondary identities assigned to this application role. These can issue approval.
-
If there is no approver given for the primary department or the application role has no members, the approver of the parent department is used.
-
If no approver with members can be determined right up to the top department, the request cannot be decided.
NOTE: When approvers are determined using the approval procedures RO or IO, and inheritance for business roles is defined from the bottom up, the following applies:
If no role approver is given for the primary business role, the role approver is determined from the child business role.