Skip to Content
author's profile photo Former Member
Former Member

user exits and Badis

Hi friends,

Can any one send me a simple notes how to use User exit and Badis . I need to learn from scratch what is that. Do any one can explain me these two objects as per real time in a simple way. I have the sites but i cannot understand on comparing with real time.

Satish raju


Add comment
10|10000 characters needed characters exceeded

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 26, 2007 at 12:40 PM

    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 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_.


    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.

    Have a look at



    How to develop BADI

    Best Regards,

    Vibha Deshmukh

    <b>*Plz mark useful answers</b>

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 27, 2007 at 07:10 AM


    <b>User exits :</b>

    1. Introduction

    2. How to find user exits

    3. Using Project management of SAP Enhancements

    1. Introduction:

    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.

    The naming standard of function modules for functionmodule exits is:

    EXIT_<program name><3 digit suffix>

    The call to a functionmodule exit is implemented as:

    CALL CUSTOMER.-FUNCTION <3 digit suffix>


    The program for transaction VA01 Create salesorder is SAPMV45A

    If you search for CALL CUSTOMER-FUNCTION i program

    SAPMV45A you will find ( Among other user exits):



    xvbak = vbak

    xvbuk = vbuk

    xkomk = tkomk


    lvf_subrc = lvf_subrc


    xvbfa = xvbfa

    xvbap = xvbap

    xvbup = xvbup.

    The exit calls function module EXIT_SAPMV45A_003

    2. How to find user exits?

    Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT

    If you know the Exit name, go to transaction CMOD.

    Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.

    You will now come to a screen that shows the function module exits for the exit.

    3. Using Project management of SAP Enhancements, we want to create a project to enahance trasnaction VA01 .

    - Go to transaction CMOD

    - Create a project called ZVA01

    - Choose the Enhancement assign radio button and press the Change button

    In the first column enter V45A0002 Predefine sold-to party in sales document.

    Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed

    Press Save

    Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.

    Now the function module is displayed. Double click on include ZXVVAU04 in the function module

    Insert the following code into the include: E_KUNNR = '2155'.

    Activate the include program. Go back to CMOD and activate the project.

    Goto transaction VA01 and craete a salesorder.

    Note that Sold-to-party now automatically is "2155"


    The use of object orientated code within SAP has lead to new method of enhancing standard SAP code called

    Business Add-Ins or BADI's for short. Although the implementation concept is based on classes, methods and

    inheritance you do not really have to understand this fully to implement a BADI. Simply think of methods

    as a function module with the same import and export parameters and follow the simple instructions below.


    1. Execute Business Add-In(BADI) transaction SE18

    2. Enter BADI name i.e. HRPBSGB_HESA_NISR and press the display


    3. Select menu option Implementation->Create

    4. Give implementation a name such as Z_HRPBSGB_HESA_NISR

    5. You can now make any changes you require to the BADI within this

    implementation, for example choose the Interface tab

    6. Double click on the method you want to change, you can now enter

    any code you require.

    7. Please note to find out what import and export parameters a

    method has got return the original BADI definition

    (i.e. HRPBSGB_HESA_NISR) and double click on the method name

    for example within HRPBSGB_HESA_NISR contract is a method

    8. When changes have been made activate the implementation

    <b>Reward points if it solves ur query or answer is helpful</b>



    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 27, 2007 at 09:34 AM

    Hi friend,

    gothrough this navigation.

    se93->provide for which transaction code u want to impliment the badi->display option->copy the package name.


    se18->press f4 help->information system->provide the package name->enter

    It will display the all the badis.

    provode the badi name->select implimentation option in menubar->create->prvide the implimantation name->enter

    provide the implimantation shrt text->save the badi.

    Go for the interface option->double click onthe method->provide the coding in between method and endmethod. and active the badi.

    program automatically call this badi and execute u code.

    This is the badi.


    1) execute Tcode SE18.

    2) Specify a definition Name : ZBADI_SPFLI

    3) Press create

    4) Choose the attribute tab. Specify short desc for badi.. and specify the type :

    multiple use.

    5) Choose the interface tab

    6) Specify interface name: ZIF_EX_BADI_SPFLI and save.

    7) Dbl clk on interface name to start class builder . specify a method name (name,

    level, desc).

    Method level desc

    Linese;ection instance methos some desc

    8) place the cursor on the method name desc its parameters to define the interface.

    Parameter type refe field desc

    I_carrid import spfli-carrid some

    I_connid import spefi-connid some

    9) save , check and activate…adapter class proposed by system is

    ZCL_IM_IM_LINESEL is genereated.


    1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.

    2) Specify aname for implementation ZIM_LINESEL

    3) Specify short desc.

    4) Choose interface tab. System proposes a name fo the implementation class.

    ZCL_IM_IMLINESEL which is already generarted.

    5) Specify short desc for method

    6) Dbl clk on method to insert code..(check the code in “AAA”).

    7) Save , check and activate the code.

    Some useful URL

    Now write a sample program to use this badi method..

    Look for “BBB” sample program.


    data : wa_flights type sflight,

    it_flights type table of sflight.

    format color col_heading.

    write:/ 'Flight info of:', i_carrid, i_connid.

    format color col_normal.

    select * from sflight

    into corresponding fields of table it_flights

    where carrid = i_carrid

    and connid = i_connid.

    loop at it_flights into wa_flights.

    write:/ wa_flights-fldate,


    wa_flights-price currency wa_flights-currency,






    *& Report ZBADI_TEST *

    *& *


    *& *

    *& *



    tables: spfli.

    data: wa_spfli type spfli,

    it_spfli type table of spfli with key carrid connid.

    *Initialise the object of the interface.

    data: exit_ref type ref to ZCL_IM_IM_LINESEL,

    exit_ref1 type ref to ZIF_EX_BADISPFLI1.

    selection-screen begin of block b1.

    select-options: s_carr for spfli-carrid.

    selection-screen end of block b1.


    select * from spfli into corresponding fields of table it_spfli

    where carrid in s_carr.


    loop at it_spfli into wa_spfli.

    write:/ wa_spfli-carrid,





    hide: wa_spfli-carrid, wa_spfli-connid.


    at line-selection.

    check not wa_spfli-carrid is initial.

    create object exit_ref.

    exit_ref1 = exit_ref.

    call method exit_ref1->lineselection


    i_carrid = wa_spfli-carrid

    i_connid = wa_spfli-connid.

    clear wa_spfli.

    This is for Exits:

    e.g. EXIT_SAPMV45A_002

    This exit is found in SD in enhancement V45A0002.








    We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit , it is required to create the project by using CMOD

    selecting the enhancement e.g. V45A0002 and selecting the component

    (one which fulfills our need) i.e the exit which will be implemented in SMOD and after coding has been done the project has to be activated.

    An exit can be coded only once.


    These are used to add functionality through ABAP code . These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any type of exit including function exits.

    The function exits are called from the standard SAP program in the form of ABAP statement


    This is in contrast to USEREXITs where PERFORM statement is used to call the required userexit. To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its components the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.

    ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation

    To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no. V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components . In the components you will see the exit EXIT_SAPMV45A_002 . This exit is used for our purpose.

    Double clicking on this exit will takes us to function builder (SE37) . This function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e if we move the desired customer name to this

    structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order.

    This function also contains a customer include ZXVVA04 . This include will be used to write our custom code .

    Double clicking on this include and it will prompt us that this include does not exists do you want to create this object ,select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.

    e.g. E_KUNNR = 301.

    Activate the include and Activate the project. Now when ever the SALES ORDER will be created , sold-to-party field will come up with a predefined customer .


    The field exits are managed, created, activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.

    The format of field exit is :

    FIELD_EXIT_dataelement_A-Z or 0-9

    If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.

    The function module associated with field exit shows two parameters INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3 , We can write our own code to change the output parameter depending upon our requirements.

    Before the field exit can have any effect the system profile parameter ABAP/FIELDEXIT in all the application servers should be set to YES


    ************Rewards some points.


    P.Naganjana Reddy


    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 21, 2011 at 08:01 AM


    Add comment
    10|10000 characters needed characters exceeded