Infotype 0034 : time constraint

Hello,
I've an issue with infotype 0034. I set time constraint to 2, but when creating a new occurence, the system doesn't delimit the previous one if it concern a different subtype.
Can someone please help?
Kr,
K

Dear Karim,
IT-0034(Corporate Functions) Time constraint is T that sap standard, which depends upon subtype,
then why are you changing the time constaint to 2.
where as with time constraint T you can see all the records.
in IT-0034 it will ask you for start date and End date of record.
why do you want system to delimit the record ?
i suggest you to use the sttandard one.
regards,
mohammed

Similar Messages

INFOTYPE 0034 - Time Constraint for Subtypes Issue

Experts,
I have an issue, our organisation maintains many subtypes for infogype 0034, and we want to delimit the previous entry regardless the subtype (same problem as yours) and i am not able to make it work the way we want..
Example :
employee joins the organisation and has the subtype '07' - home worker- for Infotype 0034 with following dates :
Start date : 01.01.2010
End date : 31.12.9999
now at a later date, the subtype of infotype changes as '09' - factory worker - for infotype 0034 with following dates :
Start date : 04.05.2010
End date : 31.12.9999
now, as we make an entry for subtype '09' with starting date as 04.05.2010 it should delimit the previous entry and the previous entry should have following dates
Starte date : 01.01.2010
End date : 03.05.2010
i have tried changing TC for IT 0034 in V_T582A to 'T' and TCs for subtypes as '1' in V_T591A as i found response for similar to this issue in one of the threads, but it does not resolve my issue
so, can experts suggest me what shall i do to make the IT 0034 behave in way that whenever there is a new entry for subtype it delimits the old entry (regardless of subtypes)?
Response will be highly appreciated
Thanks
Jalpa

Hi,
Please check the threads.
Re: Subtype wise record delimit for IT-0034 .
You can also check the user exit.. EXIT_SAPFP50M_002,LXPADU01.
Thanks & Regards,
Sandip Biswas.

Deleting an Infotype with Time Constraint 1 - programatically

Hi there,
We have a few records (IT0008), that need to be deleted. Unfortunately, when we use PA30 to delete, it won't delete the record(s). (Displays the error msg. "Record has time constraint 1" ) But, when we use the Utilities option in PA30 and go thru', it appears to successfully delete the same.
Now, could somebody pl. let us know how to go abt. doing the same programatically in ABAP ? I've tried looking at the FM's HR_MAINTAIN_MASTERDATA and HR_INFOTYPE_OPERATION (without much luck though....Although, SAP claims to have a documentation of these FM's, there is actually no proper docmn. at the Field level of these FMs)
Moreover, the FM HR_MAINTAIN_MASTERDATA returns exactly the same error "Record has time constraint 1".
Am a bit baffled as it is...
Any help would be gratefully acknowledged and appreciated.
Many thanks in anticipation,
Kind Regards,
RVS

there is no function module to do forbidden actions.
you only can do it with DELETE statement.
select single dbtab from t777d into gv_dbtab where infty = p_infty.
delete from (gv_dbtab) where pernr in p_pernr.
But you will have to be very carefully. There are "blind" infotypes behind some "normal" infotypes you will have to care about (i.e. 0000 -> 0302).

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

Infotypes -- Time constraint

Hi All,
How do you determine which time constraint is assigned to the subtype of an infotype?
Thanks in Advance...
Swapna.

Hi,
Please check Table T582A
This table tells which infotype is of which time constraint.
Fields
INFTY Infotype
ZEITB Time Constraint
Best regards,
raam

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 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 2 with HR_INFOTYPE_OPERATION

Hi,
I'm using FM HR_INFOTYPE _OPERATION to upload the data in a custom infotype having time-constraint 2. But the probelm is: its creating the data for tha GAP also.
What can be the problem ?
Regards,
Jyoti Shankar

Hi Jyoti ,
First thing just check you upload data and the dates and when you are uploading the data is any records are there , the time constraint 2 just make sure that no more than one valid record can exist any one time and whenever you create a new record it delimit the the previous record , So in this case as i think there were some entries already present it is delimit and creating gap.
There may be different cause is it checking some other infotype or record on the basis of that it creating gap , so check is there any dependency on any records .
If still problem exist reply.
Manoj Shakya.
Techno-Fuctional Consultant
SAP-HR
******(Useful answers should be rewarded)

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

Time constraints and Dialog module

1.What is the difference between the time constraints A(IT exists just once from 01 Jan 1800 to 12 Dec 9999) and B(IT exists for maximum of once from 01 Jan 1800 to 12 Dec 9999)?
2.What is the necessity of dialog module for a Infotype?

Time Constraint A and B
Infotypes with time constraint A & 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 A CANNOT be deleted.
Infotype records with time constraint B CAN be deleted.
The difference is check the BOLD TEXT.
As for ur second question, Function modules/dialog modules helps calling infotypes when called from any custom program ,and allows you to perform similar actions/tasks that you would perform on them from direct maintainance. ex: create,change, delete etc. also performing the same on multiple infotypes in a single go using a them is easier than writing a code to manipulate each single infotype.
SAP exposed these functions to be exploited as there will come many situations in business scenarios where you require to work with them by writing custom code.
hope its helpful

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.

Calendar time constraints

I started another thread about this but have had no replies. I know this means no one has a fix, but it would help a lot to know the answer to this question:
Is anyone currently syncing calendars - iCal or Entourage - to an external device, particularly a Nokia phone, where the iSync time constraints - "Don't sync events older than:..." and "Don't sync events after:... - are actually working?
I've established that I'm not the only person for whom they no longer work, but if I can find someone for whom they do actually work, then I'll keep debugging my system, instead of looking for a workaround and hoping it's fixed in the next update.
Thanks in advance,
Steve = : ^ )

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 notime 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 constraintA 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 TimeConstraint Reaction.

How to make a custom infotype field the time constraint 1?????

Hello everyone I have this challenging question for gurus to answer it.
In custom created infotype for OM Ii have that field called ZZJOBID. When infotype was created I assigned the time constraint 1 for that infotype. That time constraint was base on OBJID not on ZZJOBID. Now the problem I am encountering is when I assign the 2nd ZZJOBID with time span 01011800-12319999 it overwrite the 1st assign ZZJOBID.
for the requirement reason I have to use PO10( not po03). If I change the time constraint to 3 which let me have the multiple records but I am losing the delimit and other functionality which comes with time constraint 1.

Suresh,
you are wright when you say that ' Time Constraint is for the Infotype/Subtype record and cannot be based off a field.' The OM infotype runs on bases of Object such as Organizational Unit, Job, etc... The point I was trying to draw is I am looking for a way that allow me to work via TC PO10 which run on Organizational Unit along with different ZZJOBID (with same begda and endda, if needed).

Infotype 0034 : time constraint

Similar Messages

Maybe you are looking for