Modify Infotype 0008 using BADI or EXIT - How to?

Hi,
How to modify the values for infotype '0008' in save moment, using a EXIT or BADI????
What EXIT or BADI to use for this?
Thanks,
Daniel

Use Exit FM: EXIT_SAPFP50M_001 for setting default values and Exit FM: EXIT_SAPFP50M_002 validations for various infotypes(including IT0008) by enhancing PBO and PAI includes respectively.
for Example.
When copying an infotype 0008 record, the reason code *should be cleared.
INCLUDE y_zxpadu01_08. 
Data declaration.
DATA: BEGIN OF wa_am7912_0008.
        INCLUDE STRUCTURE p0008.
DATA:   filler(1500) TYPE c,
      END OF wa_am7912_0008.
Only perform for 0008 infotypes....
  IF innnn-infty = '0008'.
  ...that are being copied only....
    IF ipsyst-ioper = 'COP'.
    .....and that are being called manually.
      IF ipsyst-inpst = '0'.
      Parse the data.
        CLEAR wa_am7912_0008.
        wa_am7912_0008 = innnn.
      Clear the reason code.
        clear wa_am7912_0008-preas.
        clear innnn.
        innnn = wa_am7912_0008.
      endif.
    endif.
  endif.
Regards,
MM

Similar Messages

  • Not able to modify the data for infotype 0008 using FM

    Hi All ,
    I have got a requirement for updating the infotype 0008 data  using FM : HR_MAINTAIN_MASTER_DATA.
    While trying to modify the wagetypes data which is of blank ..unable to upload the amount for that partcular field ..
    For this am herewith the link  of o/p :
    http://i55.tinypic.com/28jfw2c.jpg for this am also posting the code...
    Please suggest me furthur in what way i can upload..
          SELECT * FROM pa0008 INTO TABLE itab_pa0008
    FOR ALL ENTRIES IN itab
        WHERE pernr = wa_data-pernr
        AND begda = wa_data-begda_out
        AND endda = wa_data-endda_out.
        DESCRIBE TABLE itab_pa0008 LINES lin.
        IF lin EQ  0.
          c_action = 'INS'.
        ELSE.
          c_action = 'MOD'.
        ENDIF.
        LOOP AT itab INTO wa_itab WHERE pernr = wa_data-pernr.
          CLEAR: wa_bapireturn, wa_bapireturn1, wa_hr_return.
          REFRESH: it_pprop[],it_modified_keys[].
          it_pprop-infty = '0008'.
          it_pprop-fname  = 'P0008-TRFAR'.                 "1
          it_pprop-fval = wa_itab-trfar.
          APPEND it_pprop.
          CLEAR it_pprop.
          it_pprop-infty = '0008'.
          it_pprop-fname  = 'P0008-TRFGB'.                 "2
          it_pprop-fval = wa_itab-trfgb.
          APPEND it_pprop.
          CLEAR it_pprop.
          it_pprop-infty = '0008'.
          it_pprop-fname  = 'P0008-TRFGR'.                  "3
          it_pprop-fval = wa_itab-trfgr.
          APPEND it_pprop.
          CLEAR it_pprop.
          it_pprop-infty = '0008'.
          it_pprop-fname  = 'P0008-TRFST'.                  "4
          it_pprop-fval = wa_itab-trfst.
          APPEND it_pprop.
          CLEAR it_pprop.
          flag = flag + 1.
    *****************************************************************************************************5
          BREAK-POINT.
          IF NOT wa_itab-lga1 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA01'.
            it_pprop-fval = wa_itab-lga1.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet1.
          ENDIF.
          IF NOT wa_itab-bet1 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET01'.
            it_pprop-fval = wa_itab-bet1.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************6
         IF NOT wa_itab-lga2 IS INITIAL.
           it_pprop-infty = '0008'.
           it_pprop-fname  = 'P0008-LGA02'.
           it_pprop-fval = wa_itab-lga2.
           APPEND it_pprop.
           CLEAR it_pprop.
           bet1 = wa_itab-bet2.
         ENDIF.
          IF NOT wa_itab-bet2 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET02'.
            it_pprop-fval = wa_itab-bet2.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************7
          IF NOT wa_itab-lga3 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA03'.
            it_pprop-fval = wa_itab-lga3.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet3 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET03'.
            it_pprop-fval = wa_itab-bet3.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************8
          IF NOT wa_itab-lga4 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA04'.
            it_pprop-fval = wa_itab-lga4.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet4 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET04'.
            it_pprop-fval = wa_itab-bet4.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************9
          IF NOT wa_itab-lga5 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA05'.
            it_pprop-fval = wa_itab-lga5.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet5 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET05'.
            it_pprop-fval = wa_itab-bet5.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************10
          IF NOT wa_itab-lga6 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA06'.
            it_pprop-fval = wa_itab-lga6.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet6 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET06'.
            it_pprop-fval = wa_itab-bet6.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************11
          IF NOT wa_itab-lga7 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA07'.
            it_pprop-fval = wa_itab-lga7.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet7 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET07'.
            it_pprop-fval = wa_itab-bet7.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************12
          IF NOT wa_itab-lga8 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA08'.
            it_pprop-fval = wa_itab-lga8.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet8 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET08'.
            it_pprop-fval = wa_itab-bet8.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************13
          IF NOT wa_itab-lga9 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA09'.
            it_pprop-fval = wa_itab-lga9.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet9 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET09'.
            it_pprop-fval = wa_itab-bet9.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************14
          IF NOT wa_itab-lga10 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-LGA010'.
            it_pprop-fval = wa_itab-lga10.
            APPEND it_pprop.
            CLEAR it_pprop.
            bet1 = wa_itab-bet2.
          ENDIF.
          IF NOT wa_itab-bet10 IS INITIAL.
            it_pprop-infty = '0008'.
            it_pprop-fname  = 'P0008-BET010'.
            it_pprop-fval = wa_itab-bet10.
            APPEND it_pprop.
            CLEAR it_pprop.
          ENDIF.
    *******************************************************************************************************15
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-LGA11'.
       it_pprop-fval = wa_itab-lga11.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-BET11'.
       it_pprop-fval = wa_itab-bet11.
       APPEND it_pprop.
       CLEAR it_pprop.
    ********************************************************************************************************16
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-LGA12'.
       it_pprop-fval = wa_itab-lga12.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-BET12'.
       it_pprop-fval = wa_itab-bet12.
       APPEND it_pprop.
       CLEAR it_pprop.
    ********************************************************************************************************17
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-LGA13'.
       it_pprop-fval = wa_itab-lga13.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-BET13'.
       it_pprop-fval = wa_itab-bet13.
       APPEND it_pprop.
       CLEAR it_pprop.
    ********************************************************************************************************18
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-LGA14'.
       it_pprop-fval = wa_itab-lga14.
       APPEND it_pprop.
       CLEAR it_pprop.
       bet1 = wa_itab-bet2.
       it_pprop-infty = '0008'.
       it_pprop-fname  = 'P0008-BET14'.
       it_pprop-fval = wa_itab-bet14.
       APPEND it_pprop.
       CLEAR it_pprop.
    BREAK-POINT.
          CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
            EXPORTING
              number = wa_itab-pernr
            IMPORTING
              return = wa_bapireturn1.
          BREAK-POINT.
         IF c_action = 'INS'.
           CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
             EXPORTING
               pernr           = wa_itab-pernr
               actio           = 'INS'
             tclas           = 'A'
               begda           = wa_data-begda_out             "'20110401'
               endda           = wa_data-endda_out             "'99991231'
               dialog_mode     = '2'
             luw_mode        = '1'
             IMPORTING
               return          = wa_bapireturn
               return1         = wa_bapireturn1
               hr_return       = wa_hr_return
             TABLES
               proposed_values = it_pprop
               modified_keys   = it_modified_keys.
           IF NOT wa_bapireturn IS INITIAL.
             WRITE : / wa_bapireturn.
             CLEAR : wa_itab , wa_bapireturn.
           ENDIF.
         ELSEIF c_action = 'MOD'.
            CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
              EXPORTING
             infty         = '0008'
                pernr           = wa_itab-pernr
                actio           = 'MOD'
                begda           = wa_data-begda_out             "'20110401'
                endda           = wa_data-endda_out             "'99991231'
          record        =  p_record
             recordnumber  = wa_itab-SEQNR
             operation     = change
             nocommit      = nocommit
                dialog_mode     = '0'
             IMPORTING
                return          = wa_bapireturn
                return1         = wa_bapireturn1
                hr_return       = wa_hr_return
              TABLES
                proposed_values = it_pprop
                modified_keys   = it_modified_keys.
            IF NOT wa_bapireturn IS INITIAL.
              WRITE : / wa_bapireturn.
              CLEAR : wa_itab , wa_bapireturn.
            ENDIF.
         ENDIF.
          CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
            EXPORTING
              number = wa_itab-pernr
            IMPORTING
              return = wa_bapireturn1.
        ENDLOOP.
      ENDLOOP.

    Here is a sampe, and the logic you are using for wages goes in the internal table for wages (you already have the enqueue & dequeue so you don't have to worry about that, so you only have to add the BAPI_TRANSACTION_COMMIT):
    CALL FUNCTION 'BAPI_BASICPAY_CHANGE'
      EXPORTING
        employeenumber             = pa0008-pernr
        subtype                    = pa0008-subty
        objectid                   = pa0008-objps
        lockindicator              = pa0008-sprps
        validitybegin              = pa0008-begda
        validityend                = pa0008-endda
        recordnumber               = pa0008-seqnr
        payscaletype               = pa0008-trfar
        payscalearea               = pa0008-trfgb
        payscalegroup              = pa0008-trfgr
        payscalelevel              = pa0008-trfst
    *   NEXTINCREASE               =
    *   LOCALALLOWLEVEL            =
    *   PARTNERSHIP                =
    *   CURRENCY                   =
    *   COMPARISONPAYSCLTYPE       =
    *   COMPARISONPAYSCLAREA       =
    *   COMPARISONPAYSCLGRP        =
    *   COMPARISONPAYSCLLVL        =
    *   COMPNEXTINCREASE           =
    *   CAPACITYUTILLEVEL          =
    *   HOURSWORKEDPERPERIOD       =
    *   ANNUALSALARY               =
    *   CASEGROUPCATALOG           =
    *   CASEGROUP                  =
    *   CURRENCYANNUALSALARY       =
    *   REASON                     =
    *   NOCOMMIT                   =
    * importing
    *   return                     =
    TABLES
       wagetypes                  = wages.
    Regards,
    Ryan Crosby

  • Infotype 0008 using SEQNR?

    Hi,
    Anyone here have gone down the path of using SEQNR on infotype 0008? Is it possible to do so?
    For example, a person transfering from LA to London received a position promotion increase, cost of living adjustment, and internal equity adjustment.
    True, you can do it via infotype 759 w/ ECM module, but there are situation where things shouldn't be in 759 ECM module and goes directly on IT0008.
    In situation as described and SEQNR is not the method to go down, what have everyone done in this situation?
    Thanks!
    KN

    Yea you could..
    But what if you have more than one type of pay changes and want to capture the differences
    for example promotion increase is 1000, relocation is 500, etc..which makes up a new basic pay...So we know which is which...
    w/o going down the route of recording everything in infotype 0759...

  • Upload data in infotype 1520 using BADi(HRECM00_BDG0001).

    hi experts,
    We have a requirement wherein the  BADi (HRECM00_BDG0001- which uses DETERMINE_BUDGET_VALUES method) needs to upload initial Budget Values into the Budget Structure, through an Excel Spreadsheet input (which will contain Organization Units and its respective Budget Values)
    This will result in upload of initial budget values into the Budget Values Infotype 1520.
    and based on this the Budget structure is created and ready for use.
    Is there any functional module or any other method to upload the data (excel file) into the infotype 1520?
    regards,
    joy.

    Hi Christian,
    Please check if hte below links help you in some way.
    Uploading Files and Manipulating their Content
    http://help.sap.com/saphelp_nw04/helpdata/en/ba/78d3c747b24546ab1c1499a054d8a5/content.htm
    File Upload in BSP Applications
    http://help.sap.com/saphelp_nw04/helpdata/en/eb/8c683c8de8a969e10000000a114084/content.htm
    Regards,
    SuryaD.
    Edited by: SuryaD on Dec 18, 2009 11:15 PM

  • How make display only the amount field in table control(infotype 0008)

    Dear Freinds,
    have to make display only the amount field (Q0008-bet01) on table control in infotype 0008 , could you tell me how to make it display only.
    i have tried the below coding it is not working in PBO & PAI of the user exit
    ZXPADU01 and ZXPADU02. For the table control is there any othe method??
           loop at screen.
               screen-name  = 'WA_P0008-BET01'.
              screen-input = 0.
              screen-output = 1.
              modify screen.
          endloop.
    i have tried like this as well
           loop at screen.
               screen-name  = 'Q0008-BET01'.
              screen-input = 0.
              screen-output = 1.
              modify screen.
          endloop.
    in the both the above methods it is not working. Could any one plese suggest me how to make display only the amount field in infotype 0008.
    regards
    syamla

    Dear Freinds,
    have to make display only the amount field (Q0008-bet01) on table control in infotype 0008 , could you tell me how to make it display only.
    i have tried the below coding it is not working in PBO & PAI of the user exit
    ZXPADU01 and ZXPADU02. For the table control is there any othe method??
           loop at screen.
               screen-name  = 'WA_P0008-BET01'.
              screen-input = 0.
              screen-output = 1.
              modify screen.
          endloop.
    i have tried like this as well
           loop at screen.
               screen-name  = 'Q0008-BET01'.
              screen-input = 0.
              screen-output = 1.
              modify screen.
          endloop.
    in the both the above methods it is not working. Could any one plese suggest me how to make display only the amount field in infotype 0008.
    regards
    syamla

  • Add new fields using BADI DNO_EVENT_SAVE in Solution Manager

    Hi,
    I would like to add new fields using BADI DNO_EVENT_SAVE. How can I add new fields? Thanks.

    Hi,
    This is the blog which explains how to add custom fields for CRM_DNO_MONITOR.
    /people/bruyneel.guillaume/blog/2008/06/13/service-desk-implementation-guide-part-ii
    Instead of looking or changing the BAdI, you can copy the program of CRM_DNO_MONITOR and modify it.
    Please check this thread:
    Reg : CRM_DNO_MONITOR
    Regards,
    Sanjai

  • Badi / User exits  in PM & CS

    Hi everyone ...
    Can anyone please tell me the procedure to apply or use BADI / User exits in SAP  R/3.
    with regards
    Ajaysingh

    Hi,
    For BADI's,
    1) Goto to tcode SE24 give the CL_EXITHANDLER and display and then double click on the
        GET_INSTANCE
        keep Break point at this location 'call method cl_exithandler=>get_class_name_by_interface'
        then the tcode it will trigger there and we can debugg there we can find badi'for that tcode and then
        remove the break point.
    2) Goto to tcode->status->program name->double click on that program will display's
        then pess crtl+F then cl_exithandler
    For User Exit's
    goto to tcode->status->program name->double click on that,
    then goto to-> attribute take the package name and
    Goto SMOD tcode ->Utilities->give the package name and F8
    then a list of exits will display for that tcode as well as that package.
    u can check the table MODSAP
    u can check the table MODACT
    regards,
    Venkatesan Anandan
    Edited by: Venkatesan Anandan on Mar 16, 2009 11:13 AM

  • How to Save Screen data using BADI for Screen Exit

    Hi All,,
    I have requirement got MIGO Transaction. Customer wants one tab besides VENDOR on header level. For that i used BADI 'MB_MIGO_BADI'. Also i created Append Structure in MKPF Table for two fields and designed sreen using SE51.
    Now i want to save this data ( with added new fields ) into Data base table MKPF. I don't know where to place code .
    Also pl confirm me that, when i copy Sample Code from
    Go to -> Sample Code -> Copy . All the code is copied from BADI. So is it necessary to keep the code for each method as it or i have to comment all the code i each methos. i am littel bit confused abt it. Please tell me in detial.
    Also tell where to put logic for saving newly added fields .
    waiting
    Thanks and Regards.
    Ulhas

    is this the one you are looking for?
    Learning Series SAP NetWeaver Process Orchestration, Business to Business Add-on 2d OFTP Adapter

  • [Enhancement in BW]: How to use BaDI : RSU5_SAPI_BADI

    Hi Everybody,
    Right now, could you kindly please tell me how to i use customer exit but using BADI, particularly for BADI : RSU5_SAPI_BADI.
    <b>I just wanna use the customer exit on variable (variable user-exit).</b>
    So far i've tried these steps (might you correct me/advise):
    1. tcode : SE18
    2. Enter the Badi Name : RSU5_SAPI_BADI
    3. (Toolbar) enhancement implementation -> Create
    4.  ... (After that i don't know what i've to do ..)
    Could you tell me step-by-step to make it ?
    Such as what i should fill-in for Implementation Name and any parameter should i fill in there and how to debug it ???
    Many-many thanks all for the attention.
    Hopefully i can make it :).
    Kind regards,
    Niel.

    Check out this link:
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3001894b-b1fb-2910-77ba-e80b6f2053b7">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3001894b-b1fb-2910-77ba-e80b6f2053b7</a>

  • Infotype 0008 reecord creation in a BAdI - Issue

    I am implementing the method 'CALC_SAL_ADJUSTMENT' of the BAdI definition 'HRECM00_ACTIVATION'. As per the requirement, I have to copy the record in the importing parameter IT0008_OLD, make some modifications to the record and then pass it on to the exporting parameter IT0008. Simultaneously, a new infotype 0008 record has also to be created based on the data in the new record IT0008. I tried using the FM 'BAPI_BASICPAY_CREATESUCCESSOR', since this will also delimit the previous record.
    **Create a new Infotype 0008 record, delimiting the previous record
    CALL FUNCTION 'BAPI_BASICPAY_CREATESUCCESSOR'
    EXPORTING
    employeenumber = pernr
    subtype = it0008_old-subty
    validitybegin = effdt
    validityend = c_endda
    payscaletype = it0008_old-trfar
    payscalearea = it0008_old-trfgb
    payscalegroup = it0008_old-trfgr
    payscalelevel = it0008_old-trfst
    nextincrease = it0008_old-stvor
    localallowlevel = it0008_old-orzst
    partnership = it0008_old-partn
    currency = it0008_old-waers
    comparisonpayscltype = it0008_old-vglta
    comparisonpaysclarea = it0008_old-vglgb
    comparisonpaysclgrp = it0008_old-vglgr
    comparisonpayscllvl = it0008_old-vglst
    compnextincrease = it0008_old-vglsv
    capacityutillevel = it0008_old-bsgrd
    hoursworkedperperiod = it0008_old-divgv
    annualsalary = v_annsal
    casegroupcatalog = it0008_old-falgk
    casegroup = it0008_old-falgr
    currencyannualsalary = it0008_old-ancur
    reason = it0008_old-preas
    nocommit = space
    IMPORTING
    return = wa_return
    employeenumber = v_empno
    subtype = v_subty
    objectid = v_objectid
    lockindicator = v_lockind
    validitybegin = v_valbegin
    validityend = v_valend
    recordnumber = v_recordno
    TABLES
    wagetypes = it_bwagetype.
    However, it is raising an exception 'cx_hrpa_violated_precondition', which is not caught and hence a run-time error.
    I tried using the above function module in a report program and it worked fine.
    Can anybody please let me know, whether it is possible to create an infotype 0008 record inside the above BAdI implementation? and if yes, where am I going wrong?
    Thanks in advance.
    Sujit.

    put the BAPI call as a BACKGROUND TASK & try it..
    ~Suresh

  • How to do mapping using badis?

    Hi Experts,
    Can any one tell me how to do mapping using badis. Ex : this is for in IF_DP_WTY_UI_FIELD_MAPPING~CLAIM_HEADER_DATA_IN
    this is out -  IF_DP_WTY_UI_FIELD_MAPPING~CLAIM_HEADER_DATA_OUT. any one have any idea how to use these methods in webdynpro.
    Thanks,
    kris.
    Edited by: kissnas on Jan 5, 2011 7:39 AM

    Hi,
    I am not sure of what mapping here, however to call badi methods
    you can use get badi to get badi ref and call badi to call corresponding methods if it is new badi or if it is old badi you can use class exit handler for getting ref and call the methods of badi implementaion using this ref..
    it is same as calling any method of any class, only thing to make sure is badi is implemented

  • BADI, User Exit or Dynamic Action for Infotype 24

    Hello,
    in PA30, our HR admin team want me to write an Infotype 19 record when a user amends or creates an Infotype 24 record.
    I spent all day yesterday trying to find a solution to this.
    Can anyone please tell me:
    1) Do dynamic actions work for IT0024? - our HR admin suggest that they don't as there is no 'subtype'.
    2) Should user exit PBAS0001 (function EXIT_SAPFP50M_002) work for IT0024? I have tried putting in a test display which should appear on save of IT0024 and this does not appear to work.
    3) Will BADI HRPAD00INFTY work? If so, does anyone have an example of code that tests the 'old' IT0024 record before modification - the documentation does not help too much with a good example. I'm planning to use this as a last resort due to the need for an access key.
    Many thanks in advance,
    Keiron.

    The BADI is probably the best way to go.  You should not need an access key - you do not put your code in the BADI, but instead create an implementation of it in a Z name range.  Go to SE18 for the BADI and display it, and select menu option implementation--->create.  Give a Z name and then you will have a place to put your code.  You can double click on the methods shown in your implementation to get to the ABAP code editor.
    Exit PBAS0001 should also work - put a breakpoint in it to see if it is called.
    Both the BADI and Exit are called at almost the same point in the SAP PA30 code - however the BADI is called in some cases when the exit is not.  It is outside an additional IF test in the SAP code.
    Andrew

  • Screen-exit for xk01 using badi

    Hai.. all.
         i want to add customized screen for xk01.
        by using badi i hav tried it its working and whatever the value am giving into screen is also updating  into table .but my problem is while adding this screen in xk01 it is also updating xk02, xk03.
    but in xk03 it should be in dispaly mode . in which method it hav to write code for diaplay mode screen
    can anybody suggest me how to write it .........................
    tanx in advance..............

    Modify the screen attributes to make them display only for transaction XK03. Write code in PBO of custom screen by using Loop at screen.....if sy-tcode = 'XK03'.....Endif......Endloop.
    Thanks
    Amol Lohade

  • How to determine the purchasing group using BADI BBP_PGRP_FIND

    Hello Friends
    We use SRM Server 5.5 (Classic scenario).
    As you know that, purchasing group has the responsible product categories in PPOMA_BBP, when user creates the shopping cart to determine the purchasing group. 
    In our case, we should determine the purchasing group using other criteria.
    MM side is OK to determine the purchasing group using specific criteria.
    Because Material Master has the purch. Group information. 
    In case of SRM, we should develop the logic using BBP_PGRP_FIND BADI.
    But I’m not sure how to use this badi.
    We want to determine the purchasing group based on the following logic.
    If described shopping cart without product ID
    Do Standard purchasing group determination logic.
    Else
    Assign the purch group from MARC- EKGRP (Purchasing Group)
    Is it possible to determine above the logic?
    If yes, Could you give me some information?
    Thank you,
    Best regards,
    SH
    Message was edited by:
            So Hee Lee

    Thank you for your answer.
    I found the way to develop the our logic using BADI: bbp_pgrp_find.
    But I’m not sure the following logic is correct.
    To differentiate described req. or product id req, We check the E_ITEM – PRODUCT using BBP_PD_SC_GETDETAIL.
    IF E_ITEM – PRODUCT is blank, Read the category ID to find the purchasing group.
    To find the purch. Group, we can use FM:  BBP_OM_DETERMINE_RESP_PGRP.
    Import parameter: IS_RESP_ITEM_DATA – Category _ID
    Export parameter: ES_PURCH_DATA
    ELSE
    CALL the customer function to read the R/3 purchasing group from MARC- EKGRP
    Search the HRT5500-TABNR using purchasing group from R/3.
    Search the HRP5500 – OBJID using HRT5500-TABNR
    Call the FM:  BBP_OM_DETERMINE_RESP_PGRP
    Import parameter: IS_RESP_ITEM_DATA – PROC_GROUP – OBJID
    Export parameter: ES_PURCH_DATA
    Thank you
    Best Regards
    SH

  • Screen exit for VL01 in ECC 6.0 using badi's

    Hi All,
    I got a requirement to create a new tab in VL01 transaction where i need to create one field in ECC 6.0.
    Can anyone tell me the complete procedure to create a new sub screen and adding it to the existing standard sap screen as a new tab in ECC 6.0 version.
    kindly suggest me how to do this using badi's.

    Dear Nicole,
    a)SE18:
    Definition name               ME_PROCESS_PO_CUST
    b)SMOD:
    Enhancement     MM06E005
    EXIT_SAPMM06E_013
    -> If you want to use it, use transaction CMOD to create a
    project with Enhancement     MM06E005
    Best Regards,
    Ian Wong

Maybe you are looking for