Purpose

In this process, the system runs the time logic within the General Authorization Check .

Call Parameters

The time logic is called up using the following parameters:

In addition, the period of responsibility that has already been determined is transferred.

Process Flow

If the period of responsibility is empty, the time logic returns not authorized .

The time logic determines whether the authorization check should be performed on a date-dependent basis (from T582A-VALDT).

If the check should not be performed on a date-dependent basis, the time logic check returns authorized .

If the check should be performed on a date-dependent basis, the following steps are carried out:

The tolerance time ( ADAYS authorization main switch) is determined.

The check establishes whether the check is for read access (LEVEL = R or M).

If the check is for read access, the following steps are carried out:

The end date of the period of responsibility is determined (see also the following graphic, 2: Period Determination for Read Access ):

If the current date (SY-DATUM) is not after the end date of the period of responsibility by more than the tolerance time (ADAYS), the period January 1, 1800 to December 31, 9999 is set as the new period of responsibility.

-         If the current date is not after the end date of the period of responsibility by more than the tolerance time, the period January 1, 1800 to end date of the old period of responsibility is set as the new period of responsibility.

The check establishes whether the validity periodBEGDA - ENDDAof the infotype has a full intersection with the newly defined period of responsibility, that is whether there is at least one day, which is in both periods:

If the intersection is not empty, the time logic check returns authorized .

If the intersection is empty, the time logic check returns not authorized .

If the check is for write access, the following steps are carried out (see also the following graphic: 3: Period Determination for Write Access ):

If the first day of the period of responsibility concurs with the first day of the organizational assignment (BEGDAof the first infotype record of infotype 0001, normally the date of the initial setting), the period of responsibility is extended to begin on January 1, 1800. (This is necessary to ensure that users can access dates that are before the initial setting.)

If the current date (SY-DATUM) is within the period of responsibility or after the end of a responsibility interval by no more than the tolerance time (ADAYS), the period January 1, 1800 to December 31, 9999 is set as the new period of responsibility.

If the current date (SY-DATUM) is outside a responsibility interval and by more than the tolerance time after the end of each responsibility interval, all responsibility intervals that are before the current date are deleted.

The check establishes whether the validity periodBEGDA - ENDDAof the infotype is completely within the newly defined period of responsibility:

If the validity period is within the period of responsibility, the time logic check returns authorized .

If the validity period is outside the period of responsibility, the time logic check returns not authorized .

See also:

Time Logic in Flowchart 6