HR_INFOTYPE_OPERATION not working in badi HRBAS00INFTY

Hi All,
I need to create a record in IT0019 when IT0024 is updated.
For that purpose I have created an implementation of badi HRBAS00INFTY and added my code in method IN_UPDATE.
I try to create the record in IT0019 using FM HR_INFOTYPE_OPERATION.
The problem is that the record is not created but the FM doesn't return any error( return param is empty ).
I added 'commit WORK.' after the FM but this doesn't work neither.
Do you have any idea why ths FM is not working in the badi.
kr
Karim

Hi,
Try with the BADI HRPAD00INFTY, If it not working try creating dynamic action for INFTY 0024.
Dynamic actions : SPRO -> SAP Reference IMG -> Personnel Management -> Personnel Administration - >Customizing procedures -> Dynamic Actions.
~~~ Ganesh Kumar K.

Similar Messages

RH_INSERT_INFTY is not working in BADI

Hello.
I've got the following issue:
I'm using RH_INSERT_INFTY within a BADI, just to limit a record in INFTOTYPE 1000 and is not working, even i don't get any error messages.
The thing is that i'm using the same function within a single report and works fine, it looks like the behaviour of the FM is different within a BADI (I guess).
Any ideas?

I'm locking the object in a previous form.....
FORM infotipo_1010
            USING p_plaza TYPE objektid
                   p_fecha TYPE datum
                   p_plvar TYPE plvar..
DATA:    l_t_hrp1010         TYPE STANDARD TABLE OF p1010,
           l_t_aux_hrp1010     TYPE STANDARD TABLE OF p1010,
           l_wa_t_hrp1010      TYPE p1010,
           l_wa_t_aux_hrp1010 TYPE p1010,
           l_t_objects         TYPE STANDARD TABLE OF hrobject,
           l_wa_t_objects      TYPE hrobject.
l_wa_t_objects-plvar = p_plvar.
l_wa_t_objects-otype = 'S'.
l_wa_t_objects-objid = p_plaza.
APPEND l_wa_t_objects TO l_t_objects.
CALL FUNCTION 'RH_READ_INFTY'
   EXPORTING
   AUTHORITY                  = 'DISP'
   WITH_STRU_AUTH             = 'X'
     infty                      = '1010'
   ISTAT                      = ' '
   EXTEND                     = 'X'
   SUBTY                      = ' '
   BEGDA                      = '19000101'
   ENDDA                      = '99991231'
   CONDITION                  = '00000'
   INFTB                      = '1'
   SORT                       = 'X'
   VIA_T777D                  = ' '
   TABLES
     innnn                      = l_t_hrp1010
     objects                    = l_t_objects
    EXCEPTIONS
     all_infty_with_subty       = 1
     nothing_found              = 2
     no_objects                 = 3
     wrong_condition            = 4
     OTHERS                     = 5
IF sy-subrc = 0.
    SORT l_t_hrp1010 BY subty endda ASCENDING.
    LOOP AT   l_t_hrp1010
         INTO l_wa_t_hrp1010.
      l_wa_t_aux_hrp1010 = l_wa_t_hrp1010.
      AT END OF subty.
        l_wa_t_aux_hrp1010-endda = p_fecha.
        REFRESH: l_t_aux_hrp1010.
        APPEND l_wa_t_aux_hrp1010 TO l_t_aux_hrp1010.
        CALL FUNCTION 'RH_INSERT_INFTY'
           EXPORTING
             fcode                     = 'CUTI'
             vtask                     = 'B'
           ORDER_FLG                 = 'X'
           COMMIT_FLG                = 'X'
           AUTHY                     = 'X'
           PPPAR_IMP                 =
           OLD_TABNR                 = ' '
           REPID                     = ' '
           FORM                      = ' '
           KEEP_LUPD                 =
           WORKF_ACTV                = 'X'
           TABLES
             innnn                     = l_t_aux_hrp1010
             ilfcode                   = l_t_objects
          EXCEPTIONS
             no_authorization          = 1
             error_during_insert       = 2
             repid_form_initial        = 3
             corr_exit                 = 4
             begda_greater_endda       = 5
             OTHERS                    = 6.
      ENDAT.
    ENDLOOP.
