Updating infotype 0041 using HR_INFOTYPE_OPERATION?

Hi All:
How do we update the dates in infotype 0041 using HR_INFOTYPE_OPERATION? lets say we have 6 dates populated in 41 and we another employee has 9 dates populated. We are reading these records and need to update the dates for all the employee records.
Thanks
Venkata

Hi Venkata,
What you can do is use the HR_INFOTYPE_OPERATION in Change or MOD(Modify) mode i.e.
pass 'MOD' in operation parameter.
Your recordnumber parameter should have the sequence number from infotype record you are updating (field SEQNR). All other parameters should be as it is had been for INS or insert operation.
Regards.

Similar Messages

Update infotype 0041 in payroll function

Hi,
I have created a payroll function to update infotype 0041 during payroll process, but it seems this is causing some inconsistencies in PCL2 cluster,since I'm having some payroll errors.
Is there anyway to avoid this? Can I create an infotype during the payroll process, or this is not advisable?
Thanks in advance.
Best regards,
Sónia Gonçalves

You have to make the function call a separate unit of work.One other option is to put the function call in a report & SUBMIT it from the User exit.
~Suresh

Error while modifying HR infotype PA0105 using HR_INFOTYPE_OPERATION

Hello All,
I am not able to modifying the infotype PA0105.
Currently I am using the FM HR_INFOTYPE_OPERATION.
But I am not able to modify the record.
Has anyone faced any such situation...
Please help..!!
Useful pointers will be appreciated...
Thanks & Regards,
Tarun Gambhir

Hope this helps you out...
      C_INS   LIKE PSPAR-ACTIO VALUE 'INS',
      W_000-PERNR = T_SAIDA-PERNR.
      W_000-INFTY = C_0000.
      W_000-ENDDA = C_DATA.
      W_000-BEGDA = T_PA0000-BEGDA.
      W_000-AEDTM = SY-DATUM.
      W_000-UNAME = SY-UNAME.
      W_000-MASSN = C_16.
      W_000-MASSG = S_MASSG-LOW.
      W_000-STAT1 = SPACE.
      W_000-STAT2 = C_3.
      W_000-STAT3 = C_1.
      W_PSPAR-PERNR = T_SAIDA-PERNR.
      W_PSPAR-INFTY = C_0000.
      W_PSPAR-PLANS = T_P0001-PLANS.
      W_PSPAR-WERKS = T_P0001-WERKS.
      W_PSPAR-PERSG = T_P0001-PERSG.
      W_PSPAR-PERSK = T_P0001-PERSK.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          INFTY            = C_0000
          NUMBER           = T_SAIDA-PERNR
          LOCKINDICATOR    = SPACE
          VALIDITYEND      = C_DATA
          VALIDITYBEGIN    = V_BASE
          RECORD           = W_000
          OPERATION        = C_INS
          SECONDARY_RECORD = W_PSPAR
        IMPORTING
          RETURN           = T_RET_FUNC                     "#EC *
          KEY              = T_KEY.                         "#EC *
Greetings,
Blag.

Problem in updating infotype 2001

Hi Experts,
                 While i am updating infotype 2001 , using HR_INFOTYPE_operation FM it giving a error , because it calling a wrong sceen 2000 , instead of 2001 . can anybody can help on this ?
thanks and regards
Renjith MP

Hi Dude,
Go through the below code for 2002 infotype :
TYPES BEGIN OF text_version.
TYPES   nummer TYPE x.
TYPES END OF text_version.
DATA: PERSONALDATAKEY    LIKE BAPIPAKEY.
DATA: RETURN       LIKE BAPIRETURN1.
DATA: P2002       LIKE P2002.
DATA: PSKEY       TYPE PSKEY.
DATA: IT_TEXT       TYPE HRPAD_TEXT_TAB .
DATA: LINE       TYPE HRPAD_TEXT.
DATA: version       TYPE text_version.
DATA: pcl1       TYPE pcl1.Input Parameters:
PARAMETERS: PERNR LIKE PA2002-PERNR DEFAULT '1004511',
             AWART LIKE PA2002-AWART DEFAULT 'LW',
             BEGDA LIKE PA2002-BEGDA DEFAULT SY-DATUM,
             ENDDA LIKE PA2002-ENDDA DEFAULT SY-DATUM,
             BEGUZ LIKE PA2002-BEGUZ,
             ENDUZ LIKE PA2002-ENDUZ.
