Process of Determining the Date After Which Changes Are Permitte (SAP Library

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

Call Parameters

The system transfers the following parameters to determine the date after which changes are permitted:

PERNR	Personnel Number
CKTYP	Test Procedures = Subtype of Test Procedures Infotype (0130)

Process Flow

The system performs all the following steps of this process.

The check date (RELDT) of the specified test procedure (data record of the subtype defined by CKTYP of the Test Procedures infotype (0130)) is imported:

If no date is found, every change made as of January 10, 1800 (up to and including) is permitted, that is, December 31, 1799 is taken as the date and processing is stopped at this point.
If a date is found, the following steps are carried out:

A personnel number check (with LEVEL = W, SUBTY = CKTYP) is performed for the test procedure (CKTYP) for the Test Procedures infotype (0130):

If the check returns authorized, every change made as of January 1, 1800 (up to and including) is permitted and processing is stopped at this point.
If the check returns not authorized, only changes after the check date are permitted and processing is stopped at this point.
If the check returns authorization unclear, processing continues.

The period of responsibility (for write access) is determined according to the structural authorization check.

The period of responsibility (for the corresponding subtype of infotype 0130, authorization level W) is determined according to P_ORGIN, P_ORGXX and the customer-specific authorization object, P_NNNNN.

The intersection of both periods of responsibility is determined and used as the period of responsibility:

If the current date (SY-DATUM) and the check date (P0130-RELDT) are not after the end of the period of responsibility, each change made as of January 1, 1800 (up to and including) is permitted.

If the current date or the check date are after the end of the period of responsibility, only changes after the check date (P0130-RELDT) are permitted.

The time logic for test procedures appears at first to function differently to the general time logic of authorization checks. However, both follow the exact same process. The only difference is that when you use test procedures, you already know that the check only returns authorization for write access and that the data records of the 0130 infotype are always valid from January 1, 1800 to December 31, 9999. The time logic for test procedures is as follows:

If a user has write authorization for all subtypes of the Test Procedures infotype (0130), he or she can change the check date for each test procedure and is, therefore, permitted to make changes to other infotypes independent of the test procedures.
If the user has no write authorization for a subtype of the Test Procedures infotype (0130), he or she cannot change the check date. The user is, therefore, only permitted to make changes that are after the check date to the infotypes tested by this test procedure.
The general authorization check is always used to determine the date regardless of whether or not the user has write authorization for a subtype of the Test Procedures infotype (0130).

See also:

See Flowchart 7 for a graphical representation of the test procedures and Flowchart 8for a graphic of how the date after which changes are permitted is determined.