ENDIF.

HR_INFOTYPE_OPERATION not working when editing HR master data

Hi all,
I search for similar problem but couldn't find any.
I am using HR_INFOTYPE_OPERATION to insert record to an infotype. I proceed with standard way (ENQUEUE employee, call above fm, DEQUEUE employee). It works fine when running as executable program.
Now I want this functionality when editing EE's master data (i.e. modifiying one infotype record). For this I put the same code to some user exit. Now when executed I can proceed with creating new entry, it saves I can see how data are updated in pa30 for this EE. But when I reenter his master data are without this new record anymore.
Does anyone faced similar issue? I guess it is not allowed to use that fm when editing master data, but can't find a answer if this is the issue.
I did also a test creating this new entry for some different EE, but it neither worked.
Any info appreciated.
Thank you
Marcin

Hi Marcin,
Please check whether the following links are useful,
HR_INFOTYPE_OPERATION mod not working
HR_INFOTYPE_OPERATION is not working in user exit ZXPADU02
Best Regards.

NOCOMMIT in hr_infotype_operation not working

Hi,
I am using HR_INFOTYPE_OPERATION, and passing nocommit as 'X', still the record is being created.
Have searched on SDN, but could not get the asnwer, Can anyone please help me.
Thanks and Regards
Manu

Hi Manoj,
I had checked LUW_MODE in both server A and B.
LUW_MODE = 0 in both server A and B.
The data was updated to the PA0002 table after calling this FM HR_MAINTAIN_MASTERDATA.
During debug, the runtime logic fullfilled the first IF condition (IF RETURN is INITIAL), therefore it did NOT go into
ELSE part   ( IF NOT NOCOMMIT IS INITIAL. ROLLBACK WORK. ENDIF. )
IF RETURN IS INITIAL.
    READ TABLE MODIFIED_KEYS INDEX 1.
    MOVE MODIFIED_KEYS(8) TO KEY(8).
    MOVE MODIFIED_KEYS+12 TO KEY+8.
ELSE.
    IF NOT NOCOMMIT IS INITIAL.
      ROLLBACK WORK.
    ENDIF.
ENDIF.
This is weird, looks like LUW_MODE = 0 is not working in FM HR_MAINTAIN_MASTERDATA, data is still get updated to PA0002 even with LUW_MODE = 0.
Any idea or suggestion that I can use to solve this? Is there any config on the LUW that I need to perform?
Thanks a lot.

Macbook pro camera not working -- very bad support

I have a macbook pro bought around October 2010. It has 3 years international warranty.
Few months back when I wanted to use skype, I figured out that the camera is not working. Took it to Apple care centre in Bangalore.
They found the camara to be defective. From their notes
" Reset SMC and PRAM. No go. Tried with known good OS. No go. Found camera not detected in system profiler. Checked with known good display. Camera working. Denied coverage as dent on the display clamshell"
Chatted with the relationship officer Joana,
1. I fail to understand that replacing the camera requires relplacing the whole display
2. Small scrach (can send the picture to you) on the outer cover of teh display is not the root cause of the camera not working
3. Display is working perfectly fine. Only camera not working
The relationship officers are such dumb and techically challenged people, that they fail to understand the real issue and instead just try to console you.
If camera is not working due to a defect, it needs to be replaced in warranty, if Apple's design dictates camera replacemnt to the whole display replacement, so be it.
Due to my feedback, some of my colleges (10+ guys) took Macbook pro. Extreamely dis-satisfied with the support cell and their techical abilities. Did not expect this from Apple. Will not take any Apple product and will not recommend anyone. Thinkpad rocks!!

read this: http://support.apple.com/kb/ht2090

HR_INFOTYPE_OPERATION not working when called from Dynamic action

Hi ,
       Senario : I would like to execute a form from dynamic action which
creates a record in 0015 (Additional payment IT) .
       I have writen the code as shown below am using FM HR_INFOTYPE_OPERATION
