Time constraint of Infotype 0006 subtype 1 and 2

Hi All,
Currently the TC of infotype 0006 subtype 1 is 1.
I have changed it to 2, so that the gaps are there but no overlapping.
However, when I go in SAP and create a new record, its delimiting the previous record. But if I click on change button, its overwriting the original record instead of delimiting it.
Please advise what can be done regarding the same.

So that means, whenever an employee updates his address from the front end, the create address standard BAPI should be fired to update the data in R/3.
This will delimit the previous record, since I have maintained TC as 2 for subtype 1 and 2.
Please correct me if I am wrong.

Similar Messages

Change time constraint of Infotype 0006 subtype 1 and subtype 2

Hi
Can anyone tell me how to change the TC of infotype 0006 subtype 1 and subtype 2.
Currently I tried to change the TC in table V_T582A but its giving me an error : "Text maintenance not permitted as infotype part of Data Sharing (T582G) "
Can anyone please advise.
Currently the TC is T
I want to change it to 2.

hi ,
you can use SE38 to create a report like :
to change the time constraint for IT0006 +subty 1 + 2
REPORT ZTEST.
tables: t591a.
data: wt_tc type table of t591a.
select * from t591a into table wt_tc where infty = '0006' AND
( subty = '1' OR
subty = '2').
if sy-subrc = 0.
loop at wt_tc into t591a.
t591a-zeitb = 'x'. "new TC that you need
modify table t591a from t591a.
endloop.
endif.
regards

Time constraints for infotype 0185

Hi experts,
Need your suggestions,
Is it possible to change the Time constraints for infotype 0185. What will be the impact if i change from 2 to 3 time constraints. Please explain...
Shiv.

hi,
what i meant was standard time constraints should not be changed unless there is no other option.
changing the time constraint is a quick fix solution.
these standard time constraints are set after a lot of thought.
like he referred 185 which is personnel ids.
here you can see that it has sub types each sub type can have one record.
you cannt have two passports .
you cannot have two pan numbers etc.
lets us sasy the end user enters some data wrongly and then he realises and creates another record for the same with out deleting the old one.
the system will take it.
but as you can see the data is already duplicated and it gives errors if some work flow or some other functionality is written basing on that input.
regards
nalla

Time constraint of infotype based on subtype

Hi,
     I have created a master data infotype with different subtypes 0001,0002,0003,0004, etc. I want a time constraint 1 for subtype 0001 and 3 for all other subtypes.
     I would like to know the steps required for configuring the infotypes time constraints based on sub types.
     Kindly help.
Regards,
Satish

Hi Sayantan,
    Thanks.
Regards,
Satish

Time Constraint for Subtype

Dear All,
I have created Customer Infotype 9909 having Five Subtype. Now I have to give Time Constraint to each separate subtype. please guide for the same.
Regards
Mangesh

Dear All,
My created Infotype 9909 having Five Subtype like 1,2,3,4,5 and I have give Time Constraint i.e. 1,2,3 to each separate Subtype. Like same example you will find for Infotype 0006 of Address. For Infotype 0006 the Time Constraint is "T" but there is separate Time Constraint for each subtype of 0006. You will find it in Table T591A. I am sending the following values of Infotype 0006 with its Subtypes having Filed "ZEITB" which shows different Time Constraint for its Subtypes. So like that I want to maintain separate Time Constraint for each Subtype of created Infotype 9909.
MANDT     INFTY     SUBTY     ZEITB     OBJRQ     STEXT
800     6     1     1          Permanent residence
800     6     2     3          Temporary residence
800     6     3     2          Home address
800     6     4     2          Emergency address
800     6     5     2          Mailing address
800     6     6     2          Nursing address
So please let me know the solution.
Reagrds
Mangesh

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

Time constraint 'T' for custom infotype

HI experts,
Im creating a custom infotype and i want to assign time constraint 'T' for that infotype. But while assigning the time constraint in Infotype characteristcs in PM01, it throws the below error message.
"TIme constraint T is not allowed for 9021 infotype".
Pls tell me what is the pbm here and how to solve the problem?

Hi,
Try this.
If a subtype needs to be maintained for the Infotype then some additional steps also needs to be performed
before providing Infotype characteristics
1. Select the Technical attributes from the initial screen of PM01 transaction .You will see a list of RP_XXXX where XXXX is infotype.
2. Select the change button on application tool bar. The dialog module in the above screen then becomes
editable.
3. Select the Infotype 9021 and select the details button. Make sure you are in change mode.
4. Provide the Subtype field of the Infotype, Subtype table as T591A and Subty.text table as T591S.
5. Save and go back to the initial PM01 screen.
6. The subtypes for an Infotype can be entered via the maintenance view V_T591A.
Now try maintaining time constraint T with view V_T582A through SM31.
cheers
Ajay

Need in HR Infotyp Subtyp and a second Keyfield

Dear colleague,
I will use in a HR - Infotyp a Subtyp and a second Keyfield. The Subtyp defined the shape of the Infotyp und the second Keyfield is a foreign key from a other database table. The keyfield length is greater then 3 Bytes, so I can't use the standart fields OBJPS or SEQNR for the second Keyfield.
My question is:
Is it possible to use a keyfield outside of structur PAKEY. I want to set in this case the second Keyfield as Key in the transaction SE11 for this Infotyp. Will this Keyfield to be considered in all cases as "Time constraint" (Transaction PM01 / Infotyp charakteristics)
Thank you for your response
Frank Dehle

Hi,
It is not possible to use the key field other than the PAKEY structure. When you try to create a infotype through PM01, system automatically inserts the PAKEY structure as the key for the corresponding transparent table created in the dictionary. Those fields entered by the user will be created as PSnnnn structure in the infotype.
regards,
sankar

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

Time constraints for IT0377

Hello All,
For the Benefits IT, 0377, we are using a benefit area 08 and subtype 0001.
For this Benefit Area and Subtype, we have configured several Benefit Plans such as BUPA, CYCL, TRVL etc.
We want to set the time constraint such that for an employee, multiple benefit plans for the same period can exist (Time Constraint 3), but at the same time, there should be no overlapping record for the same benefit plan.
for Ex, a BUPA can exist from 01.01.2007 - 01.01.2008 and
a CYCL could exist from 01.01.2007 - 01.01.2008 but
another BUPA with 15.01.2007 - 15.09.2007 should not be allowed. In this case the earlier BUPA should be delimited.
If I use time constraint 1 or 2 I cannot create multiple benefit plans, as all previous records with the same time range are deleted.
How can I configure the Infotype such that the above requirement can be fulfilled?
Thank You,
Vaishali

Hi..
I don't think it can be done, as this as time constraint depends on the startdate and enddate, and it has no connection with the Benifit Plan .

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

Time constraints IT0070

hi all,
does anyone know if i can set subtype time contstraint in IT0070 Court Orders GB..?
thanks

I am guessing "No" because of the setting in Table T582A.
I suppose, if you really want to you can change the setting to "T" but inadvisable in my opinion.
Anyway, I have seen cases where employees have 2 or 3 court orders running at the same time, so the Time Constraint 3 should be correct and should not require changing.
Can you please let us know why you would like to change the TC for this/

Time constraint of Infotype 0006 subtype 1 and 2

Similar Messages

Maybe you are looking for