START-OF-SELECTION.
CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
        EXPORTING
          number = PERNR
        IMPORTING
          RETURN = RETURN.
IF RETURN-NUMBER IS NOT INITIAL.
    EXIT.
ENDIF.
* ADD DATA
CLEAR: P2002.
P2002-PERNR = PERNR.
P2002-SUBTY = AWART.
P2002-ENDDA = BEGDA.
P2002-BEGDA = BEGDA.
P2002-BEGUZ = BEGUZ.
P2002-ENDUZ = ENDUZ.
P2002-AWART = AWART.
P2002-ITXEX = 'X'.
* WRITE DATA
CLEAR: RETURN, PERSONALDATAKEY.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
         EXPORTING
              INFTY          = '2002'
              NUMBER         = PERNR
              SUBTYPE        = AWART
              VALIDITYEND    = BEGDA
              VALIDITYBEGIN = BEGDA
              RECORD         = P2002
              OPERATION      = 'INS'
              NOCOMMIT       = ''
              TCLAS          = 'A'
         IMPORTING
              RETURN         = RETURN
              KEY            = PERSONALDATAKEY
         EXCEPTIONS
              OTHERS         = 0.
IF RETURN-NUMBER IS INITIAL.
    COMMIT WORK AND WAIT.
ELSE.
    ROLLBACK WORK.
    EXIT.
ENDIF.

Modify Infty 0057 using HR_INFOTYPE_OPERATION

Hi,
I am trying to update (MOD) an 0057-infotype record using HR_INFOTYPE_OPERATION. But no matter what I do, I cannot make it work. It works with INS and COP but then I get a new entry and the old entry is not delimited. When using MOD I receive the following message in RETURN (return_struct)
TYPE          E
ID          PG
NUMBER          009
MESSAGE          No data stored for 0057 in the selected period
LOG_NO
LOG_MSG_NO          000000
MESSAGE_V1          0057
The code I am using look like this:
Do you please have any advices to give according to this?
*& Report ZHR_ESS_UPDATE_INFTY_0057
REPORT zhr_ess_update_infty_0057.
PARAMETERS: p_pernr TYPE p0057-pernr,
            p_lgarto TYPE p0057-lgart, "old lgart
            p_lgartn TYPE p0057-lgart. "new lgart
CONSTANTS: change TYPE pspar-actio VALUE 'MOD'.
DATA: lt_p0057 TYPE TABLE OF p0057.
DATA: ls_current_p0057 LIKE LINE OF lt_p0057,
      ls_new_p0057 LIKE LINE OF lt_p0057.
DATA: l_p0057 LIKE p0057.
DATA: l_subrc LIKE sy-subrc.
DATA return_struct LIKE bapireturn1.
DATA w_return TYPE bapireturn1.
DATA: bapipakey_tab LIKE bapipakey OCCURS 0 WITH HEADER LINE.
DATA: validitybegin TYPE sy-datum,
      validityend   TYPE sy-datum.
CALL FUNCTION 'HR_PSBUFFER_INITIALIZE'.
CALL FUNCTION 'HR_READ_INFOTYPE'
EXPORTING
    tclas           = 'A'
    pernr           = p_pernr
    infty           = '0057'
IMPORTING
    subrc           = l_subrc
TABLES
    infty_tab       = lt_p0057
EXCEPTIONS
    infty_not_found = 1
    OTHERS          = 2.
* Enqueue personnel number
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
EXPORTING
    number = p_pernr
IMPORTING
    return = w_return.
