Position Holder relationship Time Constraint

I have received a unique requirement from my client. They want only one employee to hold one position and on position only to be held by one employee. This in itself is the easy part.
However, for contingent workers (non-employees) that want to be able to tie multiple people to one position.
Has anyone ever done this? If so, how?
Any additional information that anyone can provide would be much appreciated!

Hi - You stated the following - see my notes in Bold:
You can either turn off the '100%' check for all Positions or make it a Warning or Information instead of an Error. This affects all Positions. - Not an option as this should throw an error for employees.
Personnel Management > Organizational Management > Basic Settings > Relationship Maintenance > Maintain Relationships
Click on Holder (008) > click on 'Relationship Characteristics' > W - Warning or I - Information
You can also Change the time constraint for the Position to Person A008 part of the relationship. Also, not an option as we want employee positions to error - only for non-employee positions should this be allowed.
Personnel Management > Organizational Management > Basic Settings > Relationship Maintenance > Maintain Relationships
Click on Holder (008) > click on 'Time constraints' > Click on 'A008' > Choose '3'
You can also, set the 'Staffing' Percentage' on the Relationship Infotype - A008 - holder to a blank.

Similar Messages

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 for Position A012 Relationship

Our organization's structure is such that one position may manage more than one organizational unit. The time contstraint for A012 relationship for positions is currently set to 2, which appears to be restricting me from establishing a position as chief for more than one subordinate org units. In our test environment I changed the constraint to 3 and now am able to have a position as chief of multiple org units. Have I created any potential problems (i.e. with workflow) by changing the A012 time contraint?
Thanks for any advice,
- Lora

Not that I am aware of. In the situation of having the time constraint is the when certain program uses evaluation path, it doesn't know which one of the path to pick since there are more than one path presented.
In the case of workflow, usually it will go to all of them. The first one that open the task owns the task.
But in the case of A012, it should be okay. There are situation where the chief relationship will be towards more than one organizational unit. Where his position belongs to is a different story. As where his position belongs to for the org unit defines who is his/her reviewer for performance and compensation. But he could have as many A012/B012 to manages all those org units as he wishes.

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 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 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

No Time constraint for S 1001

Dear Team,
When I am trying to create a relationship to Position (S) or (C) Job, receiving a message as "There is no time constraint for S 1001". Unable to locate the exact error location in the customization.
Could anyone know how to solve this. Not maintained any new objects or relationships.
Thanks and Regards
Team Member.

Hi,
Should have been standard for Position (S) and Job (C), but check table V_T777ZIT for IT1001 that the time constraint entry exists for the exact relationship you are trying to create. If it does not exist, you will have to create the time constraint for that object and relationship.
IMG: Personnel Management --> Organizational Management --> Basic Settings --> Data Model Enhancement --> Maintain Infotypes. Select IT1001 and click on the folder on the left for Time Constraint. Only one relationship at a time (Position described by one Job) - time constraint = 2. More than one relationship at a time (Job describes many Positions) - time constraint = 3.
Paul

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 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 assignement to Subtypes of an infotype.

Hello All,
Where do we maintain Time constraint assignment to subtypes of an infotype. I am looking to subtypes of IT 0210 ( Tax With holding ) " where do we create the subtypes and their characteristics for this infotype in IMG? I tried in view V_T591A but there is no entry for this 0210 infotype but I can find the time constraint assignment for the rest of the infotypes in this view.
Thanks,
Chakri.

try the following
SPRO>Personnel Management> Payroll>Payroll:USA>Payroll Results Adjustment-->Define Time Constraints for adjustments
select infotype 0210 & maintain
~Suresh

Time Constraint Class

What is the number (0 to 7) stands for time constraint class in absence for the screen number 2001. I have a leave type CL (causual leave). What time constraint class shall i assign to it.
Regards,
Chinmay

for ur info alreadt raghu has given the answer any way check this tooo
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)
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.
Time Constraints:
When an info type is updated, the old data is not lost. Instead, it remains in the system so that you can perform historical evaluations. Each info type is stored with a specific validity period. This means that the system can contain more than one record of the same info type at the sometime, even if their validity periods coincide.
If you enter and save new information in an info type, the system checks whether the record already exists for this info type. If this is the case, the system reacts based on rules or TIME CONSTRAINTS set up for that particular info type or subtype.
Time Constraint 1: This is mandatory information that must be uniquely available, gaps are not allowed
Time Constraint 2: This is optional information that, if available, must be unique, gaps allowed.
Time Constraint 3: This is optional information that, if available, can exist more than once.

