Show TOC

 Process of the Test Procedures

Call Parameters

The test procedures check is called up using the following parameters:

LEVEL

Authorization Level

TCLAS

Transaction Class = Difference Personnel Number/Applicant Number

PERNR

Personnel Number

INFTY

Infotype

SUBTY

Subtype

BEGDA

Start Date of Infotype Record To Be Checked

Process Flow

The system performs all the following steps of the test procedures check.

  • The APPRO authorization main switch is evaluated If the main switch is not activated, the authorization check returns authorized immediately.

  • LEVEL is evaluated. If the check is for read access (authorization level R or. M ), the authorization check returns authorized immediately.

  • The check establishes which object the user should be authorized to access:

If the check is for access to an applicant number or to the Organizational Assignment infotype (0001), the authorization check returns authorized immediately.

If the check is for access to the Test Procedures infotype (0130), the following steps are carried out:

  • The date after which changes are permitted is determined. This date is taken as the maximum.

  • If the check is for access to one of the different Test Procedures infotypes, the following steps are carried out:

All the test procedures that are relevant for the infotype (from the T584A table ( Test Procedures – Infotype Assignment )) are determined:

  • If no test procedures are found, the authorization check returns authorized immediately.

  • If test procedures are found, the date after which changes are permitted is determined for each test procedure (that is, for each subtype of infotype 0130). See also Flowchart 8 ):

  1. The maximum of the dates that have just been defined is determined.

  2. The authorization check then establishes whether the start date of the infotype record ( BEGDA ) is after the maximum determined by the system in the previous step:

  • If the date is after the maximum, the authorization check returns authorized .

  • If the date is before the maximum, the authorization check returns not authorized .

Note Note

Applicant numbers are excluded from the test procedures for the following reason: The test procedures were developed for decentralized entry scenarios such as decentralized time evaluation where users evaluate time data outside the HR department. The HR department is only involved in checking the data. In this scenario, the test procedures should prevent other users from being able to change data outside the HR department after it has already been checked. Since applicant data is generally not changed outside of the HR department, such scenarios do not normally occur and are therefore not supported.

Similar arguments could be put forward for the exclusion of the Organizational Assignment infotype (0001) from the Test Procedures. The real reason for excluding this infotype is the special function that it has in the authorization check. Since the Organizational Assignment infotype (0001) controls the periods of responsibility for other infotypes and in particular for the Test Procedures infotype (0130), test procedures on the 0001 infotype often cause complications in the authorization check. The 0001 infotype has therefore been excluded intentionally from the test procedures to avoid this.

End of the note.

See also:

The process flow of the test procedures in Flowchart 7

Process of Determining the Date After Which Changes Are Permitted for Test Procedures