READ TABLE lt_p0057 INTO ls_current_p0057 INDEX 1..
ls_new_p0057-begda = sy-datum.
ls_new_p0057-endda = '99991231'.
ls_new_p0057-subty = p_lgartn.
ls_new_p0057-lgart = p_lgartn.
ls_new_p0057-mgart = p_lgartn.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
    infty         = '0057'
    subtype       = ls_current_p0057-subty
    objectid      = ''
    lockindicator = ''
    number        = ls_current_p0057-pernr     "employeenumber
    validityend   = ls_current_p0057-begda
    validitybegin = ls_current_p0057-endda
    record        = ls_new_p0057
    recordnumber = ls_current_p0057-seqnr
    operation     = change                     "MOD
    tclas         = 'A'
    nocommit      = '1'
    dialog_mode   = '0'
*   view_identifier = '23'
IMPORTING
    return        = return_struct
    key           = bapipakey_tab
EXCEPTIONS
    OTHERS        = 0.
IF return_struct IS INITIAL.
COMMIT WORK.
ENDIF.
* Enqueue personnel number
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
EXPORTING
    number = p_pernr
IMPORTING
    return = w_return.

Hi,
This was kind of embarrassing. Thanks for finding the error!
Kind regards
Andreas

HRMD_A07 Idoc to update InfoType 0014 does not delimit existing PA0014 rec

In ECC 6.0, we are using HRMD_A07 Idoc to update infotype 0014 using update data received from a third party application. In XI, I am creating the Idoc with Update Code "U" with E1PLOGI, E1PITYP and E1P0014 segments. E1P0014 holds the data for the latest record.
If I directly pass the Idoc thru ALE layer, It creates records for the new date range on E1P0014 segment, but does not delimit the previous record by changing its end date. This results in two records in PA0014 with end date of 12/31/9999 - which is wrong.
I also tried using a wrapper FM to create additional segments in the Idoc representing the existing record in PA0014, with the end date being delimited to incoming record's beg. date minus 1.
This also results in just creating two additional records in PA0014 corresponding to the two segments in Idoc while existing record in PA0014 stays intact resulting in two records with end date 12/31/9999.
I also experimented with setting the lock indicator (PA0014-SPRPS) but that also does not result in delimiting the existing record.
Am I missing something? Is there a piece of config that controls this?
Regards,
The time constraint on 0014 is "2"

Hi Jon and Ashish,
I too am facing the same issue that the new IDOC is not delimiting the previous record.
Can you explain how did u get over you issue.
I'm maintaining the same dates in E1PITYP and in E1P0014.
Thanks,
Jilly

Multiple date instances in infotype 0041

Has anyone configured infotype 0041 using delimted dates to track original hire date, termination date, and the re-hire date. For example, the orignal date specification for orginal hire date to the termination date, and then another date specification for a re-hire date and termination date for as many times as an individual came back.

Hi
You have to check your Dynamic action.
While querying dynamic ation how did you quaried, on which grouping you quried ?
The employee who dont get the details are members in that group are not?
if you give it in feature you must have all 4 dates to all the employees, otherwise you will be in trobuble
becuase SAP wont allow you fill the type only without date in infotype 0041
Regards
Adi

Update Infotype 1016

Hi,
I have to update Infotype 1016 using the BAPI FM "BAPI_HRMASTER_SAVE_REPL_MULT".
Two tables need to get updated, HRP1016 & HRT1016.
The Data in the HRT 1016 is a Table Data for Record in HRP1016.
Say: Orgunit O 10000001 has two standrd Profiles..
IF I go to PP01 and create the two standard profiles,
I will have a single record in HRP1016 which has a TABNR field value generated.
Now for this TABNR, I have two record in HRT1016 each corresponding to one Profile.
I need to create these three ( 1 + 2 ) entries using the FM. The FM has Input structure BAPIHR1016 which allows only one profile per structure. Also it asks for the TABNR field, which I donot know until the actual creation.
If I send one profile & TAB_SEQNR as 00001, its working fine, generating a TABNR for me.
But when I send two records in the FM, one with TAB_SEQNR 00001 & other with TAB_SEQNR 00002, the second one is overwriting the first one, and I have only the second profile assigned.
Please help solve this issue.
Thanks in Advance.
Suryakiran D.

For updating the IT 1011, we have 6 fields in the BAPI.
But when I go to PP01, i have only one field in input mode, rest all are disabled for input.
Even if I fill the values in all the fields, only one is considered for update, and rest all are recalculated using this.
Can someone please let me know how we can decide this.
Thanks,
Surya

