Show TOC

 Test Procedures

Use

You can use the test procedures to create test data for specified infotypes.

Integration

The test procedures are similar to the asymmetrical double verification principle. The difference is that the entered data is payroll-relevant even if it has not yet been checked. It can, however, only be changed after a successful authorization check by a user with special authorization.

Features

This control mechanism functions as follows: You can specify a test procedure for the given infotype (or subtype) in the T584A and V_T584A tables ( Test Procedures – Infotype Assignment ). For infotypes without subtypes, always specify < BLANK > as the subtype. For infotypes that support subtypes, you must explicitly specify each subtype to be checked.

When you have made this entry, you can create a data record of the Test Procedures infotype (0130). The subtype of this data record is the test procedure specified in T584A. This data record contains the check date amongst other things. As soon as this check date has been entered in the data record, a user, who is not authorized to change the check date (that is the subtype of the 0130 infotype), cannot make any changes that are before the check date to the infotype to be checked.

Example

In the framework of decentralized time recording, the time administrator records certain absences. An inspector should check the entered data. Time administrators should not be able to change the data once it has been checked.

You can set up a test procedure for the attendances and absences that are to be checked in table T584A. If you want to check all attendances and absences together, it is sufficient to set up one test procedure that can be used for all subtypes of the Attendances infotype (2002) to be checked. If you want to check the attendances and absences separately, you need to set up various test procedures.

At first, the time administrators can create and change any data within the scope of their authorizations. If a tester checks the entered data at a later date, he or she sets the check date for each personnel number checked in the corresponding subtype of the Test Procedures infotype (0130) to the date on which he or she finished the checks. This date is normally in the past but it can also be the current date. It would also be technically possible to have a date in the future but this makes little business sense.

As soon as the tester has set a check date, the time administrators can only enter data that is after the check date and within their scope of authorizations. Only time administrators who also have authorization to change the check date (that is, to change the corresponding subtype of the Test Procedures infotype), can still change data that is before the check date.

If the tester does not have write authorization for the data to be checked and the time administrator does not have authorization for the test procedures, data checks and data entry take place completely separately from each other.