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


difference between user exit and customer exit..dont say both are same same...

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 08:39 AM


    User exit - A user exit is a three character code that instructs the system to access a program during system processing.

    SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.

    UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number

    Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.

    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


    Creating a Project to include the enhancement

    1. Go to transaction CMOD and create a project.

    2. Enter a description for the project. Then, click on the pushbutton ‘Enhancement Assignments’ in the Application Toolbar.

    3. Enter the name of the enhancement and Save.

    4. Go to ‘Components’.

    Creating Custom Include for ANLU

    The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.

    Create the include structure with three new fields, as required. Then, save and activate it.

    Develop the subscreen and the program

    Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.

    Create it as subscreen.

    Then, go to the Layout of the screen and create three new fields from Database table ANLU.

    Drag the fields in the screen body and place them.

    Then, save and activate the screen and come back to screen flow editor.

    Create the PAI module to add validation for field “Location 2”, as required .

    Activate the whole function group and come out.

    Write code in the Function Exits to synchronize the programs

    Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.

    Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:

    Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.

    Then, activate everything – the whole project and come out.

    Complete the configuration to link the subscreen

    The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.

    Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.

    Here, the requirement is to create these three custom fields in the tab page ‘General’ of asset master screen ( AS01/AS02/AS03/AS91).

    Determine the Layout

    To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class ‘1000’ and click on folder ‘General Assignment of Layout’.

    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout ‘SAP’ cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.

    Create new tab layout

    Go to transaction AOLA. Copy the tab layout ‘SAP’ to create another layout, say, YSUB.

    System will copy all the settings and will inform you about that.

    Select your newly created layout and double-click on the folder ‘Tab page titles’.

    You want to put your custom fields in the tab page “General”. So, select this tab page entry and double-click on the folder "Position of Groups".

    Here, all the field groups currently residing in the tab-page “General” are shown. Add an entry for your newly created fields.

    Select the group box from the list. An entry will come with “U” padded with the custom subscreen prepared by you.

    Then, save and come out.

    Assign the new Layout to Asset Class

    Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.

    Save and come out.

    Test the Exit

    Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them…save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.

    <b>Reward points</b>


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 08:37 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 08:41 AM


    ‘User-Exit’ is one of the very first mechanisms provided by SAP to execute custom code in between the standard SAP control flow. This is implemented as subroutine call (PERFORM xxx). A classical example for User-Exit is MV45AFZZ include in order processing module of SAP R/3. Though this include object doesn’t fall under customer namespace, the object doesn’t get overwritten during upgrade.

    ‘Customer-Exit’ is better than the user-exit, in the sense that it is implemented using Function Modules and so has a well defined parameter interface. Also since the custom coding done as part of these customer-exits is located away from the original SAP code, the maintenance is easier than user-exits.


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 12, 2007 at 12:20 PM

    Hi Satesh,

    It is very good question there is a difference between user exit and customer exit .

    <b> User-exits(modifications)</b>

    USER EXITS are FORMS and are called by SAP standard programs using PERFORM.

    Inside the form (user exit) you can read and change almost any global data from host program.

    User exits are more flexible because you have more information to use in your code but on the other hand , it is very easy to manipulate erroneously global data and lead the standard program to a dump or even to make database inconsistent.

    User-exit doesn’t have any classification.

    Basically designed For SD module

    User-exits can be written only using access-key

    With user-exits the code , the developer has written will not be there for next version unless modification assistance tool is used

    <b> Customer-exits(enhancements)</b>

    CUSTOMER EXITS are FUNCTIONS so they are called using CALL FUNCTION (or more exactly CALL CUSTOMER FUNCTION).

    Inside a function (customer exit) you can only acces your import/export/changing/tables parameters.

    Customer exits are more restrictive but you are sure any change you can make to any parameters will never lead to inconsistency

    In customer-exit we have function-module exit , screen exit , menu exit

    Are available for MM,SD,FI,HR…..Basically designed for all modules.

    No need of access key

    Customer-exits are not wiped during upgradation

    This are the difference b/w these two.

    Hope i have answered ur question 😊

    Reward pts if found usefull 😊 😊



    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.