Updating Infotype using function module HR_INFOTYPE_OPERATION

Hi There ,
lets understand my problem related to updation of infotype .
I have a record maintained in my table within date range 01/04/2010 to 31/12/9999.
now i update my new tax rate from 1st June 2010 .
The requirement is i shall two records now :
First record from 01/04/2010 to 31st may 2010 shall be maintained .
hence we need to modify the existing record only changing the end date .
Second record will be a new record starting from 1st june , ending 31/12/9999.
Approach followed by me :
using HR_READ_INFOTYPE to read the data .
Then using HR_INFOTYPE_OPERATION
---> ACTION : "MOD" to update existing record by passing end date as 31st may 2010 .
Then using action : INS to create a new record .
but this approach is failing since i am itself not able to modify the existing record .
Please let me know the correct way of updating the record .
Regards,
Abhishek.

It depends on infotype. Every infotype has a time link.
Sometimes you can have a record for a day or more than one. You can have continuous records or not.
I think your infotype has class 1 and it's continuous in time to the end (99991231)

Issue with Dynamic Actions - Infotype 0041 Updation

Hi All,
Requirement :
I have to update the Date type-13 ( Resignation Date - DAR11 ) without Date ( DAT11 as Blank value - User will fill through Infogroup ) while performing the Termination action through PA40.
Added below code in V_T588z (0000):
I have added 186,188 Lines.Other lines are standard thing.
              04     180     P     PSPAR-MASSN='10'/X **Termination
              04     181     P     PSPAR-MASSN='ZB'/X **Termination
              04     182     P     PSPAR-MASSN='14'/X **Termination
              04     185     I     COP,41,,,(PSPAR-BEGDA),(PSPAR-ENDDA)/D
              04     186     W     P0041-DAR11='13' **BEGIN & END OF CRA01670 CODE ***
              04     188     W     P0041-DAR11='' **BEGIN & END OF CRA01670 CODE ***
Issue :
1. The above logic is not working for Finland ,other countries. For only India it is working.
2. Some times Date type-13 is coming twice while through the Infogroup-0041 screen twice,which is incorrect. The infotype-0041 should call only once.I have checked the User parameters,MOLGA,USR. But it is not working.
2. The standard configuration Date type -09-Last day of work - is working fine . But i could not be able to find ,from where it is coming.I have checked the Dynamic actions,but no use.
Need your inputs to solve the issue.
Thanks,
N.L.Narayana

P     P0000-MASSN='01'    Action type
P                   P0000-MASSG="01"   Action Reaosn
P     T001P-MOLGA='40'
F                   here u will keep the Call Routine
I     INS,2001,,,(P0000-BEGDA),(P0000-ENDDA)/D (here u have pass the date of Call routine )
W     P2001-IAWRT='01'
But here Infotype 2001 we will give Absence type this IT is used for Booking Absence Types i did not get the Wage type 8001
thru which IT are u processing it
for more info Checjk Tabvke V_T588Z here iam pasteing the sample call routine which i got from earlier thread
Create a Program (Subroutine) using SE38. Save and activate it.
ZZSY_DYA_TEST2
REPORT ZZSY_DYA_TEST2.
tables : p0000,p0001,rp50d.
FORM getdate.
rp50d-date1 = p0000-begda + 90.
ENDFORM.
FORM get_date.
rp50d-date2 = p0000-begda + 180.
ENDFORM.

Updating hr infotype pa0305 with 'HR_INFOTYPE_OPERATION'

Hi everyone i'm trying to update hr infotype pa0305 using fm HR_INFOTYPE_OPERATION but it doesn't work maybe using in worng way.
Maybe someone knows how can i use the second structure q0305 passing trough the parameter called "secondary records".
Thanks in advance,

Sorry for the late, the problem was that the part structure of p305 is empty; the part of wage type and amount exactly.
CLEAR lv_return .
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        infty                  = '0305'
        number                 = wa_alvgrid2_error-pernr
        subtype                = ''
        OBJECTID               =
        LOCKINDICATOR          =
       validityend            = wa_alvgrid2_error-endda
       validitybegin          = wa_alvgrid2_error-begda
        RECORDNUMBER           =
        record                 = st_0305
        operation              = 'INS'
        tclas                  = 'A'
        dialog_mode            = '2'
         nocommit               = ' '
        view_identifier        = '15'
        secondary_record       = st_q0305
     IMPORTING
       return                 = lv_return
        KEY                    =.
