Time constraint of time Infotype 2006

Hi all,
I have a requirement wherein In IT2006 same record should not be created on the same date. For eg. if I create a record in IT2006 for its subtype "Leave Encashable" on 01.04.2014 and again I am creating it on 01.04.2014, It is not restricting me to do so. It is accepting and creating the same record.
I checked the settings in table V_t544y and V_544y_b, but I am not able to find out where actually I need to make changes.
Looking forward for a reply.
Tnx
Megha

Check in table V_T582A. Currently it might be maintained as Z. See the below options:
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
But this is SAP Standard Infotype, and making any changes in Standard Infotype is not advisable.
Thanks and Regards,
Bhagyashree

Similar Messages

Default Time Constraint in Time Infotypes

Dear All,
Could you please tell me which is the default time constraint in Time infotypes.
Thanks in advance
Maziya

Hi,
You can check infotype setting & time constraint in T Code PM01.
0007 Planned Working Time -Time constraint 1
2001 Absences                    - Time constraint Z
2002 Attendances                - Time constraint Z
2003 Substitutions                - Time constraint Z
2004 Availability,   2005 Overtime, 2006 Overtime, 2007 Attendance Quotas, 2011 Time Events, 2012 Time Transfer Specifications, 2013 Quota Corrections       - Time constraint Z
2010 Employee Remuneration Info- Time constraint T
reagrds
Sri

Time constraint in 0008 infotype - any report for this siituation?

Hi,
I need some help to solution a big problem with time constraint and 0008 infotype.
Resume:
when I put the "2" time constraint, all the history of 0008 entries are changed...
For exemple:
Old (before "2" time constraint):
0 - 01.11.2007 - 31.12.9999 - 1000,00
0 - 01.10.2007 - 31.10.2007 - 900,00
NEW (after "2" time constraint):
0 - 01.11.2007 - 31.12.9999 - 1000,00
0 - 01.10.2007 - 01.10.2007 - 900,00
BR - 01.10.2007 - 01.10.2007 - 900,00
OR
0 - 01.11.2007 - 31.12.9999 - 1000,00
BR - 01.10.2005 - 01.10.2005 - 900,00
there aren't logical situation, all the records have a lot of errors...
Are there any report that corrects this situation????
Regards!!!!
Sandra

Daniel,
thanks for your response, and here's some more info:
- I've use the time contraint in multiple playlists, that have worked just fine before adding the time constraint;
- initially, after adding a time constraint (usually something like "time" "is less than" "10:00") everything seemed fine;
- only a few days later I noticed that my playlist hadn't been updated correctly. For example, one of my playlists consists of songs rated 4 and I limit to 50 songs by least recently played; with over 900 songs rated 4, after a song was played it should disappear from that playlist for a while but some songs didn't; also, sometimes I would see less than 50 songs in that playlist;
- after removing the time constraint the playlist updated correctly again
I know that the fact this only appears after a few days (or that I've only noticed it a few days later) makes it pretty tough to narrow down but that's all I've got so far.
Thanks again,
Heiko.

T. Code to Check Out Time Constraint for an Infotype

Is there any central transaction code to check the time constraint for an infotype? What will be its IMG Path?
Rgds,
Tapan Shah

Hello tapan
go to SM30 -> V_T582A
it is the table to configure infotypes
regards

IT2001 error, no time constraint reachion for infotype 2001 with tm const00

Dear Seriors,
When I try to add any absence, it show the below given error message (red colour), but if I hit the enter button it allows me to mark absence.
no time constraint reachion for infotype 2001 with time constraint class 001
What might be the reason?
Regards
ET

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.
Please explore on this.

No time constraint reaction for infotype 2005 with time contraint class 00u2019

Hi,
We have a incident wherein employee is trying to put overtime, IT 2005 for the period when he is on standby IT 2004. It gives error u2018No time constraint reaction for infotype 2005 with time contraint class 00u2019.
Can anybody help?

Hi,
Please maintain table V_554Y_B for 2005 TC class 00 and 2004 infotype.
Regards,
Dilek

Changing Time constraint of standard infotype..

Hi ,
Can we change the time constraint of Infotype 0001 ?
Thanks.
Madhu

Hi,
You should not attempt to do so, by doing so u r changing the standard process that is not at all recommended as it may have an adverse effect on the standard checks and validations that exist in the system and also system may behave in an un-anticipated manner.
Regards,
Tomesh

Changing Time Constraint of Standard Infotypes

Hi,
Just wondering is it possible to check the time constraint of <b>standard</b> infotypes such that the behaviour of infotype records will react accordingly to the time constraint?
I am aware that we can change the time constraint in PM01 but i have tested it, it does not seem to delimit past infotype records. I have changed the time constraint of Infotype 0081 to 2, but it does not delimit past records. Is it dependent on the infotype itself as well? Is there any existing function module or user exit that I can use to enhance the module pool of infotype to delimit records?
Thank you.

Hi,
Can u tell me which IT r u trying ,,,, try for 0022 IT too ,
check whether the behaviour is the same .
When u give 2 as time constraint , your problem should be solved .
Eg: 24.10.2007 - 31.12.9999 - 1st record
24.11.2007 - 31.12.9999 - 2nd record
While saving the second record ,
IF Time constraint is 1 : it will delimit with a date as 23.11.2007 for 1st record
IF Time constraint is 2 : it will delimit with a date as 23.11.2007 for 1st record (does the same thing)
Time gaps are the difference (You can have the record delimited to 20.11.2007 for Tiime constrint 2 but for 1 it shud not allow the same)
If this is not happening the messages are the problem .
Use user exit for the same to correct the problem .
What is the message ur getting when you try to save the second record .
Regards
Gajalakshmi

Impact of changing Time Constraints in Time Management

hello gurus,
2 leaves can be taken at the same time if TCC is 3 with a Warning Message.
a) Is this feasible ??
b) Will this have any negative impact on the time evaluation? If yes what will be the impact?
My business requirement is that are 2 diff leaves possible for the same period?
rgds,

