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

Reg userexits?

Hi All,

What is diff bw User Exits and Customer Exits?

Thanks&Regards,

Srikanth

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 10, 2008 at 11:17 AM

    Hi Srikanth,

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

    The following document is about exits in SAP :-

    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 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 item’s 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 screen’s 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 ‘001’.

    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 company’s 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.

    Regards,

    Points If Helpful,

    Phani.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 10, 2008 at 11:20 AM

    Hi,

    These r the main differences between user exits and customer exits

    1) user exits r subroutines where as customer exits r function modules

    2) user exits r not upgraded where as customer exits r will upgrade

    3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode

    4) customer exits r reusable where as user exits r not reusable.

    Also:

    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:

    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm

    http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm

    http://sap.niraj.tripod.com/id21.html

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

    http://www.sap-img.com/ab038.htm

    User Exits.

    -


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

    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

    customer exits

    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d

    Menu Exit.

    http://www.sappoint.com/abap/spmp.pdf

    http://www.sappoint.com/abap/userexit.pdf

    http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm

    http://www.sapdevelopment.co.uk/enhance/enhancehome.htm

    1. Previously there were only user-exits.

    2. Then came the concept of customer-exits.

    3. user exits were nothing but subroutines

    FORM/PERFORM

    called from standard programs.

    4. The FORM defintion was placed inside

    an empty include file.

    5. So It was called EVERYTIME.

    and we need to MODIFY/REPAIR the

    standard include .

    6. Then it came with concept of customer-exit

    7. It consists of calling a FUNCTION MODULE,

    which is called only if

    the user-exit is ACTIVATED (other wise not called)

    In this case, the code in put inside

    a pre-defined Z include.

    8. Functionality of both is same, howerver

    we can note the following important differences

    a) Customer exit is called only if activated.

    (hence, it does not waste resources)

    b) in customer exit, REPAIR does not happen

    to the standard include.

    Exits are basically the hooks whcih SAP has provided to add your own code.

    User Exits: These are provided only SD module .

    They are Empty subroutines with naming like USEREXIT_.

    We need to have Access key to implement them.

    Customer Exits: These are enhancement techniques.

    There are defined in SMOD and implemented in CMOD.

    Types of Customer exits: Function exit, Screen Exit, Menu exit.

    User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...

    Customer Exit,

    Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.

    Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.

    Customer Exit

    -


    SAP creates customer exits for specific programs, screens, and menus within standard 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.

    If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:

    • They do not affect standard SAP source code

    When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.

    • They do not affect software updates

    When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.

    Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits

    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm

    SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.

    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm

    User Exits: allow you to add additional functions to the SAP standard.

    Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.

    Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).

    Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors

    Reward Points if found helpfull..

    Cheers,

    Chandra Sekhar.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 10, 2008 at 11:37 AM

    Hello Srikanth,

    <b>In Simple terms </b>

    User exits are nothing but standard includes,which reuqires access key inorder to write the code....it over writes standard SAP functionality....example in se80 give the program name as SAPMV45A...and open the subroutines node..u can see the userexits_*....

    Customer exits starts with z includes, and it doesn't require any access keys...u have to create a project and atatch ur enhancemnet to it and activate the function exits......it will enhance the SAP functionality..

    <b>******REWARD WITH POINTS,IF FOUND USEFUL</b>

    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.