Example: Periods of Responsibility and Time Logic
An employee is transferred from personnel area A to personnel area B.
Move Date: Date of transfer in infotype 0001 for the employee (the responsible administrator then changes).
Period of responsibility: If an employee has within a specific period one or more organizational assignments for which the administrator is responsible based on his or her authorization profile, the entire validity period for the organizational assignments is defined as the period of responsibility.
If an administrator accesses the infotype data for a person (employee or candidate), the system reads the organizational assignment and the work area (infotype, subtype, and authorization level).
Note
See also the documentation for the authorization objects P_ORGIN (HR: Master Data) and P_ORGXX (HR: Master Data – Extended Check) .
Each infotype usually has different records with different validity periods. In a specific period, an employee can have different organizational assignments (infotype 0001:
Organizational Assignment
).
If different administrators (users) are responsible for these organizational assignments, this is taken into account when checking the authorization for a specific validity period of the infotype.
If the field for the access authorization VALDT is set to SPACE in the table T582A , then an administrator has access to all past, present, and future infotype records for this person if the administrator’s authorization profile enables him or her to access this data.
If the field VALDT is set to X , then the authorization check is based on the current (system) date. This means that only the administrator who is responsible at the current time has access to the infotype data (assuming his or her authorization profile permits him or her to access this data).