Hi,
When an employee goes on FMLA he has certain leaves that can be taken with FMLA. So my doubt if its feasible & if yes then whts the impact?
see in simple terms of what i understand is FMLA is a leave OK with that you can take certain leaves right,so what i presume is if he has some 4 diff types of leave ,he can avail all those one by one complete them all then go on FMLA.
e g:- leave 1 from 1st April to 30th April,leave 2 from 1st may to 31st may,leave 3 from 1st June to 30th June and leave 4 from 1st July to 30th July and when all are exhausted then from 1st Aug FMLA (this is only illustration of my understanding )hope its clear cause which employee would want to take 1 CL & PL on same day and sacrifice one extra leave?
when we say it combines all leaves its actually one after the other,if still you have doubts you can revert back to forum with other experts view on this.
Salil

Position to Cost Center Relationship with time constraint 1

Hi,
I have a situation wherein:
1. There exists 2 records in PP01 with S-K relationship e.g. 01.01.2013 to 28.02.2013 and 01.03.2013 to 31.12.9999
2. There is a requirement to create another S-K record with dates; 01.02.2013-28.02.2013 automatically delimiting the first record.
Hence in all three records should exist
But when i try creating the 3rd record with end date 28.03.2013, it gives an information message stating End Date corrected to maximum end date of 31.12.9999. Thereby over writing the previous record(2nd one)
Do I need to change time constraint? Time constraint 1 should ideally allow this, as my records do not have gaps and exist at all times.
Please guide me through.

Hi Rohan,
Please check the table V_T777ZVK and the time constraint between S and A011 it must be 02 as per the standard system.
Then time constraint 2 means a maximum of one infotype record of the same type for the same object at the same time.
So if you change then end date must be 31.12.9999.
Regards,
Mithun K

Time Constraints - Hr ABAP

Hi Everyone
Can anybody throw some light on the various time constraints used in the HR-ABAP and their relation to the infotypes.
Also specify if their some Transaction code from where we can get to know about the value's of the time constraints.
And also if their's any Table associated with them.
<REMOVED BY MODERATOR>
Thanks & Regards
Gaurav
Edited by: Alvaro Tejada Galindo on Feb 22, 2008 10:24 AM

Hi,
Please refer to the document below:
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 employees 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.
The system also contains the following time constraint indicators:
Time Constraint A
Infotypes with time constraint A must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.
Infotype records with time constraint A cannot be deleted.
Time Constraint B
Infotypes with time constraint B must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.
Infotype records with time constraint B can be deleted.
Time Constraint T
Infotype records with time constraint T depend on the subtype.
The principles of data entry and time constraints that apply to infotypes ensure that data is consistent and accurate. They also constitute the basis of time recording, payroll accounting, and reporting.
Thanks,
Sriram Ponna.

Time Constraint

Hi All,
Can you please tell me how to view all the infotypes which fall under a particular category. For example, what are infotypes that are of category 'A'.
Thanks,
Ranjith.

The field ZEITB in the table T582A holds the time constraint of the Infotype.
1. Execute the transaction SE16
2. Click on the Table Contents button in the toolbar
3. Ensure that the Time Constraint field is available for selection
(If not availble, add the field by following the menu path Settings->Fields for selection)
4.Input the value of the time constraint (Ex: 1 or A)
5. Now, click on execute, the system lists all the infotypes with the selected time constraint.

Time Constraint Classes.

Hi All,
Pls let me know the concepts for Time Constraints classes.
Regards
Rajesh

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.
Regards
...Sadhu

Time Constraint- 1,2,3/A,B,T,Z

Respected Seniors,
Please guide me on the system response Of Time constraint on Info types.
I have gone through the SAP Docs,But some where i am not able to understand the system response.
As per the documents what i can understand is
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
My question here is how the infotypes react as per the time constains?????what kind of restriction time constraints puts on the infotypes.
Thank you very much.

Greetings,,
as i understand from your concern "correct me if i were wrong" that you couldn't understand the impact of time constrains on infotypes.
1 = Record must have no gaps, no overlapping.
when you chose this TC, you can't have gaps, nor overlapping.
this would be require from Infotypes like, 0001,0008,0009 ... etc etc
where it should be only ONE record valid.
2 = Record may include gaps, no overlapping
when you chose this TC, it means that you can have gaps but NO overlapping.
for example: IT0021, you can have 1 spouse ! but also, a gap can occur their if a divorce happens.
3 = Record may include gaps, can exist more than once
for example: IT0014 you can have multipull records in that infotype in the same time with overlapping "for IT0014 you can have a record with the same start date and end date"
you can pick any of TC's that you have mentioned in restricting creation multiple records for any infotype.

IT0009 with Time Constraint 1

Hi Experts,
We have defined IT0009 with a subtype whcih has Time Constraint value as 1. Ideally we shouldn't be able to delete the IT0009 with Time Constraint 1. But still we are able to delete all records for It0009. Could anybody tell why this is happening?
Regards
Niharika

Hi,
Time constraint Class for infotype 0009 is T that means it will depend upon the subtype
If you change this time constraint class to one in table V_512W_D you will not be able to delete the recods for 0009.
Warm Regards,
Kapil Kaushal

Time constraint of time Infotype 2006

Similar Messages

Maybe you are looking for