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

Similar Messages

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

  • 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

  • Multiple screens on an infotype based on subtype

    I've created a custom infotype with 2 seperate screens which need to be called based on subtype.  I have subtype set to required on the initial infotype screen but can't figure out how or where to go to set up the rules needed to call each screen seperately based on subtype entered.  My entries in T588m are as follows.
    MP980000     2000     P9800          0     0
    MP980000     2000          01     2000     0
    MP980000     2000          02     2001     0
    Any guidence would be greatly appreciated.
    Thanks.

    Hi Scott
    You can use a feature (transaction PE03) to distinguish the different dypros. For an example have a look at infotyp 0006 in T588M (using SM30 or via transaction PM01).
    Regards
    Roger

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

  • 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

  • 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

  • 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 <b>standard</b> 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 - 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 employee’s 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 T possible for IT0022?

    Hi
    We need to make sure one of our school types (SLART) has time constraint 2.  I see that field SLART is also saved in field SUBTY.  But when I check the table T582A, I see that the subtype table for IT0022 is T517T.  This does not contain a possibility for time constraint.  So my question is:  Can a school type have a time constraint, or do we need a badi for this?
    Thanks in advance.
    Kirsten

    Hi,
    The answer lies in table T777D, field ZBTAB for infotype 0022. SAP has delivered this table without any subtype table for IT22. The F1 help on the field is:
    Time Constraint Table When TC is Subtype-Dependent
    Use
    This field contains the name of the time constraint table if the time constraint is dependent on the subtype.
    Note
    You may not edit this table manually. You must use one of the following transactions to maintain infotypes and their components:
    o     PPCI  (Personnel Planning Infotype Copier)
    o     PM01  (Personnel Administration Infotype Copier)
    Hope this helps.
    Donnie

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

  • 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

Maybe you are looking for