. When i execute the program from se38 it is creating a record, however it is
not created when it is called from dynamic action..when i debugged the code in
inside the FM HR_INFOTYPE_OPERATION there is a FM HR_MAINTAIN_MASTERDATA where
they are using call dialog (statement) and
sy-oncom = 'N'   when called from Dynamic action and
sy-oncom = 'S'   when called executed directly.
I tried to change the sy-oncom to S while run from Dynamic action it created
the record.
So Can anyone explain me abt sy-oncom and how can i resolve the issue..
code..
REPORT ZHRPYENH01 .
perFORM TERMIATION_9000.
INCLUDE DBPNPMAC.
      FORM Termiation_9000                                          *
FORM TERMIATION_9000.
INFOTYPES : 0015.
*data : i .
*i ='c'.
*break-point.
*message i000(000) with i.
TABLES : PRELP.
DATA : P9000 TYPE PA9000." with header line.
DATA : P0000 TYPE STANDARD TABLE OF P0000 WITH HEADER LINE.
DATA : P0015 TYPE STANDARD TABLE OF P0015 WITH HEADER LINE.
DATA : HIRE_DATE LIKE SY-DATUM,
         TERM_DATE LIKE SY-DATUM.
DATA : MOLGA LIKE T500L-MOLGA VALUE '25',
         SEQNR LIKE PC261-SEQNR.
DATA : RGDIR TYPE STANDARD TABLE OF PC261 WITH HEADER LINE.
DATA : ACTUAL_PERIOD LIKE PA9000-RETENTION.
DATA : PNP-SW-FOUND TYPE SY-SUBRC ,
         PNP-SY-TABIX TYPE SY-TABIX.
DATA : TER_PERNR LIKE PA0001-PERNR.
DATA : REF_PERNR LIKE PA0001-PERNR.
data : key type BAPIPAKEY.
data : payed_amount type p0015-BETRG.
data : future_payment_amount type p0015-BETRG.
data : p0002 like pa0002.
types : begin of t_deduction ,
          deducation_date like p0015-begda,
          future_payment_amount type p0015-BETRG.
types : end of t_deduction.
data : future_deduction type standard table of t_deduction with
*header line.
data : future_deduction type t_deduction .
data : RETURN type BAPIRETURN1.
*data : deduction_p0015 like standard table of p0015 with header line.
data : deduction_p0015 like p0015 .
xxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxx
****Prepare 0015 data for deduction
*deduction for payed amount
clear deduction_p0015.
*refresh deduction_p0015.
deduction_p0015-pernr = REF_PERNR.
*deduction_p0015-pernr = TER_PERNR.
deduction_p0015-lgart = 'M120'.
deduction_p0015-begda = sy-datum + 1 .
deduction_p0015-endda = sy-datum + 1 .
deduction_p0015-BETRG = payed_amount.
deduction_p0015-WAERS = 'SGD'.
deduction_p0015-ZUORD = TER_PERNR.
*append deduction_p0015.
**deduction for future payment amount
*loop at future_deduction.
*clear deduction_p0015.
*deduction_p0015-pernr = REF_PERNR.
**deduction_p0015-pernr = TER_PERNR.
*deduction_p0015-lgart = 'M120'.
*deduction_p0015-begda = FUTURE_DEDUCTION-DEDUCATION_DATE.
*deduction_p0015-endda = FUTURE_DEDUCTION-DEDUCATION_DATE.
*deduction_p0015-BETRG = future_deduction-future_payment_amount.
*deduction_p0015-WAERS = 'SGD'.
*deduction_p0015-ZUORD = TER_PERNR.
*append deduction_p0015.
*endloop.
Create a deduction wage type in 0015 for the employee
break-point.
CLEAR RETURN.
CALL FUNCTION 'BAPI_EMPLOYEET_ENQUEUE'
EXPORTING
    NUMBER              = REF_PERNR
    VALIDITYBEGIN       = '18000101'
IMPORTING
   RETURN              = return
if not return is initial.
message E000(000) with
'Referred Employee could not be locked for referal payment deducation,
please try after some time'.
endif.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
    INFTY                  = '0015'
    NUMBER                 = REF_PERNR
   SUBTYPE                = 'M120'
OBJECTID               =
LOCKINDICATOR          =
   VALIDITYEND            = SY-DATUM
   VALIDITYBEGIN          = SY-DATUM
RECORDNUMBER           =
    RECORD                 = deduction_p0015
    OPERATION              = 'COPY'
