Ansicht
Dokumentation

OHIX0198 - Specify System Reaction to Overlapping Time Infotypes

Addresses (Business Address Services)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Specify Reactions to Overlapping Time Infotypes

Use this Customizing activity to define the system responses to overlaps between newly created and existing data records in Time Management infotypes (2001 to 2013) as part of collision checks.

The collision checks are also performed at the level of the subtypes of the infotypes. You can use a time constraint class to group different infotypes and/or subtypes for which the same time constraint reaction is to be triggered. You define the time constraint classes in Customizing, under Define Time Constraint Classes.

In addition, you can use the feature MOCOL to determine the system response depending on certain data in infotype 0001. You make the settings for this in Customizing, under Define Modifier for Collision Grouping.

The time constraint reaction is determined using a reaction indicator. The reaction indicator is set for each time constraint class of an infotype or subtype in relation to the time constraint classes of all other infotypes or subtypes.

The system can react to a collision in one of four ways, each of which you can determine using a reaction indicator:

• A: The old record is delimited, meaning that the part of the old record that overlaps with the new record is deleted. One or two new records are created from the old record.

• E: It is not possible to create a new record. The system issues an error message.

• W: It is possible to add the new record without changing the old record. The system issues a warning.

• N: It is possible to add the new record without changing the old record. The system does not issue a warning.

Note: In the Customizing table, you can only select the reaction indicators A, E, and W. If there is no entry for a specific combination of infotypes in the reaction table, the system uses the indicator N as the default return value.

Note on Time Events Infotype

The Time Events infotype (2011) is also available for setting up collision checks. However, it does not usually make sense to check collisions with time events, since time evaluation has different processing options.
The infotype still exists in the list for consistency reasons, but you should leave all entries with the reaction indicator N. The collision checks for the infotype Time Events are no longer maintained.

You have defined time constraint classes in the Customizing activity Define Time Constraint Classes.

You have then assigned the time constraint classes to the relevant infotypes in the following Customizing activities:

• Define Substitution Types

• Define Entry Screen and Time Constraint Class for Absences

• Define Absence Quota Types

• Define Entry Screen and Time Constraint Class for Attendances

• Define Attendance Quota Types

• Define Availability Types

You can also define additional rules in Customizing, under Define Modifier for Collision Grouping.

A time constraint reaction has already been defined for the time constraint classes used by SAP.

Note: If possible, use the standard time constraint classes and adjust only the reaction indicators.

1. Check whether the system response to overlapping time infotypes meets your requirements.
2. If necessary, change the reaction indicators of a time constraint class.

Note: In the Customizing table, you can only select the reaction indicators A, E, and W. If there is no entry for a specific combination of infotypes in the reaction table, the system uses the indicator N as the default return value.

Note on Special Features of the System Response

When infotype records are entered, the system may react differently than specified in the Customizing settings:

• Special Features of Full-Day Infotype Records

• Special Features of Infotype Records of Less Than One Day

• Special Features of Infotype Records of More Than One Day

Special Features of Full-Day Records

Case 1:
An absence, attendance, or overtime collides with a substitution that overwrites the employee's personal work schedule (no position substitution or time substitution in combination with position). The reaction indicator A is defined in the system settings.
Since the substitution record forms the basis for valuating the attendance, absence, or overtime, the substitution record must not be delimited. Instead, the system issues an error message.

Case 2:
An absence with quota deduction collides with another absence with quota deduction. Both absences are deducted from the same quota. The reaction indicator A is defined for this combination in the system settings.
Since the system has already been deducted from a quota when the first absence is entered (for example, leave), the system cannot delimit the records. Errors would occur in quota deduction. For this reason, the system outputs an error message.

Case 3:
An absence with quota deduction collides with an absence with quota deduction for which the quota deduction has been maintained manually. Delimitation is not possible in this case either. The system issues an error message.

Special Features of Infotype Records of Less Than One Day

Case 1:
A partial-day record for which clock times have been entered collides with a partial-day record specifying a number of hours. In the system settings, reaction indicators A or E are defined for these combinations.
Since the system cannot delimit records in this example, or the records do not collide in certain circumstances, the system displays a warning.

Case 2:
A partial-day record specifying clock times or a number of hours collides with a full-day record or a record which encompasses several days. The reaction indicator A is defined for this combination in the system settings.
Since the system cannot delimit in this case, it is not possible to add the new record. The system issues an error message.

Case 3:
A partial-day record that specifies a number of hours collides with a partial-day record for which a number of hours or clock times have been entered. The reaction indicators A and E are defined in the system settings.
Since these records may not overlap, the system only issues a warning instead of delimiting the old record or preventing the new record from being added.

Case 4:
Two partial-day records for which clock times have been entered collide.

• If both records cover the same time interval, the system response depends on the system settings.

• If the time intervals of the two records do not overlap, you can add the new record regardless of the system settings. The system does not issue a warning.

• If the time intervals of the two records overlap, the system responds as follows:
  If the reaction indicator in the system settings is E or W, the system responds as entered. However, if the reaction indicator is A, the system issues an error message.

Special Features of Records of More Than One Day

If there is a record spanning more than one day for the previous day (a full-day record or one of less than a day with clock times) that extends into the current day, and if there is a record for the current day (a full-day record or one of less than one day with clock times), the system responds as follows:

• The record for the previous day overlaps with the current day's record.
  In this case, the conditions described in the special features for records of less than one day apply.

• The record for the previous day does not overlap with the current day’s record.
  If you have defined the reaction indicators A and W for this scenario in the Customizing settings, the system converts them to reaction indicator W.

1. You want to prevent the absence types Illness with Certificate and Paid Leave from being entered for the same period. Therefore, you assign time constraint class 02to the absence type Illness with Certificate, and time constraint class 01 to the absence type Paid Leave. If these two time constraint classes collide, define the time constraint reactions:

• If a sickness record has already been entered for the period, it should not be possible to enter leave. Therefore, this combination is assigned the time constraint reaction E.

• If a leave record has already been entered for the period, entering a sickness record should delimit the leave record. Therefore, this combination receives the time constraint reaction A. One or two new records are created from the old record:

• Old record: Paid Leave from 1/2/2022 - 1/20/2022

• New record: Illness with Certificate from 1/10/2022 - 1/12/2022 Illness with certificate

Result: The old record is delimited and a new leave record is generated:

• Paid Leave from 1/2/2022 - 1/9/2022 (delimited old record)

• Illness with Certificate from 1/10/2022 - 1/12/2022 (new record entered)

• Paid Leave from 1/13/2022 - 1/20/2022 (generated new record)

1. A substitution record is entered for a period for which an absence record Leave Paid already exists. The employee cannot act as a substitute if they are absent, so this combination is assigned reaction indicator E (error message).
2. A substitution record is entered for a period for which an overtime record already exists. This combination is permitted. However, in certain circumstances, the substitution may result in changed working times. For this reason, this combination is assigned reaction indicator W (warning) to give you an opportunity to recheck your entries.
3. An absence quota record is recorded for a period for which an attendance record already exists. Attendances and absence quotas are not mutually exclusive. For this reason, this combination is assigned reaction indicator N (add without warning).

BAL Application Log Documentation   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 13784 Date: 20240523 Time: 182046     sap01-206 ( 209 ms )