Procedure to Delimit Infotype 1613

HI,
I need to delimit infotype 16313 for about 350 positions whcih are assigned to single Worker compensation code. Accept PP02 anyone pleasee let me know hos can i do this in bulk. Is there any fast entry or any programe to delimit WC code entries for all the positions at a time?
Please help me in this.
Thanks & Regards,
Naga

Hi Naga,
Try transaction RE_RHGRENZ2.
Good luck,
Dilek

Similar Messages

  • Delimit Infotype 0105 Subtype 0001

    Hi All
    I am new to ABAP so need help.
    We need to delimit Infotype 0105 subtype 0001 records.
    I tried vai a number of ways but facing issues in someway or the other.
    When I try to do the same via FM: BAPI_HRMASTER_SAVE_REPL_MULT, it creates a new entry for the same record with end validity day as system date (the old record which has end validity date as 31.12.9999 remains).
    When i try to do the same via FM: BAPI_EMPLCOMM_DELIMIT, it throws an error 'EPG                  009No data stored for 0105 in the selected period' even though the record exists.
    CALL FUNCTION 'BAPI_EMPLCOMM_DELIMIT'
      EXPORTING
        employeenumber       = '00000049'
        subtype              = '0001'
        objectid             = 'P'
        lockindicator        = ''
        validitybegin        = '20100701'
        validityend          = '99991231'
        recordnumber         = '000'
        delimit_date         = '20120219'
    *   NOCOMMIT             =
    IMPORTING
       RETURN               = return.
    *   EMPLCOMMKEY          =
    Not sure how to go about it. I searched the forum which suggested to use Function Modules, but even then the issue isn't getting resolved.
    Please help.
    Martin

    Hi
    Your problem is the parameter OBJECTID It doesn't make sense to pass a 'P'.
    Other than that, you just have to lock and unlock the Personnel Number accordingly.
    Regards
    data: return type BAPIRETURN1.
    CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
      EXPORTING
        number        = '00000224'
    * IMPORTING
    *   RETURN        =
    CALL FUNCTION 'BAPI_EMPLCOMM_DELIMIT'
      EXPORTING
        employeenumber       = '00000224'
        subtype              = '0001'
        objectid             = ''
        lockindicator        = ''
        validitybegin        = '20070101'
        validityend          = '99991231'
        recordnumber         = '000'
        delimit_date         = '20120219'
    *   NOCOMMIT             =
    IMPORTING
       RETURN               = return.
    *   EMPLCOMMKEY          =
    BREAK-POINT.
    CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
      EXPORTING
        number        = '00000224'
    * IMPORTING
    *   RETURN        =

  • Need to delimit infotype pa2006 record 'HR_INFOTYPE_OPERATION'

    Hi
    I need to delimit infotype record of infotype pa2006  in my own function module.
    start date =  01.01.2009
    delimit date = 01.01.2010
    PA2006
      SELECT * FROM PA2006 INTO IT_PA2006
                    WHERE PERNR EQ PERNR
                      AND ENDDA LE '99991231'.
      ENDSELECT.
      IF SY-SUBRC = '0'.
        WA_TAB1-INFTY = '2006'.
        WA_TAB1-FNAME = 'P2006-PERNR'.
        WA_TAB1-FVAL = IT_PA2006-PERNR.
        APPEND WA_TAB1 TO IT_TAB1.
        WA_TAB1-INFTY = '2006'.
        WA_TAB1-FNAME = 'P2006-BEGDA'.
        WA_TAB1-FVAL = IT_PA2006-BEGDA.
        APPEND WA_TAB1 TO IT_TAB1.
        WA_TAB1-INFTY = '2006'.
        WA_TAB1-FNAME = 'P2006-ENDDA'.
        WA_TAB1-FVAL = IT_PA2006-ENDDA.
        APPEND WA_TAB1 TO IT_TAB1.
        WA_TAB1-INFTY = '2006'.
        WA_TAB1-FNAME = 'P2006-KTART'.
        WA_TAB1-FVAL = IT_PA2006-KTART.
        APPEND WA_TAB1 TO IT_TAB1.
        WA_TAB1-INFTY = '2006'.
        WA_TAB1-FNAME = 'P2006-BEGUZ'.
        WA_TAB1-FVAL = IT_PA2006-BEGUZ.
        APPEND WA_TAB1 TO IT_TAB1.
        WA_TAB1-INFTY = '2006'.
        WA_TAB1-FNAME = 'P2006-ENDUZ'.
        WA_TAB1-FVAL = IT_PA2006-ENDUZ.
        APPEND WA_TAB1 TO IT_TAB1.
        WA_TAB1-INFTY = '2006'.
        WA_TAB1-FNAME = 'P2006-ANZHL'.
        WA_TAB1-FVAL = IT_PA2006-ANZHL.
        APPEND WA_TAB1 TO IT_TAB1.
        WA_TAB1-INFTY = '2006'.
        WA_TAB1-FNAME = 'P2006-DESTA'.
        WA_TAB1-FVAL = IT_PA2006-DESTA.
        APPEND WA_TAB1 TO IT_TAB1.
        WA_TAB1-INFTY = '2006'.
        WA_TAB1-FNAME = 'P2006-DEEND'.
        WA_TAB1-FVAL = IT_PA2006-DEEND.
        APPEND WA_TAB1 TO IT_TAB1.
    ENDIF.
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        INFTY                  = 2006
        NUMBER                 = PERNR
       SUBTYPE                = IT_PA2006-SUBTY
      OBJECTID               =
      LOCKINDICATOR          =
       VALIDITYEND            = DATE
       VALIDITYBEGIN          = IT_PA2006-BEGDA
      RECORDNUMBER           =
        RECORD                 = IT_TAB1
        OPERATION              = 'MOD'
      TCLAS                  = 'A'
      DIALOG_MODE            = '0'
      NOCOMMIT               =
      VIEW_IDENTIFIER        =
      SECONDARY_RECORD       =
    IMPORTING
       RETURN                 = RETURN
      KEY                    =
    Why it is not delimit the infotype record. Let me know if any other way to do the same.

    Hi friend please do this
    "Need to lock the employee before delimiting
    CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
        EXPORTING
          number        = px_infty_key-pernr
    IMPORTING
           return       = px_bapireturn.
    "in the 'HR_INFOTYPE_OPERATION' we need to specify all the details of the infotype what i have mentioned belo
      CHECK px_bapireturn-type NA 'AEX'.
      CLEAR: px_bapireturn.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'       " Updation of Employee Record
        EXPORTING
         infty                  = px_infty_key-infty
         number                 = px_infty_key-pernr
         subtype                = px_infty_key-subty
         objectid               = px_infty_key-objps
         lockindicator          = px_infty_key-sprps
         validityend            = px_infty_key-endda     "just give the date which you want to delimit with
         validitybegin          = px_infty_key-begda
         recordnumber           = px_infty_key-seqnr
         record                 = px_infty_data
         operation              = lc_mod
         tclas                  = 'A'
         dialog_mode            = '0'
         nocommit               = space
       IMPORTING
         return                 = px_bapireturn
         key                    = px_bapikey.
    "Unlock the employee after the operation
      CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'       " Unlock the Employee Record
        EXPORTING
          number        = px_infty_key-pernr.
    I think will will solve your problem.
    Just try it and let me know if you have any issues.
    Thanks and Regards,
    Sri Hari Anand Kumar

  • Infotype 1613  - Worker's Comp Override Duplicates

    We are assigning Worker's compensation codes to Position . It was discovered that the Worker's Comp Override (in OM) allows for overlapping records. How I can configure Infotype 1613 that It should not allow for overlaps,  there should not be more then one that ends in 12/31/9999 (there can be gaps)? I tried to maintain Time constrain on Infotype level but it did not work. Any ideas.
    Thank you in advance,
    Rena

    Hi,
    I believe Time Constraints should solve your issue.
    Which time constraint you used and how you used?
    Let me know
    Thank You,

  • Delimit Infotype

    Hello All
    I have IT210 which pops up if i do any Action but when new record is created its not delimiting, Time Constraint for this infotype is 2. In previous threads i can see Operation LIS9, will that be  good option or any other way out?
    Thanks
    A.

    Hi Tarangini,
    Your Objective is to delimit the infotype 0167 - Health Plans -
    This would mean that you want to delimit and create a new record with a new dependent coverage option.
    If thats the case, the simple solution would be:
    1. Maintain an Adjustment Reason for Change of Coverage
    2. Once maintained, this should call HRBEN0001 program wherein you can enroll with new Coverages...
    3. Use HRBEN0014, Terminate the PERNR from the Previous Benefit Plans.
    In your case, you will have to do all these at one go.
    You may also want to have a look at this link (Delimiting IT0167 using Dynamic Actions)..
    [Re: Delimit health benefits last day of month using dynamic actions;
    Hope this helps.!!!!
    Good Luck !!!
    Kumarpal Jain.

  • BAPI to delimit Infotype 0017.

    Hi All
    Is there any BAPI to delimit the Infotype 0017? Is yes, please provide me with a sample code of what all values to pass.
    I tried searching on the forums but couldn't get it.
    Thanks in advance.
    Harsh

    Hi,
    1.Check the time Constraint of infotype 17.
    2.You can use Function Module -
        call function 'HR_INFOTYPE_OPERATION'
             exporting
                  infty         = '0017'
                  number        = employeenumber
                  validityend   =   validityend ( delimit date
                  validitybegin =  validitybegin
                  record        = p0017 (infotype 17 record)
                  operation     = 'MOD'
                      tclas         = 'A'
             importing
                  return        = ls_return
                    key           = lv_emplcommkey.
             exceptions
                  others        = 0.
    Or operation 'LIS9'
    Regards,
    Manoj.

  • Funtion module to delimit infotype 167

    Hello Gurus,
    Is there any function module to delimit automatically infotype 167 ???
    Best Regards
    Bruno Silva

    Hi,
    Pls refer to the following FM, it may help you
    CRM_CP_DELIMIT_POSITION
    RH_BUF_DELIMIT_USER_POSITIO
    RH_DELIMIT_POSITION_OF_USER
    RPM_BUPA_DELIMIT_POSITION
    regards
    ravi

  • Delimit several infotypes for Leaving Action

    Hi,
    I would like to know how to 'Send' or call a backend program to delimit infotypes called during the leaving action of the employee. thus calling several infotypes but sometimes configured in such a way it is dependent on the status of the EE or have PY record.
    Thanks!

    Hi Binoj,
    thx. i tried this:
    0000              MASSN     06     0     *     * TERMINATION - DELIMIT RECORDS*
    0000              MASSN     06     10     P     T001P-MOLGA='34'
    0000              MASSN     06     20     P     P0000-MASSN='10'
    0000              MASSN     06     30     I     LIS9,9021,,,,,(P0000-BEGDA)
    0000              MASSN     06     40     I     LIS9,9022,,,,,(P0000-BEGDA)
    0000              MASSN     06     50     I     LIS9,9023,,,,,(P0000-BEGDA)
    0000              MASSN     06     60     I     LIS9,9024,,,,,(P0000-BEGDA)
    delimit process has been done..
    but we still have to input delimit date
    btw what is '/D' for?
    looking forward to hearing from you.
    best regards,
    dhenny muliawaty (pei pei)

  • Issue with Delimiting Infotype 169

    Hi All,
    I am trying to delimit Infotype 169. It's working fine.
    We also have Change Document Logging on. It is storing all changes to IT 169 except delimit action.
    Any inputs will be helpful.
    Regards,
    Amit Khare

    Try out by creating LSMW for your scenario ....
    for any clarifications can reach out..
    rgds:
    kkreddy

  • AEDTM no change to the new date when delimit done

    Hai,
    I have a question and would like to know whether it is a std SAP behavior or not? Where the delimit function (example delimit infotype 0014) is changing to new change date at field AEDTM? It's the same date which the record was created earlier or not? At field AEDTM it's look like the new changing date is not appear and its hard for user to define when was the action has been delimited.
    For info report S_AHR_61016380 - Logged Changes in Infotype Data, still not able to meet our user needs.
    Is there any notes or patch that need to be apply to address this problem?

    Hi Marini,
    As of release 4.0A the logic is that if the CONTENT of an infotype          
    record is changed the new UNAME and AEDTM are stored in the record.         
    If only the validity range of an infotype record changes by copying, or     
    by the delimit functionality the former UNAME (and AEDTM) stays.                                                                               
    That means: If the function delimit is used, or if for an infotype with     
    time constraint 1 or 2 a new record is created which delimits a former      
    record for the delimited record the former values of UNAME and AEDTM        
    are still stored and not updated.                                                                               
    The fields "changed by" (UNAME) and "changed on" (AEDTM) are only           
    updated, when a field other then 'end date' (ENNDA) has been changed.                                                                               
    To further clarify, if you use transaction PA30 and the function            
    'Change', the fields UNAME and AEDTM will be updated.  It is with         
    the function 'Delimit' that only the end date of the infotype               
    will change.                                                                               
    If you want to store the information when and by whom an infotype has       
    been changed, you can activate the infotype change documents which is       
    designed for the tracking of changes on infotype records.                                                                               
    The IMG Path is: Pers Mngt > Pers Admin > Tools > Revision > Set up         
    Change Document.                                                                               
    Some further explanation is provided in note 333493.                        
    However if you want the old functionality back, please have a look at       
    the other note I attached, 353788.                                                                               
    An important issue to keep in mind when you implement the changes of        
    this note 353788, is that these source corrections will NOT be taken up     
    in SAP standard and also not be delivered by HR Support Package.            
    Regards,
    Ana

  • PA30 Initial Screen - need to take off /delimet  infotype menu group

    Hi All,
    If i want to take off / delimit infotype menu group from PA30 screen ( for example - I dont want user to see Gorss/net payroll and Net Payroll infotype tabs)
    can any one please guide me how to do that?
    Regards,
    Amit

    Manu,
    Well....  even after checking off the user dependency for some of infotypes, i can still see them on pa30 screen,,?
    So i was wondering if there some more steps to be done?
    Regards,
    Amit

  • Workers Comp 1613 and V_t5u28

    I am trying to maintain master data in our QA client in PP02 for Workers Comp to test out the functionality.
    I go to PP02.  Enter 01 as Current Plan, S as object type, and an object ID of a position in the system.  Then I choose infotype 1613, Planning status 1 and try to add a record. It allows me to enter data but when I save it prompts me for a transport.  I do not want to transport this data because I want to maintain it in Production.
    However, when I do the same thing in Dev it does not prompt me for a transport.
    Any thoughts?

    Yes, it was a change the Basis team had to make directly in QA and Prod to change the settings of one of the tables used to allow changes to be made to the table.  I 'm not sure what the table/view is.
    I hope that helps out some- I just posted this question for another team member and so that is all the information I have.

  • Issue in Leaving Actiion

    Dear friends,
    Whta is the exact configuration for leaving action to delimit records.Did we assign LIS9 Operation to all infotypes or any specific infotypes.
    Once i did leaving action emp should not come under payroll process for every month
    Please giude someone to overcome this issue..
    Regrads:
    Kumar

    Hi,
    You need to make sure that employee status is "withdrawn" in IT000, then there will be no payroll run for that employee.
    You cannot delimit Infotypes 0, 1, 2, 8, others u can delimit when an employee separates from the organisation.
    Regards,
    Tomesh

  • List of Standard Reports

    Is there any transaction I can run to obtain a list of available HR standard reports within the system?
    Thanks in advance!

    Hi Some standard reports
    Program     Description
    H99CWTR0     Wage Type Reporter. Returns pay for particular wage types. To submit from new report you will need to create copy and export value to memory.
    RHGRENZ0     Delimit IT1000 and related 1001s. Program will delete any 1001 infotypes whose start date is after the delimit date.
    RHGRENZ1     Extend the end date on delimited records. Very useful when you delimit a bunch of records incorrectly, and need to change the end date.
    RHGRENZ2     Delimit infotypes (IT1001)
    RPCMPYG0     Statutory Maternity Pay(SMP)
    RPCSSPG0_HIST     Statutory Sickness History(SSP)
    RPDTRA00     List all HR transactions and there uses
    RPTPSH10     Personal work schedule, also accessed via PA20/PA30 infotype 2001
    RPUAUD00     HR Report to list all logged changes in infotype data for an employee. Uses the PCL4 Audit Cluster.
    RPUAUDDL     HR Report to delete audit data from the PCL4 Audit Cluster
    RPUDELPN     Delete all info for an employee number, including cluster data and infotypes
    RPUP1D00     View/Delete records from PCL1 Cluster
    RPUP2D00     View/Delete records from PCL2 Cluster
    RPUP3D00     View/Delete records from PCL3 Cluster
    RPUP4D00     View/Delete records from PCL4 Cluster

  • Idoc extension-- HRMD_A06

    hi all,
    iam extending the idoc hrmd_a06 for infotypes 0065,0069,0571,0570.and each infotype having 5 to 6 fields only ,pernr ,infty,begda,endda,are the comon fields.
    extension is completd.in process code  fm IDOC_INPUT_HRMD. i find a exit for in bound process .i need coding procedure to update  infotypes tables.

    Hi Venkat,
    In the exit, check the following sample code.
    READ TABLE it_idoc_contrl INTO wa_idoc_contrl WITH KEY mestyp = your message type.
    IF sy-subrc = 0.
    it_idoc_contrl[] = idoc_contrl[].
    it_idoc_data[] = idoc_data[].
      READ TABLE it_idoc_data INTO wa_idoc_data WITH KEY segnam = your relevant segment.
      IF sy-subrc EQ 0.
    do the necessary operations for your requirement.
    READ TABLE it_idoc_data INTO wa_idoc_data WITH KEY segnam = c_e1plogi ( The Header Segment ).
    populate your internal tables with the Segments data here by using the appropriate classes and methods ( which u can find very easily for ur specific requrement ).
    The FM 'HR_INFOTYPE_OPERATION' cam be used to update PA infotypes.
    Hope this helps you to some extent.
    - Surya.
    Edited by: suryaprakash gaddam on Jul 28, 2008 9:21 AM

Maybe you are looking for

  • Marketing attributes creation/update from ELM

    Hi Experts. A small question regarding the external list management. I have created a mapping format with some marketing attributes I want to create/update for a certain business partner. This works fine in the sense that the system is fully capable

  • Can't install Photoshop CS6 Extended

    I recently purchased CS6 student version for mac and get an error message that PS cannot install. Below are the error messages i keep getting are multiple attempts to install. Exit Code: 6 Please see specific errors and warnings below for troubleshoo

  • Editing from LR 4 to PS Elements 9

    Im unable to export files for editing from LR 4 into photoshop elements 9. All my settings are the same as I had with LR 3 but nothing happens, PS doesn't launch or open. ANY SUGGESTIONS???

  • Buying An ipod From Ebay

    I am considering buying a "Brand New, Still Sealed 60GB Video ipod in Black" from ebay.co.uk. In the item desciption it states that this ipod has been imported from France. 2 questions: 1. Are all ipod's universal? i.e. would this ipod function corre

  • Windows 7 x64 X-Fi drivers!!

    Assuming these board are not dead, im looking for Windows 7 (beta) drivers for my sound card is the X-Fi XtremeGamer Fatalty Pro Series i've tried using the vista driver (guess work) and it just crackled to high hell (installed via compat vista mode)