Limit an infotype time constraint 2

Hi,
We have maked a client infotype that must have one register for every year. And for this reason its time constraint is 2.
User wants this infotype limits when employee fires. Do you know how to limit this infotype in a date different of 31.12.9999 without creating a new register?
Thanks in advance.

Write a dynamic action which will update it dates when there was an entry for FIRING in IT000.
Regards,
Amit
Reward all helpful replies.

Similar Messages

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

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

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

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

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 assignement to PD infotypes based on Subtypes.

Hello All,
Is there a way to assign Time contraint to PD infotype like 1005 based on Subtypes? If so how can we do this? I tried in table T591A but I guess this table is only for PA infotypes.
Thanks,
Chakri.

Hi,
Goto to sm30 and give T777I. There choose your infotype and click the time constraint. You can give the subtype and time constraint.
Balaji

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 for Time infotype

Hi all,
Where is the table to create a new time constraint class? I know how to link the reaction rules, but not how to create a new digit?
Thanks

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

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

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

Change Time Constraint for Personal Data InfoType

Hi,
How to change the Time Constraint for Personal Data InfoType.
I tried to do it in Customisation Procedure --> Infotypes, but the option to change Time Constraint is disabled for Infotype 0002.
Thanks

Hi,
you can change time constraints in general attributes of infotype attributes,this can be done through table maintenace view V_T582A.
But note that we cannot change the time contraints for mandatory infotyepe of personnel in an organization i.e -0000,0001,0002.
ex:- without personal details like names no personnel will exist in an organization.
regards,
Soori

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

Limit an infotype time constraint 2

Similar Messages

Maybe you are looking for