Definition of Collision Checks 

Collision checks are defined when you customize the system, for subtypes rather than infotypes. This means you can also control collisions between two different attendance or absence types.

Attendance and absence types, and attendance and absence quotas form a separate subtype within their respective infotypes.

When the system is customized, the reaction to a collision between two subtypes is defined. It does not matter whether these subtypes belong to the same infotype or two separate infotypes.

Grouping subtypes

It is possible to group the subtypes belonging to one infotype; this saves you having to define the system reaction to collisions for each subtype individually. You should group all subtypes which are processed similarly under the same Time constraint class.

The reaction indicator

A reaction indicator is set when the system is customized for subtypes which belong to the same time constraint class. The indicator determines how the system should react if subtypes collide. There are four possible reactions:

The system does not display the collision or change records, and allows you to create the new record.

The collision is displayed but no records are changed. The new record can be created, but a warning message is issued.

The collision is displayed but no records are changed. The system does not allow you to create the new record, and displays an error message.

The system displays the collision and changes the old record. The new record is created, but a warning message is displayed.

If you have problems entering time data, please contact your system consultant or refer to the Implementation Guide for the various configuration options. You can find these under: System reaction to overlapping time infotypes.