Get time constraint

Hi
Is there any function module or anything by which i can get the time constraint of an infotype.
I have tried RH_PM_GET_TIMECONSTRAINT, but it does not return anything if time constraint of subtype is not in T591a.
As time constraint of subtypes may be stored in any other table other than T591a, this FM does not work.
Please help.
Regards

Please check below tables
T591A-- Subtype characteristics
T512Z --Infotypes 0008/14/15/0276 and 2010 sty are defined here ( wage types) these WTs time constraints are defined in T591B.
Please check my be useful.
Thank you,
NLR

Similar Messages

Get a process variable's value to set a task's time constraints

Hi,
I want to have my task expiration times determined by a process variable (Data Object Artifact) that defines a task's "time to live".
The problem is that I don't have visibility of the process variables inside the Time Constraint's Expression editor.
Is there a way to get a value of a process variable inside a task without modifying the Web Dynpro associated with the task?
Thank you,
Pietro

Hi Pietro,
As the task is associated with the WD mapped to it, we will be able to access only the WD Interface controller context associated with it and also few other Task attributes.
Regards,
Unni

Time Constraint for Boundary Events

Hi experts.
I am pretty new to BPM (NetWeaver Developer Studio 7.1 SP04 BPM SP05) and I am just making a test process to try to get the time constraint concept right. So far I have three tasks in my process, very much like a textbook example. In my first task I have an input field in which you're supposed to type in your name, which is then saved to the context and triggers the second task when completed. That second task is nothing but a screen displaying "You successfully generated a second task, (with the name you entered in the first task here)."
That works fine so far. Then there's the third task, which is linked to a boundary event on the second event with a start deadline which is critical exception. Here's the idea... You complete the first task (name input), then you fail to start the second task within a certain amount of time defined by an expression, so the process should go to the third task because of the deadline. By the way, it works fine when using a default time, so I must be doing something right so far, the problem is when trying to dynamically change the time with the expression.
What I tried was to define a context attribute type time and date (I tried both) and assigning a time (current time plus whatever amount of minutes) to that attribute via Java coding at the time you click on the button which completes the task, then use that context element in the expression, but that didn't work. I also tried to make that context attribute an integer and set it to whatever amount of minutes I want to use for the deadline, then in the expression get the current time and add that afore mentioned integer to its minutes. That didn't work either.
Please help, I have seriously done some research, and no success yet.
Edited by: david.palafox on Jul 1, 2010 5:54 PM

Figured it out.

Any report to identify Time Constraint issues?

Hello,
Is there a report that I can run to get the employees and Infotype records with time constraint issues? So until last week, we had not turned on the PC-UI switch in T77S0 table. So the way it worked was, if in history there were 2 records with time gaps for Infotype with time constraint = 1, then it still allowed us to create new records. Now with the switch turned on, it gives an error. Once the historic records are corrected, it allows us to proceed. This is freaking out a lot of data specialists, and we were wondering if we can proactively identify the employees with these historic data inconsistencies and be able to correct them. Please let me know.
Thanks,
Nakul

Found it: RPUSCNTC
Thanks,
Nakul

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 Constraints on ESS - Record Working Time and Leave Request

Hi All,
I have configured Time Constraints and their reaction in V_T554Y.
When I record the appropriate combination of Attendances and Absences in back-end, I can see the reactions as specified... However, when I try to do the same in ESS - Recording Working Time and Leave Request, I do not see that Time Constraints taking effect on the front end.
Here is what I have done:
I have two attendance - P001 and P002. P001 is configured to be recorded on Leave Request where as P002 is configured to be recorded via Record Working Time (CATS) link.
I record the attendance P001 in Leave Request and also post that into infotypes. After this, I try to record P002 in the Record Working Time Screen and I still get errors (Errors are from: HRTIM00REC E/207 and LR E/335)
If I try to replicate the same in the back-end in IT20002, then there is no issues.
Can anyone help and let me know how we can implement the same Time constraints reactions on the front-end and the back-end.
Thanks a bunch
- Harshal

Note that Time constraints are not valid for Leave request and Working time ie in ESS
it only comes via PA30
in CATS too, we dont follow much HR related collisions checks these are taken into consideration during CAT6
and in leave request via Rptarqpost
so its not gonna work, Its intended and correct! go for a user exit cats0003 or check cac1 profile customisation

Time Constraints for objects and relationships

Hi,
How to set up time constraints for objects and relationships under Org Management?
Thanks in advance.

Hi,
If you need time constraint for subtype A002 then you have to define it over here.
Usually for all standard objects this table gets populated by SAP. But in case you want something which is not there in this table and is as per the client requirement, you can create.
regards
guds

Time constraint collision

Hi all,
When i am trying to book an employee for absence i am getting collision with other leaves.
Why is this?Should i need to change the TC.
Regards
janhavi

