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



What is used for User Exists?

How prepared for User Exists?



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

6 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 07:53 AM

    User Exits are also called as BADI's (Business ADIns.)

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 08:04 AM

    Hi Suresh,

    Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:

    1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.

    2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.

    BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)

    Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.

    Please go through the following link which will help you understand the exits in a much better way:

    User Exits.


    customer exits

    Menu Exit.

    USER EXIT,295199,sid63_gci982756,00.html

    Field Exit

    If you are in 4.7 and up follow this

    1. Run report RSMODPRF

    2. Run on the selection screen

    3. In list Field Exit > Create

    4. Give your data element

    5.System will generate the FM FIELD_EXIT_XXXXX

    6. Activate it.

    7. Select your field exit and assign to your program and screen

    8. Select again .. Field exit > Activate

    If you are in version below 4.7

    1. CMOD

    2. Go to >Text enhancment > Field exit

    then follow the same step from 3 onwards as given above.

    Menu Exit

    Procedure for Creating MENU Exits.

    1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command


    2) In Area Menu Paramenter type 'S000' (S triple Zero)

    3) Then Press Change Icon in Application Tool Bar. Then It may ask for

    Access Key [or] it may display "Specify Processing mode" window. If it ask

    for the Access Key Check for the availability of OSS Note and apply to open

    Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify

    Processing mode" window with Three Push Button. In which select "Change" and

    proceed further.

    4) Then it will display "Information" window with the following information

    "Caution : The Original Language of the structure is German (editing lang. :

    English) ". Then press "Enter Key to proceed further.

    5) Then you will get into "Edit Area Menu S000".

    6) for eg:- Expand Tools Menu.

    7) Then Press ABAP Workbench <Icon>.

    8) Then you will get into ABAP Workbench Menu Tree.

    9) Then Expand Utilities Menu.

    10) In the last line you will find one MENU EXIT Provision to include your

    own menu. "Node Text Not Found" This text can be change by double Clicking

    that. There you can find the T.Code. Here for Eg:- "+DW4".

    11) for eg: - Here change the Text to "Sample Menu Exit" and then note down

    the T.Code "+DW4".

    12) Then Save with Change Request Number and come out of Transaction SE43.

    13) Then Goto Transaction SE93.

    14) Then type T.Code "+DW4" and press Create.

    15) Then proceed further to create transaction called "+DW4".

    I hope this could help you in Creating Menu Exit...

    Creating menu exits



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 08:13 AM

    hmmm well. above information is enough i sense, though i got to clarify some things.

    User exits are NOT also called BADI´s or Customer exits.

    User-Exits and BADI´s as well as Customer exits or Enhancement pionts are various technologies around the same subject.

    All of this solutions are made to enable the user to make code additions without modifying.

    But still a user exit is something completeley diffenrent than a BADI or a Customer exit.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 07:34 AM

    .Code SE18 is used to Identify the BADI available.

    Look for the string 'CL_EXITHANDLER' in the standard program. This is a class which has a method 'GET_INSTANCE' which is used to trigger BADI's from the Standard Program. The interface parameter for this static method 'EXIT_NAME' is used to pass the BADI to the method.

    Open Standard Program and do a global search 'CL_EXITHANDLER'.

    SE18 > give the BADI name found through above search.

    CUSTOMER_ADD_DATA > which has a method SAVE_DATA.

    T.Code SE19 is used to Implement BADI.

    SE19 > give the implementation name > Give the Definition name as CUSTOMER_ADD_DATA and the Short Text.


    Check these links for info about badi..





    New to Badi

    check any fo the below links. this will def help u.

    And also download this file....

    There are other tutorials on this site...

    What are BAdIs?

    -> is an anticipated point of extension – these points act like sockets and exist in the original source code

    -> based on ABAP Objects. BAdI defines an interface that can be implemented by BAdI-implementations that are transport objects of their own

    ->Important! There are 2 roles: Enhancement Option-provider & Implementer.

    -> In the above context, Enhancement Implementation can be done only if option (hook) is provided by the Option-provider. In simple words there are no implicit BAdIs.

    Note: In the following slides, Definitions are created so as to understand the method of BAdI definition & for example purpose. As stated above this is the role of Enhancement Option-Provider.

    Classic BAdIs already exist since SAP Release 4.6

    BAdIs have been Re-implemented in ECC7.0 under the new Enhancement Framework & Switch Framework

    Classic BAdIs

    To understand what a powerful pattern a BAdI is, we will now define & then implement a BAdI

    BADI Class is created automatically.

    The various options are described below in detail:

    1. Enhanceable: Enhanceability of filter types can only be specified for filter-dependent BADI definitions under very special conditions. For example, the domain belonging to the filter type must be linked with a value table that is of the type E or G. A BADI implementation can then be created in one step by creating a new filter value that is automatically entered into the value table at save and also copied into the transport order of the BADI implementation. In addition, it is also possible to create a new filter value and, at the same time, a BADI implementation with the same name. Naturally, you can also specify existing filter values.

    You should select this feature if there is a prerequisite that a new filter value is created together with a new BADI implementation - that is, that BADI implementations are not created solely with existing filter values, although this, too, is possible.

    2. Multiple-Use

    3. Filter-Dependent

    Instance Methods can access all of the attributes of a class and can trigger all events of a class. Static Methods can only access static attributes and static events.



    Events can be defined in classes or in interfaces. Corresponding methods can trigger these events with the RAISE EVENT statement. Each class (or interface) that is going to handle the corresponding event must implement a relevant handler method, and register it using the SET HANDLER statement. When an event occurs, the system calls all of the handler methods registered for that event.

    Like method definitions, events have a parameter interface. The only difference is that events may only have EXPORTING parameters.

    BADI : Businees Add IN's

    Business Add-Ins are SAP enhancement technique based on ABAP Objects.

    Where the SAP standard program is not going to fullfill the client requirement , we are going to add our own program to SAP standard program, without changing the standard prog.

    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

    Each BADI has two different Views.

    1.Definition view

    2.Implementation view

    T.C for BADI Definition is SE18.

    T.C for BADI Implementation is SE19.

    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

    Rewards if useful.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 07:47 AM


    user exists same as BADI???


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 08:00 AM

    Hi Suresh,,

    BADI are also the customer exits,

    User Exits.

    User exits are a type of system enhancement that were originally developed for the R/3 SD.

    The SAP developer creates a special include in a module pool. These includes contain one or more subroutines that satisfy the naming convention userexit_<name>. The calls for these subroutines have already been implemented in the R/3 program. [Refer Conventional SD User exits Slides]

    A user exit is considered a modification, since technically objects in the SAP namespace are being modified.

    After delivering them, SAP never alters includes created in this manner; if new user exits must be delivered in a new release, they are placed in a new include program.

    Types of Customer exits..

    Function module exits

    Menu Exits.

    Screen exits.

    Locating Customer Exits: SMOD

    Execute transaction SE81.

    Business Add-Ins

    Similar to user exits, helps hook custom enhancements to SAP functionality

    Definition / Implementation

    Transactions SE18 (Definition) / SE19 (Implementation)

    BADI Vs User Exits –

    BADIs are object oriented

    BADI’s can be implemented multiple times

    Demo on SE18 / SE19

    rewards if useful


    Mohinder Singh Chauhan

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.