TCLAS                  = 'A'
   DIALOG_MODE            = '2'
NOCOMMIT               =
VIEW_IDENTIFIER        =
SECONDARY_RECORD       =
IMPORTING
   RETURN                 = return
   KEY                    = key
break-point.
COMMIT WORK.
if not return is initial.
*return-TYPE
*ID
*NUMBER
*MESSAGE
message I000(000) with return-MESSAGE.
endif.
CALL FUNCTION 'BAPI_EMPLOYEET_DEQUEUE'
EXPORTING
    NUMBER              = REF_PERNR
    VALIDITYBEGIN       = '18000101'
IMPORTING
   RETURN              = return
xxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxx
Thanks and regards
-Senthil Bala
Message was edited by: senthil bala

Hi Senthil
Why at all U want a subroutine to create a record in IT0015 through Dynamic action.There are some standard codes available to update infotypes.
Let me give U an example
14     9CON     BETRG     4     2     I     INS,0015 This will create a record in IT0015 when IT0014 is updated with Wagetype 9CON
14     9CON     BETRG     4     3     W     P0015-LGART='5400' Set wagetype for IT0015(Here U can use a subroutine call to set the wagetype)
14     9CON     BETRG     4     4     W     P0015-BETRG=P0014-BETRG set amount for IT0015(Here U can use a subroutine call to get the amount)
14     9CON     BETRG     4     5     W     P0015-BEGDA=P0014-ENDDA set the dates(Here U can use a subroutine call to set the dates)
Hope this will help U.
Please award points if helpful

HR_INFOTYPE_OPERATION not Working for IT0002 while Hire

Hi all ,
we have created a report which picks the file from the Application Server for creating Employee in HR.
First created Position and Used FM 'HR_PAD_HIRE_EMPLOYEE' to create Employee Pernr.
After which I have used 'HR_INFOTYPE_OPERATION' for creating records in IT such as 2,6,8,14,22,105,185.
Expect 2,6,185 everything works fine.
I have debugged the FM 'HR_INFOTYPE_OPERATION' ( Parameters are correct ) it returns nothing. No Error .
Kindly assist.
Jerome.J

Using user program is not advised to hire/maintain an employee, because FM 'HR_INFOTYPE_OPERATION' does not do all the validation/subsequent update performed in PA40/PA30 txn program module.
1. Create an Excel file with the data required for each infotype in the same order as a hiring action and save as a *.txt file.
2. Create a batch recording from PA40 transaction for hiring an employee
3. Create a LSMW object using the batch recording from step 2.
4. Test the LSMW object thoroughly using the file from step 1 above
5. Save in a transport, the objects from steps 2 & 3 above
6. Move the transport to Test system; Test again here with more data as in 1 above
7 Move the transport to prod system
In production system:
8. With small no. of employee data (as in step 1), run the LSMW action.
Display the data created.
9. If everything is OK, you may proceed with the rest; if it is a large number of employees, you may split the LSMW run to a few batches.
Alternatively, use 3rd party s/w e.g. INFO SHUTTLE, etc.

HR_INFOTYPE_OPERATION not working for LIS9

Hi Friends
AM using HR_INFOTYPE_OPERATION FM to delimite record of IT0105 the return paramenter is not showing any error and executing successfully but when i see the record it not get delimited ....
Regards
Meeta

Hi Meeta,
LIS9 is the function-code for LIST-DELIMIT and user interaction is required to select the records to be delimited.
Thus, I would advise you to use MOD instead (by changing the endda).
Regards,
Dilek

Deletion of index not working (GT085) - Bad performance

Hi experts,
our table COEP has around 90 MIO entries and now it seems like one index is not any longer working.
Therefore I wanted to rebuild the index ith SE14.
However, on rebuilding the index I get error GT085. Does anybody know how I can go on?
Kind regards

Hi,
Was the index actually rebuild or not?
Please give us a bit more detail.
What do you see in se14 if you run Extras -> Database Object -> check ?
Regards,
Johan

