Show TOC

Object documentationTime Constraints Locate this document in the navigation structure

 

Time constraints are used internally by the system to protect the integrity of information such as infotypes, subtypes and relationships.

 

You use time constraints to prevent you from creating records that contradict each other. For example, a position can belong to only one organizational unit at one time. If the system allowed you to assign the position to another organizational unit during the same timeframe, there will be two contradictory records. Then, if you try to report on the data, the information will be useless.

Structure

There are four classes of time constraints:

Time constraint 0

This allows for:

  • A maximum of one infotype record of the same type for the same object at the same time.

  • No changes to the record

Time constraint 1

This allows for:

  • A maximum of one infotype record of the same type for the same object at the same time.

  • No gaps in time between valid records.

  • Some changes to be made to the attributes of the record

Time constraint 2

This allows for:

  • A maximum of one infotype record of the same type for the same object at the same time.

  • Gaps in time between valid records

Time constraint 3

This allows for:

  • Several infotype records of the same type for the same object at the same time.

  • Gaps to exist between valid records. For example, there could be a three-year gap between the validity periods of two infotype records that exist for the same object.

Integration

Time constraints work interdependently with validity periods. They determine which combination of validity periods are allowed among the different types of records you create and maintain in Organizational Management.