How to find User Exit / Badi

Hi All
My requirement is to search the User Exit / Badi / any other enhancement, which is used in a standard transaction. For example:- I know that there is some Exit / badi used in transaction VA01, now how can I search for these exit / BADI which is applied in the transaction VA01.
Pl. do not suggest me to take the help of ABAP, since I want to search it myself. Any help will be highly appreciated.
Thanks and regards
AA

Hi,
I hope this will help you.
for sales order creation VA01  program SAPMV45A, u can find out by starting the transaction VA01 and put /h (debugging mode on) then
from the various buttons on top of the screen like Fields, table, breakpoints, watchpoints, calls, overview and settings.
from above click on overview button, then it will show you all the userexits under this programs used.
like Program -
block -
name
SAPMV45A    program      SAPMV45A
MV45AFZA     form           USEREXIT_MOVE_FIELD_TO_KOMKD
Mahesh

Similar Messages

  • How to find User Exits/ Enhancments/ BADI's for T-code CJ20N

    Hi All,
        In T-code CJ20N, assume there are two fields A & B. User will input value in A, based on A value I need to fill B field. So I need to find first suitable User Exit/ Enhancment/ BADI.
    Kindly help me in this regard. Pls tell me how to find User Exit/ Enhancment/ BADI for a given t-code.
    Regards
    Jaker.

    Hi,
    Check the following , this might help,
    1. CNEX0037
    2.CNEX0038
    3.CNEX0039
    Regards
    Kiran Sure

  • How to find  USER-EXIT  for tcode - F110

    I am new in  USER-EXIT  Please help   how to find  USER-EXIT for  F110
    ASAP

    Hi,
    Enhancement/ Business Add-in            Description
    Enhancement
    RFFOX074                                Frame for user exit RFFOX074 (in program RFFOCH_U)
    RFFOX075                                Frame for user exit RFFOX075 (in program RFFOCH_U)
    RFFOX081                                Frame for user exit RFFOX081 (in program RFFOF__T)
    RFFOX082                                Frame for user exit RFFOX082 (in program RFFOF__T)
    RFFOX100                                Frame for user exit RFFOX100 (in program RFFOUS_T)
    RFFOX101                                Frame for user exit RFFOX101 (in program RFFOUS_T)
    RFFOX102                                Frame for user exit RFFOX102 (in program RFFOUS_T)
    RFFOX103                                Frame for user exit RFFOX103 (in program RFFOUS_T)
    RFFOX104                                user exit
    RFFOX105                                Frame for user exit RFFOX105 (in program RFFOUS_T)
    RFFOX200                                Frame for user exit RFFOX200 (in program RFFONZ_T)
    RFFOX210                                Frame for user exit RFFOX210 (in program RFFOAU_T)
    RFFOX211                                Frame for user exit RFFOX211 (in program RFFONZ_T)
    RFFOX230                                General program for user exit RFFOX230 (in program RFFOJP_L)
    RFFOX240                                Enhancement for User Exit 240 (RFFOAT_P)
    RFFOX250                                Enhancement for User Exit 250 (RFFODK_E)
    RFFOX901                                Framework for user exit RFFOX901 (in program RFFOM100)
    RFFOX902                                Framework for user exit RFFOX902 (in program RFFOM100)
    FDTAX001                                Enhancement to Transaction FDTA (event after the download)
    FEDI0002                                Function exits for EDI DOCS in FI - Incoming pyt adv.notes
    FEDI0003                                Function exits for EDI docs in FI - Save PEXR segments
    FEDI0004                                Function exits for EDI docs in FI - particular events
    FEDI0006                                Function Exits for EDI-docs in FI: Save IDCR Segments
    RFFOX003                                Frame for user exit RFFOX003 (in program RFFOM100)
    RFFOX041                                Framework for user exit RFFOX041 (in program RFFOBE_I)
    RFFOX042                                Framework for user exit RFFOX042 (in program RFFOBE_E)
    RFFOX043                                Framework for user exit RFFOX043 (in program RFFOBE_D)
    RFFOX061                                Frame for user exit RFFOX061 (in program RFFOCH_P)
    RFFOX062                                Frame for user exit RFFOX062 (in program RFFOCH_P)
    RFFOX063                                Frame for user exit RFFOX063 (in program RFFOCH_P)
    RFFOX064                                Frame for user exit RFFOX064 (in program RFFOCH_P)
    RFFOX065                                Frame for user exit RFFOX065 (in program RFFOCH_P)
    RFFOX066                                Frame for user exit RFFOX066 (in program RFFOCH_P)
    RFFOX071                                Frame for user exit RFFOX071 (in program RFFOCH_U)
    RFFOX072                                Frame for user exit RFFOX072 (in program RFFOCH_U)
    RFFOX073                                Frame for user exit RFFOX073 (in program RFFOCH_U)
    Business Add-in
    FI_BSTM_MC_EXIT                         FI Account Statement: Exit from MultiCash Conversion
    FI_F110_SCHEDULE_JOB                    F110: Check before scheduling a proposal/update run
    No.of Exits:         36
    No.of BADis:          2
    Arunima

  • How to find user exit implemented in the program

    how to find user exit implemented in the program or standerd transaction

    try this program to get the list of all the user exits for a transaction...
    *& Report  Z_USER_EXIT                                                 *
    *REPORT  Z_USER_EXIT                             .
    REPORT z_find_userexit NO STANDARD PAGE HEADING.
    *&  Enter the transaction code that you want to search through in order
    *&  to find which Standard SAP User Exits exists.
    *& Tables
      TABLES : tstc,     "SAP Transaction Codes
               tadir,    "Directory of Repository Objects
               modsapt,  "SAP Enhancements - Short Texts
               modact,   "Modifications
               trdir,    "System table TRDIR
               tfdir,    "Function Module
               enlfdir,  "Additional Attributes for Function Modules
               tstct.    "Transaction Code Texts
    *& Variables
      DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
      DATA : field1(30).
      DATA : v_devclass LIKE tadir-devclass.
    *& Selection Screen Parameters
      SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
      SELECTION-SCREEN SKIP.
      PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
      SELECTION-SCREEN SKIP.
      SELECTION-SCREEN END OF BLOCK a01.
    *& Start of main program
      START-OF-SELECTION.
    Validate Transaction Code
        SELECT SINGLE * FROM tstc
          WHERE tcode EQ p_tcode.
    Find Repository Objects for transaction code
        IF sy-subrc EQ 0.
          SELECT SINGLE * FROM tadir
             WHERE pgmid    = 'R3TR'
               AND object   = 'PROG'
               AND obj_name = tstc-pgmna.
          MOVE : tadir-devclass TO v_devclass.
          IF sy-subrc NE 0.
            SELECT SINGLE * FROM trdir
               WHERE name = tstc-pgmna.
            IF trdir-subc EQ 'F'.
              SELECT SINGLE * FROM tfdir
                WHERE pname = tstc-pgmna.
              SELECT SINGLE * FROM enlfdir
                WHERE funcname = tfdir-funcname.
              SELECT SINGLE * FROM tadir
                WHERE pgmid    = 'R3TR'
                  AND object   = 'FUGR'
                  AND obj_name = enlfdir-area.
              MOVE : tadir-devclass TO v_devclass.
            ENDIF.
          ENDIF.
    Find SAP Modifactions
          SELECT * FROM tadir
            INTO TABLE jtab
            WHERE pgmid    = 'R3TR'
              AND object   = 'SMOD'
              AND devclass = v_devclass.
          SELECT SINGLE * FROM tstct
            WHERE sprsl EQ sy-langu
              AND tcode EQ p_tcode.
          FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
          WRITE:/(19) 'Transaction Code - ',
          20(20) p_tcode,
          45(50) tstct-ttext.
          SKIP.
          IF NOT jtab[] IS INITIAL.
            WRITE:/(95) sy-uline.
            FORMAT COLOR COL_HEADING INTENSIFIED ON.
            WRITE:/1 sy-vline,
            2 'Exit Name',
            21 sy-vline ,
            22 'Description',
            95 sy-vline.
            WRITE:/(95) sy-uline.
            LOOP AT jtab.
              SELECT SINGLE * FROM modsapt
              WHERE sprsl = sy-langu AND
              name = jtab-obj_name.
              FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
              WRITE:/1 sy-vline,
              2 jtab-obj_name HOTSPOT ON,
              21 sy-vline ,
              22 modsapt-modtext,
              95 sy-vline.
            ENDLOOP.
            WRITE:/(95) sy-uline.
            DESCRIBE TABLE jtab.
            SKIP.
            FORMAT COLOR COL_TOTAL INTENSIFIED ON.
            WRITE:/ 'No of Exits:' , sy-tfill.
          ELSE.
            FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
            WRITE:/(95) 'No User Exit exists'.
          ENDIF.
        ELSE.
          FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
          WRITE:/(95) 'Transaction Code Does Not Exist'.
        ENDIF.
    Take the user to SMOD for the Exit that was selected.
      AT LINE-SELECTION.
        GET CURSOR FIELD field1.
        CHECK field1(4) EQ 'JTAB'.
        SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
        CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.

  • How to find user exit for a perticular screen?

    Dear all,
    Can some one tell me how to find user exit for a perticular screen?
    ex: MC88 screen can we figure out are there any user exit for that screen!!
    Regards,
    Vj

    User exits are built into the Standard SAP code. You just activate them and insert your code into the include programs.
    Here is a program that will list the user exits per transaction code. Not perfect, but it may help.
    report z_find_user_exit no standard page heading.
    tables: tstc, tadir, modsapt, modact,
            trdir, tfdir, enlfdir, tstct.
    data : jtab like tadir occurs 0 with header line.
    data : hotspot(30).
    parameters : p_tcode like tstc-tcode obligatory.
    at line-selection.
      get cursor field hotspot.
      check hotspot(4) eq 'JTAB'.
      set parameter id 'MON' field sy-lisel+1(10).
      call transaction 'SMOD' and skip first screen.
    start-of-selection.
      perform get_data.
      perform write_list.
          FORM get_data                                                 *
    form get_data.
      select single * from tstc
                  where tcode eq p_tcode.
      check sy-subrc eq 0.
      select single * from tadir
                where pgmid = 'R3TR'
                  and object = 'PROG'
                  and obj_name = tstc-pgmna.
      if sy-subrc ne 0.
        select single * from trdir
                 where name = tstc-pgmna.
        if trdir-subc eq 'F'.
          select single * from tfdir
                         where pname = tstc-pgmna.
          select single * from enlfdir
                         where funcname = tfdir-funcname.
          select single * from tadir
                         where pgmid = 'R3TR'
                           and object = 'FUGR'
                           and obj_name eq enlfdir-area.
        endif.
      endif.
      select * from tadir into table jtab
                 where pgmid = 'R3TR'
                   and object = 'SMOD'
                   and devclass = tadir-devclass.
      select single * from tstct
              where sprsl eq sy-langu
                and tcode eq p_tcode.
    endform.
          FORM write_list                                               *
    form write_list.
      format color col_positive intensified off.
      write:/(19) 'Transaction Code - ',
      20(20) p_tcode,
      45(50) tstct-ttext.
      skip.
      if not jtab[] is initial.
        write:/(95) sy-uline.
        format color col_heading intensified on.
        write:/1 sy-vline,
        2 'Exit Name',
        21 sy-vline ,
        22 'Description',
        95 sy-vline.
        write:/(95) sy-uline.
        loop at jtab.
          select single * from modsapt
          where sprsl = sy-langu and
          name = jtab-obj_name.
          format color col_normal intensified off.
          write:/1 sy-vline,
          2 jtab-obj_name hotspot on,
          21 sy-vline ,
          22 modsapt-modtext,
          95 sy-vline.
        endloop.
        write:/(95) sy-uline.
        describe table jtab.
        skip.
        format color col_total intensified on.
        write:/ 'No of Exits:' , sy-tfill.
      else.
        format color col_negative intensified on.
        write:/(95) 'No User Exit exists'.
      endif.
    endform.
    SMOD, is where you can find the system modifications provided by SAP. CMOD is where you will implement them. If you are looking for all the enhancements provided, then go to CMOD, follow the menu, 'Utilities-->SAP Enhancements'. This will take you to a screen where if you just execute it, you will get all the enhancements provided by SAP.
    It is always difficult to find a user exit if all you have is a program name or a transaction code, unless you do a program like Rich suggested. But even there, you will not be able to find user exits that are implemented as sub-routines(also called forms not sapscript forms). Most of the user exits are documented under the corresponding task under IMG structure. So use transaction code SPRO, go to the IMG structure, choose the application area that your program or transaction might be and then you should find a task that talks about enhancements. If you execute that task most often it will take you to CMOD and sometimes to SE38. But all you want to know is there in the documentation attached to the task. Then you can go to CMOD and see which components are there.
    Regards,
    Amey

  • How to find user exit in SPRO

    Hi experts,
                 how to find user exit in spro.
    the path is in spro.
    in spro->financial accounting>travel managment>travel expenses>transfer to accounting-->
    define assigment of wage type to symbolic account.
    when u click on this  it will ask for trip provision variant if we key in the work area number thne we get a screen . in that wage test key start date end date so on... are there so in the field KEY its empty so i want to find a user exit.can u please help me in this.
    regards,
    sunita.

    Hi,
    For more information on user exit,
    use the following link.
    Hope it is useful.
    http://****************/Tutorials/ExitsBADIs/ExitsMain.htm
    Regards,
    Phani.

  • Help to find user exit/BADI in cj20n to save requisitioner as use name

    Hi,
    I have requirement in cj20n. Please help me to find user exit or BADI for cj20n which saves requisitioner as user name automatically.
    Thanks,
    Roshani.

    Hi,
    Check this BADI :                   WORKORDER_CONFIRM.
    Goto SE18 ---> Give the above BADI name. If you want to create go to SE19 and use the above definition to create.

  • How to find user exit for the transaction PBAW

    Dear Freinds
                 In Recruitment ....PBAW(Job Advertisements--when we execute the
    transaction PBAW ...we can find create Advertisement...  > here will create posting
    in this screen i have to add a field  Status  . could you please let me know how
    i can add.. Is there any user exit through which i can add a field or there is any way...
    as it is standard..
    regards
    Vamsi.

    Hello Vamsi,
    This might be of help. It is a program to find user exits based on transaction codes. Just install it on your sandbox and see if it works for you.
    http://www.erpgenie.com/abap/code/abap26.htm
    KR,
    Peter Linn

  • How to find User exit for PO

    Hi
    My require ment is system should check for the follwoing PO document type
    i have ctreated new document type with respective PR ,  while creating PO system should check following while saving.(ME21N)
    1.PO,
    2.incoterm,
    3.price,
    4.quantity.
    So for that i want find user exit for PO. can u plz heip me....

    Hi
    You can use the BADI  ME_PROCESS_PO_CUST
    use the methods IM_HEADER and IM_ITEM
    if needed check the following  PO related exits
    Enhancement
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number
    MM06E004                                Control import data screens in purchase order
    MM06E005                                Customer fields in purchasing document
    MM06E007                                Change document for requisitions upon conversion into PO
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator
    MM06E010                                Field selection for vendor address
    MM06E011                                Activate PReq Block
    MMAL0001                                ALE source list distribution: Outbound processing
    MMAL0002                                ALE source list distribution: Inbound processing
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    AMPL0001                                User subscreen for additional data on AMPL
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    M06B0003                                Number range and document number
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    SMOD_MRFLB001                           Control Items for Contract Release Order
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • How to find user exits for a specific field

    hi,
        How can we find a user exit for a specific fields .
    as i know Three ways to search user-exits
    1. SE80 look includes in a packages with name user-exits
    2.  by zreport which will fetch user-exit in a T-CODE
    3. SMOD
    but what if we have to find a user-exit for particular field for e.g bupla(bussiness place) in MIRO.
    Please suggest me.
    Thanks and  Regards ,
    Rahul Singh.

    Hi Rahul,
    Here is the procedure to create field exits.
    Step by step procedure for creating Field Exits
    There are eight steps to creating a field exit:
    Step 1: Determine Data Element
    Step 2: Go To Field Exit Transaction
    Step 3: Create Field Exit
    Step 4: Create Function Module
    Step 5: Code Function Module
    Step 6: Activate Function Module
    Step 7: Assign Program/Screen
    Step 8: Activate Field Exit
    Step 1: Determine Data Element
    u2022     Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
    Step 2: Go To Field Exit Transaction
    u2022     The transaction to create field exits is CMOD.
    u2022     You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
    u2022     From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
    u2022     After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
    NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
    Step 3: Create Field Exit
    u2022     From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
    u2022     After choosing this menu path, a dialog box will prompt you for the appropriate data element .
    u2022     Enter the data element name and click the u2018Continueu2019 pushbutton.
    u2022     Now, you will be able to create the function module associated to the data elementu2019s field exit.
    Step 4: Create Function Module
    u2022     You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the u2018Continueu2019 pushbutton.
    u2022     In the u2018Function moduleu2019 field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
    FIELD_EXIT_<data element>
    u2022     You can add an identifier (an underscore followed by a single character ).
    u2022     The first function module for a data elementu2019s field exit must be created without an identifier.
    u2022     To create the function module, click on the u2018Createu2019 pushbutton, choose menu path Function module -> Create, or press u2018F5u2019.
    u2022     After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing u2018Enteru2019, you will be able to go ahead and create the function module.
    u2022     Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
    Step 5: Code Function Module
    u2022     From the function moduleu2019s attributes screen, click on the u2018Source codeu2019 pushbutton or choose the Goto -> Function module menu path to the code of the function module.
    u2022     Here you will add your desired functionality for the field exit.
    u2022     Remember that field exitu2019s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
    u2022     You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
    Step 6: Activate Function Module
    u2022     After coding the function module, you must remember to activate it.
    u2022     Use the Function module -> Activate menu path to activate the function module.
    u2022     At this point, you can return to the field exit transaction.
    u2022     You should be able to 'green arrow' back to this transaction.
    u2022     When you return to the field exit transaction, you will see an entry for the newly created field exit.
    u2022     At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
    u2022     Also, the field exit will not be triggered yet because it is inactive.
    Step 7: Assign Program/Screen
    u2022     This step is only needed if you want to make a field exit local.
    u2022     To make a field exit local, select the field exit and click on the u2018Assign prog./screenu2019 pushbutton.
    u2022     In the dialog box , indicate the appropriate program name and screen number.
    This information indicates that the field exit is local to the specified screen in the specified program.
    u2022     In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the u2018Fld. Exitu2019 field.
    u2022     If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
    u2022     If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
    Step 8: Activate Field Exit
    u2022     The field exit must be active for it to be triggered by the system.
    u2022     Activate the field exit by choosing the Field exit -> Activate menu path.
    u2022     After assigning the field exit to a change request, its status will change to u2018Activeu2019 and it will be triggered automatically on the appropriate screen(s).
    NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
    Execute the transaction SE38 with PROGRAM NAME - RSMODPRF
    Then give the Data Element Name for which field you want to create the exit(Just cross check with your field data element) and execute.
    then it takes you to SE37 with the function module name FIELD_EXIT_<DATA ELEMENT NAME> and then create the same function module.
    and in the coding part, You can write your logic to display the output of that field. and activate it.
    once you complete the above,
    Again execute SE38 transaction with program RSMODPRF and again click on Execute button without any Data Element Name. Now you select the data element which you have created and click on Assign prog/ Screen button and assign the program name and screen number of the filed and click on the menu Field Exit and Activate.
    Hope it helps.
    Regards
    Radhika
    Edited by: Radhika Pande on Nov 26, 2009 7:58 AM

  • How to find user-exit?

    Hi Friends i have got a requirement of adding new fields in MM01 screen i am trying but i have stricted up in user-exits like i got know tht i have to use EXIT_SAPLMGMU_001 but i am unable to find the user-exit can anyone tell me the procedure how to view and edit the user-exits.
    Thks in Advance

    You can find the exits in many ways.
    Get the developement class of the transaction code from SE93.
    Then go to transaction SMOD and press F4 and give the Development class in Press ENTER, then it will show all the exits available for that transaction.
    Or
    Go to transaction SE80 and give the development class name and then expand the enhancements tree view then you will get the list of userexits for that corresponding dev class.
    Thanks,
    Srinivas

  • How to find user exit for XK01/XK02/MK01/MK02/FK01/FK02

    I am working on an outbound interface and sending data from SAP to external syatem. I need to send the new supplier is created or modified data (transaction XK01/XK02/MK01/MK02/FK01/FK02) an user-exit is called to check which fields had been maintained / modified.
    Can you please help me in identifying how do i find the user exit for the above transactions.
    Thanks and regards
    Amol S

    Hi,
    If you need to find out the user-exits for the transaction which you have listed.
    you can goto T code SE85 under Enhancements -> Customer Exit -> type in the package name for the  tcode you are looking you would get the availlabel exits for the following tcode.
    and smod test those exits.
    Regards,
    Ranjith Nambiar

  • How to find user exit for a specific function

    Hello Gurus,
          I have some question about user exit:
        (1) how can I know which user exit can be used to implement my specific requirement ?
        (2) I think user exit is active subroutine in the main program. so if I know the name of some user exit, how can I get the program code for it ? ( ie. how to get name of main program,  name of include file ? )
    thanks very much!

    Hi friend,
         thanks for your suggestion. I have read that book. but this question is not clear in that book . I'd like to repeat may question again:
       (1) if I want to implement a tailored function by user exit, how can I know which userexit
           should I use ?
       (2.) I wonder if there is a document which shows which userexit corresponds which
           program?
      in fact, if I know the place where I can put my own abap subroutine in , everything will be done.
    thanks very much!

  • How to find User Exit definition

    Hi,
    Please can anyone help me to find a definition of a user_exit routine called in a form trigger.
    I need to where I can find the definition and related code file and how can i obtain it.
    Thanks & Regards,
    Shyam

    Hi Shyam;
    Please see below notes which could be helpful for your issue:
    http://www.exforsys.com/forum/oracle-apps/96606-user_exit-how-to-use.html
    http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28427/pc_20exi.htm
    http://download.oracle.com/docs/cd/A57673_01/DOC/api/doc/PAD18/ch10.htm#toc112
    Regard
    Helios

  • Finding user-exits

    Hi Experts,
    1.How to find the screen Exits and Menu Exits for any Transaction code?
    I know how to find thru SMOD by giving package name and thru MODSAP table.I also know a Z-program is there to find.But i want to find thru SAP program.Like Call Customer function is there any way for finding menu Exits and Screen Exits?
    2. Is access key required to implement Menu and Screen exits in ECC6.0 version?
    3. I will be great full if any body let me know the step by step procedure for implementing screen exit and Menu Exit with an Example in ECC 6.0 version.
    Regards
    Ravi.
    Regards

    1. Finding user exit/BADI
    SMOD, is where you can find the system modifications provided by SAP. CMOD is where you will implement them. If you are looking for all the enhancements provided, then go to CMOD, follow the menu, 'Utilities-->SAP Enhancements'. This will take you to a screen where if you just execute it, you will get all the enhancements provided by SAP.
    It is always difficult to find a user exit if all you have is a program name or a transaction code, unless you do a program like Rich suggested. But even there, you will not be able to find user exits that are implemented as sub-routines(also called forms not sapscript forms). Most of the user exits are documented under the corresponding task under IMG structure. So use transaction code SPRO, go to the IMG structure, choose the application area that your program or transaction might be and then you should find a task that talks about enhancements. If you execute that task most often it will take you to CMOD and sometimes to SE38. But all you want to know is there in the documentation attached to the task. Then you can go to CMOD and see which components are there.
    Finding BADIs
    Business add-ins are enhancements to the standard version of the system.
    Business Add-In is a new SAP enhancement technique based on ABAP Objects.
    They can be inserted into the SAP system based on specific user requirements.
    Each Business Add-In has:
    • at least one Business Add-In definition
    • a Business Add-In interface
    • a Business Add-In class that implements the interface
    In order to enhance a program, a Business Add-In must first be defined
    Subsequently two classes are automatically generated:
    • An interface with ‘IF_EX_’ inserted between the first and second characters of the BADI name.
    • An adapter class with ‘CL_EX_’ inserted between the first and second characters of the BADI name.
    The Application developer creates an interface for this Add-In.
    There are multiple ways of searching for BADI.
    • Finding BADI Using CL_EXITHANDLER=>GET_INSTANCE
    • Finding BADI Using SQL Trace (TCODE-ST05).
    • Finding BADI Using Repository Information System (TCODE- SE84).
    1. Go to the Transaction, for which we want to find the BADI, take the example of Transaction VD02. Click on System->Status. Double click on the program name. Once inside the program search for ‘CL_EXITHANDLER=>GET_INSTANCE’.
    Make sure the radio button “In main program” is checked. A list of all the programs with call to the BADI’s will be listed.
    The export parameter ‘EXIT_NAME’ for the method GET_INSTANCE of class CL_EXITHANDLER will have the user exit assigned to it. The changing parameter ‘INSTANCE’ will have the interface assigned to it. Double click on the method to enter the source code.Definition of Instance would give you the Interface name.
    2. Start transaction ST05 (Performance Analysis).
    Set flag field "Buffer trace"
    Remark: We need to trace also the buffer calls, because BADI database tables are buffered. (Especially view V_EXT_IMP and V_EXT_ACT)
    Push the button "Activate Trace". Start transaction VA02 in a new GUI session. Go back to the Performance trace session.
    Push the button "Deactivate Trace".
    Push the button "Display Trace".
    The popup screen "Set Restrictions for Displaying Trace" appears.
    Now, filter the trace on Objects:
    • V_EXT_IMP
    • V_EXT_ACT
    Push button "Multiple selections" button behind field Objects
    Fill: V_EXT_IMP and V_EXT_ACT
    All the interface class names of view V_EXT_IMP start with IF_EX_. This is the standard SAP prefix for BADI class interfaces. The BADI name is after the IF_EX_.
    So the BADI name of IF_EX_CUSTOMER_ADD_DATA is CUSTOMER_ADD_DATA
    3. Go to “Maintain Transaction” (TCODE- SE93).
    Enter the Transaction VD02 for which you want to find BADI.
    Click on the Display push buttons.
    Get the Package Name. (Package VS in this case)
    Go to TCode: SE84->Enhancements->Business Add-inns->Definition
    Enter the Package Name and Execute.
    Here you get a list of all the Enhancement BADI’s for the given package MB.
    2. No access key will be asked
    3. Step by step procedure
    http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/menu-exits-72696#
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

Maybe you are looking for