PO13 and 0001 infotype (HR_INFOTYPE_OPERATION + badi HRBAS00INFTY

Hello Friends,
We have cretaed a position description subtype and assigned it to 1002 infotype.
Query: 1) Adding 2 customer fields(Subtype and description) to infotype 0001 (This is done using PM01).
2) Using Po13, they assign a subtype(position description) for a particular Position.
Now the requirement is When they assign subtype to a postion in PO13 and save then these subtype
and subtype description should be stored in 0001 infotype.
the position should use to locate the employee and once the employee have been located update 0001.
for ths I have implemented a PO13 badi HRBAS00INFTY(IN updating method) and inside the BADI we are calling
HR_INFOTYPE_OPERATION' to update the eMPLOYEE(0001 INFOTYPE).
Problem: Now the problem is , when we open PO13 in change mode to assign a subtype to Position ,sap creates a lock entry and when svae we are call
HR_INFOTYPE_OPERATION' to update the eMPLOYEE(0001 INFOTYPE).but HR_INFOTYPE_OPERATION' also internally tries to lock the position but raising a
message "You have already locked object/infotype S50000024".
Pleae find below function and follwoing parameter I am suing for updating the person(0001 infotype) .
I dont understand why HR_INFOTYPE_OPERATION is trying to lock position when I pass Pernr and 0001 as a parametr.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = c_infty
number = wa_pernr-pernr
SUBTYPE =
OBJECTID =
lockindicator = 'X'
validityend = wa_pernr-endda
validitybegin = wa_pernr-begda
RECORDNUMBER =
record = it_0001
operation = 'MOD'
tclas = 'A'
dialog_mode = '0'
NOCOMMIT =
VIEW_IDENTIFIER =
SECONDARY_RECORD =
IMPORTING
Please help me .
Thanks In advance
Best Regards
Trupthi

Hi,
Onemore thing I couldn't find the code for IF_EX_HRBAS00INFTY-in_update.
For every BADI there will be an example interface. Here for this BADI example is IF_EX_HRBAS00INFTY. If u want to see the model code, go to SE24 and give the name :IF_EX_HRBAS00INFTY and click on display. Then you can find the methods and respective exapmle code.
One more thing
Some BADIs will not allow calling commit work. In your BADI also already one LUW is opened, so it will not allow to open another LUW and the respective commit work.
Thanks and Regards,
Chandra

Just upgraded to Lion an am discovering that I cannot send email photos from within iPhoto. Error message says bad Internet connection or server not working, when that's not the case. Never happened in Snow Leopard! Help!!!

Just upgraded to Lion an am discovering that I cannot send email photos from within iPhoto. Error message says bad Internet connection or server not working, when that's not the case. Never happened in Snow Leopard! Help!!!

what email service - Yahoo mail have been acting up lately
you can try setting Mail as your email client - it resolves this pfoblem for some people
LN

BADI implementation is not working in background for MRRL

Hai frnds,
BADI: MRM_WT_SPLIT_UPDATE is used for deducting withholding tax in MRRL(Invoice verification). This BADI was implemented and working fine in foreground, but not working in background.
After implementing the BADI, the standard method of calculating TDS(from vendor master) is over written by BADI implementation.Now standard deduction is also not workijng in background.Plz help me to solve it.
Bala.V

HI,
COR6N is the Enjoy Transaction and sap does not suggest to write the BDC on these transaction as most of these transaction uses the GUI elements foe better display and which cannot be recorded while processing the BDC in back ground.
Check for the Normal transaction and write the BDC for it.
Or
Pass X to Rcommit flag in the CTU_PARAMS option and check.

Hi. I habe one old ID and now i have one new ID. The old one is bad , because the Email not working. But i hav a lot of Apps and i want to copy this apps in my new ID. How can i do this?

Hi. I habe one old ID and now i have one new ID. The old one is bad , because the Email not working. But i hav a lot of Apps and i want to copy this apps in my new ID. How can i do this?

You don't. Apps are permanently tied to the ID used to purchase them. Instead of creating a new ID, change the primary email address on your existing ID.

HR_INFOTYPE_OPERATION is not working in user exit ZXPADU02

