time constraint class

[Former Member]

what is time constraint class,explain with simple example about it

[Former Member]

Hi,

This is Kumar...

Time constrains are using mainly for automatic process of infotypes...........

Eg:...While u r updating 0002 infotype,system will take u automatically 0021 -Family Members ,like this all infotypes.........

Regards:

Kumar.G

[Former Member]

Time constraint class

The time constraint class is used to check for collisions between Time Management infotypes (2001 to 2012). It allows you to specify different regulations for checking for collisions between individual subtypes.

The views Time Constraint Reaction to Time Management Infotypes (V_554Y_B) and Global Time Constraint Reaction (V_T554Y) contain rules for the collision check.

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.

System reaction:

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.

All these will be determined based on Tim Constraint class

[Former Member]

hai ananth,

thanks for ur reply, u have given good overview od tcc with simple example,we r using mostly 3 tcc,but what about 4 to 9,is it custom defined,and where we can define it.

[former_member583520]

Hi

I think

Just as in HR Master Data, Time Management defines rules and procedures which govern the entry of new time records and their impact on existing data records. In many cases, data records collide. As a result, there must be an established method for determining under which circumstances collisions may or may not be allowed with respect to time infotypes. In addition, consideration must be given to the length of time each data record covers and what special relationships may occur as a result.

Time Management controls time constraints by using

Time Constraint Classes

Time constraint classes are assigned to the time infotypes and subtypes in the HR Time Management component, and define the collision rules which apply to each.

Time Constraint Tables

Each Time Management infotype is linked to a time constraint table. Here, relationships are defined between the new time record and all other infotypes with which it could collide. In other words, these tables determine what time collisions are allowed between time infotypes and/or subtypes.

Time Constraint Indicators

An indicator is applied to each collision relationship defined within the time constraint tables. These indicators are displayed on screen when new data records are entered. Depending on the collision and the infotypes involved, they determine:

Whether the new record can be admitted to the system

Whether the system issues a warning message, or

Whether the system rejects the new record and issues an error message

Of the three primary time constraints defined for Master Data, Time Management is best linked with Time Constraint 3, which allows for the existence of both gaps and collisions. However, while checks for Master Data time constraints are carried out at the day level, Time Management requires checks at the hour level.

Time Constraint Z is unique to Time Management infotype records. The time constraint for a time infotype record is defined in the subtype.

If you have any querys on this pls let me know.

Regards,

Revathi.

[Former Member]

Thanks Revathi,

you are given the detailed view of time constraint class,so we are aware of 3 time constraint class only,but what about the remaining, as these are used as per the custom ,how can we define the rules for those.