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

wht is difference bet. user exit andcustomer exit

Hi expart

wht is difference bet. user exit andcustomer exit

Regards

Bhabani

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 May 19, 2008 at 12:56 PM

    customer exits are provided to the customer in the form of function module which holds the include in the customer namespace. the user can add own source code in it. this is an enhancement. This doesnot affect sap std source code.

    user exits are empty sub routines that the sap provides . you can fill it with your own source code. this is a modification. this affect the source code.

    user exits means there is need of access key, as we are going to modify the sap std. code. whereas customer exits don't need access keys.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 19, 2008 at 12:57 PM

    Hi,

    Nothing much really.

    User exit is usually a subroutine , where as customer exit is a function module. there fore you will see form endform example program : mv45afzz ( sales order user exits )

    The visibility of data is higher in case of user exit as it is a part of the main program.

    But customer exit you only have visibility to the data that is passed in the function module.

    example : from function module idoc_input_orders

    CALL CUSTOMER-FUNCTION '005'

    TABLES

    didoc_data = idoc_data

    didoc_status = idoc_status

    didoc_cntrl = idoc_contrl

    dreturn_variables = return_variables.

    regards,

    Advait

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 19, 2008 at 01:00 PM

    Dear friend,

    i am sending you a tutorial for the

    diff between these two.

    pls go through it if there is any problem

    pls keep in touch.

    REWARDS are expecting.

    vivek srivastava

    What is User Exits and Customer Exits?

    Difference between user exits & customer exits:

    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 SAPu2019s 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. *-- Mani

    The following document is about exits in SAP :-

    The R/3 enhancement concept allows you to add your own functionality to SAPu2019s standard business applications without having to modify the original applications.

    SAP creates user 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.

    Types of Exits

    There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.

    Menu Exits

    Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.

    SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu itemu2019s text when activating the item in an add-on project.

    Screen Exits

    Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screenu2019s flow logic.

    Function Module Exits

    Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.

    When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.

    Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.

    These calls have the following syntax:

    CALL CUSTOMER-FUNCTION u2018001u2019.

    Field Exits

    Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companyu2019s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.

    The field exit concept lets you create a special function module that contains this logic.

    You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.

    In 4.6c, you can use "RSMODPRF" program to create field exits.

    An example of a user exits :-

    MODULE user_exit_0001 INPUT

    CASE okcode.

    WHEN 'BACK OR EXIT'.

    CASE sy-dynnr.

    WHEN '100'.

    SET SCREEN 0.

    LEAVE SCREEN.

    WHEN '200'.

  • Note that you can write any code that satisfy your needs. ****

  • But in this case, this was wrote as a sample code for reference sake. ****

  • And you can test it. ****

    SET SCREEN 100.

    LEAVE SCREEN.

    ENDCASE.

    ENDCASE.

Add a comment
10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 19, 2008 at 01:04 PM

    Hi,

    USER EXITS->

    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>

    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

    CUSTOMER EXITS-> t-code CMOD.

    As of Release 4.6A SAP provides a new enhancement technique, the Business Add-Ins.

    Among others, this enhancement technique has the advantage of

    being based on a multi-level system landscape (SAP, country versions, IS solutions, partner,

    customer, and so on)

    instead of a two-level landscape (SAP, customer) as with the customer exits.

    You can create definitions and implementations of business add-ins at any level of the system landscape.

    To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.

    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm

    *****************

    In order to find out the user exits for any tcode,

    1. get the developement class of the tcode from SE93.

    2. Now goto transaction SMOD and press F4,

    3. give in the Deve class in the dev class and Press ENTER

    this will show u the exits for any tcode.

    or execute this report

    http://www.erpgenie.com/sap/abap/code/abap26.htm

    which gives the list of exits for a tcode

    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm

    For information on Exits, check these links

    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

    http://www.sapgenie.com/abap/code/abap26.htm

    http://www.sap-img.com/abap/what-is-user-exits.htm

    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

    http://www.easymarketplace.de/userexit.php

    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

    http://www.sappoint.com/abap/userexit.pdfUser-Exit

    Reward points if helpfull

    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.