DCIF - Time constraint 1

Hi all
The time constraint for the relationship that I am trying to update is set to 1.
When the relationship start data is earlier than the object start date the DCIF changes the start date of the relationship to the start date of the object and updates the infotype with an information message stating 'Start date corrected to the minimum date allowed'.
But if the relationship start date is later than the object start date then it gives an error message stating 'The validity of the record must match the validity of the object'.
At the same time I can update the same relationship with the same start date as the error record(i.e the start date later than the object start date) from transaction PP01 and it allows me to save the record.
Is there a particular reason why DCIF is meant to behave different to the standard transaction? has anyone else encountered this scenario?
Thanks

Hi Priti,
What are time constraint
1 no gaps and records are unique records are must eg IT 0008
2 Records may or may not be there if records are there they are unique eg IT 0019
3 Records may or may not be there gaps may be there Eg IT
In which context you want to use time constraint , Time constraint classes are stored in T582A.
Warm Regards,
Kapil KAushal
09833346985
19:00to 23:00 IST

Time Constraint Error when calling a Function module from Webdynpro ABAP

Any help will be greatly appreciated - Thanks RM
Time Constraint Error
Information on where terminated
    Termination occurred in the ABAP program "SAPUP50R" - in
     "CHECK_TIME_CONSTRAINT_S1".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 1069
    of the (Include) program "UP50RU01".
Error occurred during batch input processing
Source Code Extract
      l_is_inconsistent = 'X'.
    ENDIF.
Check if there are inverted time periods.
    IF l_prelp_line-begda > l_prelp_line-endda.
      l_is_inconsistent = 'X'.
    ENDIF.
Check if there are overlaps or gaps.
    IF NOT l_prelp_before IS INITIAL.
      l_date_difference = l_prelp_line-begda - l_prelp_before-endda.
      IF l_date_difference <> 1.
        l_is_inconsistent = 'X'.
      ENDIF.
    ENDIF.
    l_prelp_before = l_prelp_line.
ENDLOOP.
IF l_prelp_before-endda <> '99991231'.
    l_is_inconsistent = 'X'.
ENDIF.
IF l_is_inconsistent = 'X'.
    IF p_access_type = 'R'.
490 Datenbankschiefstand Personalnummer & Infotyp &
      MESSAGE x490 WITH l_prelp_before-pernr l_prelp_before-infty.
    ELSE.
491 Unzulässige Daten Personalnummer & Infotyp &
Line 1069 Error occcurs >>>> MESSAGE x491 WITH l_prelp_before-pernr l_prelp_before-infty.
    ENDIF.
ENDIF.
ENDFORM.                    " CHECK_TIME_CONSTRAINT_S1     "XYVN0352581
*&      Form clear_no_adapter_needed              new     "XREN844998
      text
FORM clear_no_adapter_needed .
CLEAR no_adapter_needed.
ENDFORM.                    " clear_no_adapter_needed
*&      Form set_no_adapter_needed              new     "XREN844998
      text
FORM set_no_adapter_needed .
no_adapter_needed = 'X'.
ENDFORM.                    " clear_no_adapter_needed

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

Time Constraints and Boundary Events in BPM

Hi all,
I have done the following:
In the Task window, Time Constraints tab
- Checked "Define a default completion deadline" with the offset as 3 minutes.
- Checked the "Raise critical exception when deadline is reached" checkbox.
In the boundary events for the activity, I have added "CompletionDeadlineIsCriticalException".
From the boundary event, I have linked to to another activity that belongs to another user (User B).
When i am testing the BPM, the task goes into a Suspended status after 3 minutes. However User B did not received a new item in the UWL.
In the NWA, "Manage Process: Process Instances", i can see that Task is escalated by null and the status is suspended.
Does anyone has any advice over here?
Thank you.

Hi,
i have checked the BPEM-CORE version as instructed.
It says 1000.7.11.2.0.20090321233900
Does that means I need to update to the latest patch?
Please also check the version of your NWDI build plug-in BPEM-BUILDT in the respective NWDI track. This is used to build Process Composer DCs in your NWDI.
I am in the Development Infrastructure Perspective in NWDS
How do i check the version number for BPEM-BUILDT in the NWDI?
Thank you.

Position Holder relationship Time Constraint

Similar Messages

Maybe you are looking for