TIme Constraint

[Former Member]

Can Someone Explain different time constraints for Infotype in detail.....

[Former Member]

If you create a new record when a previous record already exists, the system reacts in one of the

following ways: it delimits the record, extends it, divides it, or deletes it. The system‘s reaction

depends upon the time constraint. The time constraint is a characteristic of infotypes and subtypes. In

Master Data, we differentiate between three different time constraints (1, 2, and 3).

n Infotypes or subtypes with time constraint 1 must be unique i.e. only one valid record can exist for

any given time period. There can be no gaps between records.

n When you add a new record to an infotype with time constraint 1, the system delimits the

overlapping infotype record on the key date and adds the new record. This happens with infotype

Basic Pay (0008), for example. If you delete a record that must exist at all times, the previous record

is automatically extended. There can be no gaps between records here.

n Infotypes or subtypes with time constraint 2 can only have at most one record for a given time

period. There can be no gaps between records. If records overlap, the system adapts the previous

record accordingly by deleting, dividing, or delimiting it. An example of an infotype with time

constraint 2 is the subtype Spouse (1) in infotype Family/Related Person.

n Infotypes or subtypes with time constraint 3 can have gaps between records or overlapping records.

If records overlap here, the system does not react at all. Examples of infotypes with this time

constraint are Monitoring of Dates (0019) and Objects on Loan (0040).

[Former Member]

Time Constraint

A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:

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.

2: Only one record may be available at one time, but time gaps are permitted.

3: Any number of records may be valid at one time, and time gaps are permitted.

Other possible time constraint indicators are as follows:

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.

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.

T: The time constraint varies depending on the subtype.

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.