Time Constraint
 

When you update an Infotype, old data is not lost but archived for historical evaluation. The system records a specific period of validity for each Infotype, This enables the system to store more than one Infotype record at the same time, even if their validity periods overlap. This means that the time relationships between Infotype records must be defined. The concept of time constraints enables you to do this.

HR master data uses the following three time constraints:

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. If a new record is created, 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. If a record is delimited because of time constraint 1, the system displays an appropriate message.

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. If a new record is created, the system automatically delimits the previous record, if one exists.If a record is delimited because of time constraint 2, the system displays 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.

The system also contains the following time constraint indicators:


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.The principles of data entry and time constraints that apply to infotypes ensure that data is consistent and accurate. They also constitute the basis of time recording, payroll accounting, and reporting.

need examples for timeconstraint
 

Dear Trainer,


Pls post with example for timeconstraints

Regards,
Nanda

Hi

We asked on trainers, will attach soon.

Thanks
Wiki SAP Tier I