An SAP Consultant

Time Constraints

A time constraint indicates whether more than one infotype record may be available at one time.
Time constraints are maintained in the view V_T582A.



                               The following time constraint indicators are permissible.

Time Constraints  1: An infotype record must be available at all times. 

This record may have no time gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.
Example: 0002(Personal Data ). A record must exist at all time time
Example: Infotypes 0019(Monitoring of Tasks):
Example: Infotype 0015 (additional payments).



Time Constraints A: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible. View V_T582B Infotypes Which are Created Automically controls
whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action. Infotypes with time constraint A may not be deleted.
Time Constraints B: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible. Infotypes with time constraint B may be deleted.
Time Constraints T: The time constraint varies depending on the subtype.

For the Addresses infotype (0006), 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 Constraints Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y  Time Constraint Reaction.