The determination of the period of responsibility is called up using the following parameters:
LEVEL |
Authorization Level |
TCLAS |
Transaction Class = Difference Personnel Number/Applicant Number |
PERNR |
Personnel Number (or Applicant Number) |
INFTY |
Infotype |
SUBTY |
Subtype |
The system performs all the following steps of this process.
The organizational assignments of the personnel number are determined (data records of the
Organizational Assignment
infotype (0001)).
The following steps are carried out for each organizational assignment (data record of infotype 0001):
An authorization check for P_ORGIN is performed: If there is no authorization, the validity period of the organizational assignment does not belong to the user’s period of responsibility.
An authorization check for P_ORGXX is performed: If there is no authorization, the validity period of the organizational assignment does not belong to the user’s period of responsibility.
An authorization check for the customer-specific authorization object, P_NNNNN , is performed: If there is no authorization, the validity period of the organizational assignment does not belong to the user’s period of responsibility.
If all the authorization checks run successfully, the validity period of the organizational assignment is added to the user’s period of responsibility.
When all the organizational assignments of the personnel number have been evaluated, the period of responsibility is returned.
If the period of responsibility is empty,
not authorized
is returned as the result. Otherwise, the result is
authorized
.
Note
For applicant numbers ( TCLAS = B ), P_APPL is checked instead of P_ORGIN, P_ORGXX, and the customer-specific authorization object P_NNNNN.
See also:
Flowchart of the Authorization Check Using P_ORGIN, P_ORGXX and P_NNNNN