Time Constraints in Time Management 

Use

Just as in HR Master Data, Time Management defines rules and procedures which govern the entry of new time records and their impact on existing data records. In many cases, data records collide. As a result, there must be an established method for determining under which circumstances collisions may or may not be allowed with respect to time infotypes. In addition, consideration must be given to the length of time each data record covers and what special relationships may occur as a result.

Features

Time Management controls time constraints by using

Time constraint classes are assigned to the time infotypes and subtypes in the HR Time Management component, and define the collision rules which apply to each.

Each Time Management infotype is linked to a time constraint table. Here, relationships are defined between the new time record and all other infotypes with which it could collide. In other words, these tables determine what time collisions are allowed between time infotypes and/or subtypes.

An indicator is applied to each collision relationship defined within the time constraint tables. These indicators are displayed on screen when new data records are entered. Depending on the collision and the infotypes involved, they determine:

A list of these indicators can be found in the section Definition of Collision Checks.

Of the three primary time constraints defined for Master Data, Time Management is best linked with Time Constraint 3, which allows for the existence of both gaps and collisions. However, while checks for Master Data time constraints are carried out at the day level, Time Management requires checks at the hour level.

Time Constraint Z is unique to Time Management infotype records. The time constraint for a time infotype record is defined in the subtype.

For information on time constraints, see also Time Constraints in Master Data