maybe I am in wrong when I pass the secondary record.

Creating an Infotype Record 0019 using HR_INFOTYPE_OPERATION

All,
I have written a little test application for this, my code is below, and there is something funny happening. For some reason when I run the program for the first time it creates the 0019 infotype but it doesn't add on the additional text. However if I run the program again, without doing anything else, the text does get updated.
It appears that I am missing a commit statement or something along those lines but I am not sure.
I would appreciate any help on getting this working
Many Thanks,
Colm
DATA t0019 TYPE TABLE OF p0019.
DATA w0019 TYPE p0019.
DATA in_pernr TYPE prelp-pernr.
in_pernr = '02000305'.
BREAK-POINT.
CALL FUNCTION 'HR_READ_INFOTYPE'
EXPORTING
*   TCLAS                 = 'A'
    pernr                 = in_pernr
    infty                 = '0019'
   begda                 = '18000101'
   endda                 = '99991231'
*   BYPASS_BUFFER         = ' '
*   LEGACY_MODE           = ' '
* IMPORTING
*   SUBRC                 =
TABLES
    infty_tab             = t0019
EXCEPTIONS
   infty_not_found       = 1
   OTHERS                = 2.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
BREAK-POINT.
DATA in_infty TYPE prelp-infty VALUE 0019.
DATA in_subty TYPE p0001-subty VALUE 02.
DATA wa_return1 TYPE bapireturn1.
DATA wa_pakey TYPE bapipakey.
DATA wa_pskey TYPE pskey.
DATA l_pgmid TYPE old_prog.
DATA it_text TYPE hrpad_text_tab.
DATA wa_text TYPE hrpad_text.
wa_text = 'Line 1'.
APPEND wa_text TO it_text.
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
EXPORTING
    number = in_pernr
IMPORTING
    return = wa_return1.
IF NOT wa_return1 IS INITIAL.
*ERROR MESSAGE
ENDIF.
w0019-pernr = in_pernr.
w0019-subty = '02'.
w0019-infty = '0019'.
w0019-endda = '20081204'.
w0019-begda = '20081204'.
w0019-seqnr = '000'.
w0019-aedtm = sy-datum."CREATED DATE
w0019-uname = sy-uname.
w0019-itxex = 'X'.
w0019-tmart = '02'. "TASK TYPE
w0019-termn = '20081204'. "DATE OF TASK
w0019-mndat = '20081203'. "REMINDER DATE
w0019-tmjhr = '2008'. "DATE OF TASK YEAR
w0019-tmmon = '12'. "DATE OF TASK MONTH
w0019-tmtag = '04'. "DATE OF TASK DAY
w0019-mnjhr = '2008'. "REMINDER DATE YEAR
w0019-mnmon = '12'. "REMINDER DATE MONTH
w0019-mntag = '03'. "REMINDER DATE DAY
BREAK-POINT.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
    infty         = '0019'
    number        = in_pernr
    subtype       = '02'
    validityend   = sy-datum
    validitybegin = sy-datum
    record        = w0019
    operation     = 'INS'
IMPORTING
    return        = wa_return1
    key           = wa_pakey
EXCEPTIONS
    OTHERS        = 0.
IF NOT wa_return1 IS INITIAL.
*ERROR HANDLING
ELSE.
*SUCCESS
wa_pskey-pernr = wa_pakey-employeeno.
wa_pskey-infty = '0019'.
wa_pskey-subty = wa_pakey-subtype.
wa_pskey-objps = wa_pakey-objectid.
wa_pskey-sprps = wa_pakey-lockindic.
wa_pskey-endda = wa_pakey-validend.
wa_pskey-begda = wa_pakey-validbegin.
wa_pskey-seqnr = wa_pakey-recordnr.
l_pgmid = 'SAPFP50P'.
BREAK-POINT.
TRY.
    CALL METHOD cl_hrpa_text_cluster=>update
      EXPORTING
        tclas         = 'A'
        pskey         = wa_pskey
        histo         = 'X'
        uname         = sy-uname
        aedtm         = sy-datum
        pgmid         = l_pgmid
        text_tab      = it_text
        no_auth_check = 'X'.