Hi frndz,
i want to delimit/modify record in infotype 0014 after checking some condition when user clicks on SAVE in infotype 0008.
For this i'm using the code like below.
In Include ZXPADU02.
when '0008'.
IF sy-ucomm = 'UPD'.
chek <condition>
if sysubrc = 0.
Lock employee.
Delimti(LIS9) record in IT0014 using HR_READ_INFOTYPE_OPERATION.
Unlock employee.
endif.
Here every thing working fine but record is not getting delimitted.
Could anybody please help me any other possibilities to solve it.
Thanks and Regards,
Venkat

Hi,
I tried to use the FM HR_INFOTYPE_OPERATION in ZXPADU02 but I found that it will
not update data in the real DB table(PAXXXX).I found that in FM 'HR_MAINTAIN_MASTERDATA' from FM 'HR_INFOTYPE_OPERATION' will set the field 'PSPAR-PBPFL' as 'X'.
In standard program, it looks like if this field is set it will not do the logic to update the DB table. So I put the code in other report and then call in the ZXPADU02. I think it's about LUW.
Code as follows to understand.
data:
      lw_p0008      LIKE p0008,
      lw_pskey      LIKE pskey,
      lv_option,
          EXPORT lw_p0008 lw_pskey lv_option
            to memory id 'ZXPADU02_0008'.
          submit ZHRR_PA_ZXPADU02_0008
                 and return.
Inside program ZHRR_PA_ZXPADU02_0008
IMPORT w_p0008 lw_pskey lv_option
    FROM MEMORY ID 'ZXPADU02_0008'.
CALL FUNCTION 'ENQUEUE_EPPRELE'
        EXPORTING
          pernr          = lw_p0008-pernr
        EXCEPTIONS
          foreign_lock   = 1
          system_failure = 2
          OTHERS         = 3.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
      infty                  = '0008'
      number                 = lw_p0008-pernr
      subtype                = lw_pskey-subty
      objectid               = lw_pskey-objps
      lockindicator          = lw_pskey-sprps
      validityend            = lw_pskey-endda
      validitybegin          = lw_pskey-begda
      recordnumber           = lw_pskey-seqnr
      record                 = lw_p0008
      operation              = lv_opera
*      TCLAS                  = 'A'
*      DIALOG_MODE            = '1'
*      nocommit               = 'X'
*     VIEW_IDENTIFIER        =
*     SECONDARY_RECORD       =
    IMPORTING
      return                 = lw_return
*      KEY                    =
IF NOT lw_return IS INITIAL AND
     lw_return-type EQ 'E'.
    MESSAGE e000(38) WITH lw_return-message.
ENDIF.
CALL FUNCTION 'DEQUEUE_EPPRELE'
    EXPORTING
      pernr = lw_p0008-pernr.
If this not works, then go for dynamic action from V_T588Z as suggested by Suresh.
Regards
Eswar

ME21N badi ME_GUI_PO_CUST - not working in PO creation

Hi All,
I am working on badi ME_GUI_PO_CUST to create a custom tab on PO header. I have implemented the BADI with custom fields in the custom screen. However, in ME21N, this new tab is not appearing. At the same time, it is appearing in ME23N. If i take a PO in display mode, the tab appears and then switch to chaneg mode, the tab disappears.
Any solution for this pleas.??
Regards,
Arun.

Hi Arun,
You can use MM06E005 exit for adding the tab for item level in ME21n transaction. In general, you go to smod and you give this exit there and then press on documentation then you will find all the information regarding function module exits.
Give this exit in SMOD and then press Attributes--> click on Components, then you will find all the function module exits and subscreen areas where you can add your custom field on the subscreens.
I am giving you the subscreen :
SAPMM06E 0111 CUSTSCR1 SAPLXM06 0111 Subscreen: PO item
Function module exit:
EXIT_SAPMM06E_018 Import Data from Customer Subscreen for purchasing document
Then you start adding the custom field in Custom include of EKPO table and then you go to SE51 and then you import I mean ( Get from dictionary ) that particular Z field and then activate it. These all the thing you need to create a project and implement in CMOD transaction.
Then you write the respective code in Functionmodule exit to populate the data to the database.
Thanks,
Swamy Kunche
Edited by: Swamy Kunche on Dec 7, 2009 10:58 AM

HR_INFOTYPE_OPERATION not working in badi HRBAS00INFTY

Similar Messages

Maybe you are looking for