yes u need to do change time constraints
http://help.sap.com/saphelp_47x200/helpdata/en/48/35c9f24abf11d18a0f0000e816ae6e/frameset.htm
Edited by: Sikindar on Apr 24, 2008 1:50 PM

Time constraint maintainance error

hi, when I am trying to update the infotype 1002, after maintaining the relation between Position and Org Unit through RH_Relation_Maintain I am getting an error ' time constraint not found for S 1002 A003'. I do not have the previliges to maintain new entries in T777Z either.
any suggestions on how can I handle this would be helpful.

Hi,
Well, are you trying to do a batch input on infotype 0000? If yes you need to check that the proposed values respects the time constraint, meaning no gap, no overlaps and no inversions. Also fields SUBTY, OBJPS, SPRPS and SEQNR must remain initial when processing IT0000...
Kr,
Manu.

Time constraint of Subtype

Hi
For the Infotype's Time constraint we can use the table T582A,
But how to get the Subtype's Time Constraint?
Thanks & regards
Manjari

HI,
Refer to the link.
Time Constraint assignement to Subtypes of an infotype.
Regards
Sumit Agarwal

Time Constraint issue

I am getting the error below when I change the S-S (A002) relationship in po13
"No time constraint exists for key 01001S 100003931001A 1 2009090499991231S 100020"
When I go to OOIT to look for the time constraint I do see time constraint defined...
S 1001 Relationships A002 Reports (line to) 2 (ENTRY FROM OOIT)
This issue occurs in our environment with SP16 service pack (ECC 6) but if I go to other environment which is still on SP4 (ECC 6) I don't get this error.
Also, I noticed that when I try to create a new position, I am able to do so. But when I go to add A002 relationship (S-S)
I get the error below.
No time constraint exists for key 01001 000000001001B0021 2009092999991231S 100077
Please help. Thanks for your help.
Edited by: Vikas Mahajan on Sep 30, 2009 3:46 AM

Hi
Kindly let me know how did you fix this issue. I am also getting same error.
When uploading costcentre (S to K A011) through LSMW, i am getting the below error.
" No time constraint exists for key 51001 000000001001B0111 2009080199991231S 600020"
When i update manually, i am not getting the error. I am able to update.
With regards
K.Vijayaragahvan

Time constraint classes and screen number for absence type

Hi all,
What should be the Time constraint classes and screen number for absence type.
The different absence types are annual leave, sick leave , study leave , personal leave, maternity leave , juryduty leave nad leave without pay etc
Kindly help.
Regards,

The time constaint class depends on the client requirement.
eg.if they want that a error needs to be generated while overlapping absences or warning message is required.
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
For screen number you will have to see if the is quota based deduction or just an absence. Here is the documentation of screen number from SAP
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)
Please go through the documentation of the configuration.
Shrikant Basarkar

Time Constraint Type T for IT0380

Currently we have the Time Constraint on IT0380 set to 3, but that results in Infotypes getting created as shown below with the second Infotype with the same BEGDA but a different subtype and different ENDDA getting SEQNR = 1. Because of this if someone were to run the program that inserts these records again, I assume it would create a new record with SEQNR = 2. I only want 1 record for a given SUBTYPE to active in a period so I was looking at changing the Time Constraint to T. The ENDDA will not be 12/31/9999 on these records. Is this a good idea and will it accomplish what I'm trying to do?

Hello Sir,
Of course you can, but this configuration needs to be consistent. How so?
On V_T582A, you configure the Infotype for Type T as you mentioned.
Then, on V_T591A you configure how you want the constraints on the subtypes for this particular IT 0380.
This is possible indeed.
Regards,
Bentow

Time constraint not found for A1001 B007

Hi all,
I have created a role and assigned users to the role and created a workcenter in Po01. While assigning the workcenter to the role, its giving a error "Time constraint not found for A1001 B007". I have checked the start date of workcenter is greater than the start date of the role. Please let me know, any config. needs to be done.

Hi!
Check in table T777Z in SM30 or SM31, you will see the time constraint for B007 has not maintained
Simply add new entry and fix it. Then you can get rid of this error!
Regards!

How to slove the time constraint error?

Hi Experts,
Please help me solving the error " Grouping not possible for infotype 0077 time constraint 3 I '".
I am getting this error when i click on check and send button. Please help me in solving this on.
Thanks,
Rocky.

Hi,
I solved a similar problem by changing the configuring Personnel Management->Personnel Administration->Basic Settings->Basic Settings for Concurrent Employment->Editor for Personnel Assignment Groupings->Change Assignment of Grouping Rules to Grouping Reasons in the img.
Hope it helps.

Get time constraint

Similar Messages

Maybe you are looking for