Time Constraints in HR Master Data 

Definition

Time constraints guarantee that exactly the data the system needs to be able to correctly process the employee data, handle personnel administration processes and run payroll for an employee is available in the system. Time constraints keep you from storing mutually incompatible data and prevent gaps from occurring in the data history.

Use

You use time constraints to define the following:

·        Whether an infotype record must exist for an employee in the system

·        Whether further records of the same infotypes may exist

·        Whether these records can overlap in the validity period.

For certain infotypes, you can also assign different time constraints in relation to the infotype’s subtype.

When you enter infotypes, the system automatically checks if your input satisfies the time constraints’ conditions, and reacts by automatically delimiting data records or issuing error messages.

Structure

·        Time Constraint 1

For the entire time that the employee works at the enterprise, exactly one valid infotype record must exist. The validity periods of the individual records must not overlap. When you create a new record, the system automatically uses the start date of the new record as the delimitation date of the old record. Gaps are only allowed between the employee’s entry date and the start date of the first record.

Time constraint 1 must be used for all of the infotypes containing information that must be available at all times. This is particularly true of personal and organizational assignment data.

An Organizational Assignment infotype record (0001) must exist for all active or inactive employees in the SAP System. The system needs the data stored in this infotype for all business processes.

In addition, this data must be unique, in other words, the system must know precisely to which organizational units the employee belongs. That’s why only one record may exist at the same time.

·        Time Constraint 2

No more than one valid record can exist at any one time. Records with constraint 2 must not overlap. Their existence is not obligatory. When you create a new record, the system delimits the previous record, if one exists. If the system delimits a record because of time constraint 2, it issues an appropriate message.

·        Time Constraint 3

Any number of valid records can exist at any one time. The individual records do not conflict with each other.

In the Powers of Attorney infotype (0030), you can store different powers of attorney. That’s why any number of records for this infotype can exist at the same time. Since not every employee in your company has powers of attorney, a record for this infotype does not have to exist in the system.

·        Time Constraint A

Infotypes with time constraint A must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.

Infotype records with time constraint A cannot be deleted.

·        Time Constraint B

Infotypes with time constraint B must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.

Infotype records with time constraint B can be deleted.

·        Time Constraint T

Infotype records with time constraint T depend on the subtype.

For the Addresses infotype (0030), you can assign a different time constraint for each subtype. In this way, you can make sure that a main address always exists for the employee and you can also enter temporary residences, if necessary.

·        Time Constraint Z

The infotypes you use for entering working and absence time have a special time constraint behavior. For more information, see Time Constraints in Time Management.