Time Constraint Value
1 = Record must have no gaps, no overlappings
2 = Record may include gaps, no overlappings
3 = Record may include gaps, can exist more than once
A = Infotype exists just once from Jan.1 1800 to Dec.12 9999
B = IT exists for maximum of once from Jan.1 1800 to Dec.12 9999
T = Time constraint is based on subtype or subtype table
Z = Time constraint for time management infotypes -> T554Y
Time Constraint Definition
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 notime 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 constraintA 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 TimeConstraint Reaction.
When you enter a new record, the system carries out a check to ensure that there are no contradictory records for that particular employee and time period.
It is not possible, for example, to enter an absence record if there is already an attendance record in the system for the same employee and time period.
When you customize the system, you can determine the system reaction if time data records collide. There are four possible reactions:
- An employee is on Leave from Monday to Friday, but is required to interrupt the vacation and return to work on Wednesday.
- You try to enter a Substitution record for an employee who is on leave.
- You try to enter substitution data for an employee who already has an overtime record for the same day.
- An employee is assigned to work a substitution, which involves longer hours than usual. You try to record the absence quotaTime off for overtime.
When you enter this data for the attendance type Attendance hours, the system draws your attention to the fact that a leave record already exists for the period. The leave record is automatically delimited if you proceed to save the attendance record.
The system does not allow this particular constellation, as it is not logical to assign a substitution to an employee who is not at work. An error message is displayed and the system rejects the record.
This combination is in fact permitted. Overtime and substitution records are not mutually exclusive. The substitution may involve the employee working different hours from normal, however. If this is the case, it may be that the new working time coincides with the period in which the employee is authorized to work overtime.
It is therefore preferable that the system draws your attention to the collision so that you can check your entries.
This constellation is allowed, since substitutions and absence quotas are not mutually exclusive. There is no time correlation between these two subtypes. The system therefore accepts the absence quota without drawing your attention to the existing substitution record.