ENDTRY.
IF sy-subrc EQ 0.
*SUCCESS
ENDIF.
ENDIF.
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
EXPORTING
    number = in_pernr
IMPORTING
    return = wa_return1.
BREAK-POINT.

[url]HR_INFOTYPE_OPERATION is not working in user exit ZXPADU02[url]
If you do this and then update the text using the update task it should work perfectly.

Using hr_infotype_operation to update it0021 problem

I am using hr_infotype_operation to update data for it0021 and it0528.
In pa30, just in it0021 and different to update data for it0021 and it0528, IT0528 is not allowed maitain
when i am using hr_infotype_operation to update data for it0021 and it0528 one by one, the problem occurs, it 0528 is not update.
Any idea?

Hi,
The FM HR_INFOTYPE_OPERATION infact copy a BDC & performs all the screen validations that normally occur in PA30. It uses the CALL DIALOG option.
Also, set the MODE to '2' which is like the display ALL option in the CALL TRANSACTION.
This will let you see the error in the foreground.
Regards,
Shamma

Problem in changing end date of PA-Infotype using HR_INFOTYPE_OPERATIONS .

Hi All,
I am trying to change the end date of an active record in an infotype using HR_INFOTYPE_OPERATIONS FM. But am getting an error, 'Infotype does not exist'.
I am using operation as 'MOD' and passing appropriate parameters as required.
it would be great if someone can help me out to understand, why could that error be coming?

Hi Santosh,
With this FM you cannot change the enddate as enddate is a key field and used to determine the exact record in the database.
Why don't you use PA30 to change end date of an infotype record?
Or else delete the row first w. HR_INFOTYPE_OPERATION DEL and insert it again with INS operation and new end date.
Regards,
Dilek
Edited by: Dilek Ersoz Adak on Jan 8, 2010 7:54 AM

DELETE infotype 0000 using HR_MAINTAIN_MASTERDATA or HR_INFOTYPE_OPERATION

Please kindly help ,
how to delete infotype using HR_MAINTAIN_MASTERDATA or HR_INFOTYPE_OPERATION?
i did try to use HR_INFOTYPE_OPERATION but return code shown as :
"No data stored for 0003 in the selected period"
but when i try using HR_MAINTAIN_MASTERDATA.
Return code was zero, and infotype 0000 still exist.
regards,
Rudy.

Here you go Rudy
Loopt at the your internal table. Lock the user, post or delete the record, unlock the user.
CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
      EXPORTING
        number       = t_file-pernr
      IMPORTING
        return       = t_return
        locking_user = w_uname.
    IF t_return-number IS NOT INITIAL.
      t_return-message_v1 = t_file-pernr.
      APPEND t_return.
      g_fail = g_fail + 1.
      g_flag = 'X'.
    ELSE.
      CLEAR: t_return, personaldatakey.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
          EXPORTING
            infty         = '2006'
            number        = t_file1-pernr
            subtype       = t_file1-subty
            validityend   = t_file1-endda
            validitybegin = t_file1-begda
            record        = p2006
            operation     = 'DEL'
            dialog_mode   = '1'
            nocommit      = ' '
          IMPORTING
            return        = t_return
            key           = personaldatakey.
      IF t_return-number IS NOT INITIAL.
        t_return-message_v1 = t_file-pernr.
        APPEND t_return.
        g_fail = g_fail + 1.
        g_flag = 'X'.
      ELSE.
        MOVE-CORRESPONDING t_file TO t_file1.
        APPEND t_file1.
        g_success = g_success + 1.
      ENDIF.
      "Unlock the employee
      CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'
        EXPORTING
          number = t_file-pernr
        IMPORTING
          return = t_return.
Please award points if useful.
Thanks, Raj

Updating infotype 0041 using HR_INFOTYPE_OPERATION?

Similar Messages

Maybe you are looking for