on 02-19-2009 10:25 AM
What is time constraint class? n how to give a time constraint class on the screen i.e . "Determine entry screeen & time cnstraint classes"?
Hi,
A rule that determines whether collisions in time data are allowed, and if so, specifies how the system reacts to such collisions.
Time contraints comprise the following:
Time constraint classes that determine which collisions in time data records are allowed
Time constraint table that contains the time-based collisions allowed in the time data records
Time constraint indicator that displays whether a new data record that collides with an existing time data record can be transferred to the system or whether the transfer is prohibited
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 employeeu2019s 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.
Good luck
Devi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If you are asking for attendances and absences..
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.
Time Management controls time constraints by using
u2022 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.
u2022 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.
u2022 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:
u2212 Whether the new record can be admitted to the system
u2212 Whether the system issues a warning message, or
u2212 Whether the system rejects the new record and issues an error message
Good Explanation Devi...................
Other time constraints:
A: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint A may not be deleted.
B: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint B may be deleted.
T: Time constraint varies depending on subtype.
Z : Refers to time management infotypes.Time constraint for these ITs depend on time constraint class in table V_T554S_I. Collision checks : V_T554Y
Apart from 1, 2, 3 there are some other types of Time Constraints: A, B, T, Z.
The Infotypes with TC type A must exist, must have only one record in its lifetime, and these ITs cannot be deleted.
Example: IT0003 (Payroll Status)
The Infotypes with TC type B must have only one record in its lifetime.
Example: IT0031 (Reference Personnel numbers)
The Infotypes with TC type T will have subtypes, and the TC is based on the subtype.
Example: IT0009 (Bank Details)
The Time Mnagegement Infotypes will have TC type Z .
Example: IT2001 (Absences)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have three different types of time constraints:
TC 1: No gaps no overlaps
TC2: Gaps allowed no overlaps
TC3: Gaps and overlaps allowed
To assign to a screen you will have to decide if the that particular screen should be present at all times eg: IT0001 is time constraint 1 caz it should always be there for an employee and at the same there cannot be 2 records overlapping. Based on this you will assign the TC for screens..
As mentioned by sikindar TC A,B will have the start date and end date assigned by the system, whereas in TC1,2 and 3 you can assign the start and end date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the F1 states as below check V_554s_o
Determine Entry Screens and Time Constraint Classes
Use the data entry screen number for an absence to determine which screen (entry screen) is used to enter, display and maintain a record of this particular absence type.
The time constraint class controls the system reaction if a new record in the Absences infotype (2001) overlaps with existing time infotype records.
Example
When the system processes an absence classed as leave, it deducts from the leave entitlement quota. You should therefore assign the leave absence type to the quota deduction screen (2001).
Requirements
You have defined all required absence types in the Define Absence Types step.
Standard settings
The standard SAP absences types are already assigned to the appropriate screen numbers.
In the standard system, the following numbers are allocated to the screens:
1. 2000 - General absence
This screen is used for all absences which do not require special processing (such as paid leave of absence for getting married).
2. 2001 - Quota deduction
This screen is used for entering data on leave or time in lieu of overtime.
3. 2002 - Work incapacity
Use this screen for all absence types where continued pay should be taken into account automatically by the system.
4. Special screens have been developed for the following absence types:
2003 - maternity protection, parental leave
2004 - military and non-military service
2005 - work incapacity (Netherlands)
Recommendation
Copy the model entries from the SAP system when you define absence types. Note that non-visible entries from views are also copied. The appropriate screen numbers are already assigned in this step.
Each time you copy an entry, make sure that you only use absence types that have similar processes.
Activities
1. Check that the correct screen numbers have been assigned for all absence types. This is particularly important if you want to implement quota deduction.
2. Correct the entries if necessary.
3. Enter the time constraint class for the absence type. The section Specify System Reaction to Overlapping Time Infotypes contains concept information for defining time constraint classes.
Edited by: Sikindar on Feb 19, 2009 4:08 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Time constraints tell you about the existence of a record
A record must be present all the time
A record may be present, but if its present it should be unique. There should not be any overlaps.
Multiple records can be present at a time. This will have overlapping records.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.