Skip to Content
avatar image
Former Member

user exit

Hello All

Could you please explain me about the user exit as i am not aware of it.Where do we can find the user exist in what context they are user.Can you please forward documents regarding the user exits

Thanks a lot

Regards

T.Srikanth.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Nov 05, 2008 at 05:58 AM

    Dear Srikanth,

    user exit

    Customer Enhancements

    A point in an SAP program where a customer's own program can be called.

    In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System. On upgrade, each user exit must be checked to ensure that it conforms to the standard system.

    There are the following types of user exit:

    User exits that use INCLUDEs -

    These are customer enhancements that are called directly in the program.

    User exits that use tables -

    These are used and managed using Customizing.

    To find the SD related User Exits go through this IMG path

    SPRO>IMG>sales and distribution>System modifications>User Exits here you can find all SD related user exits.

    I hope this will help you,

    Regards,

    Murali.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 05, 2008 at 06:17 AM

    Dear Thalapalli,

    User Exits:

    The original purpose of user exits was to allow the user to avoid modification adjustment.

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

    The SAP developer creates a special include in a module pool. These includes contain one or more subroutines routines that satisfy the naming convention userexit_<name>.

     The calls for these subroutines have already been implemented in the R/3 program.

     Usually global variables are used.

    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.

    User exits are actually empty subroutines that SAP developers provide for you. You can fill them with your own source code.

     The purpose behind this type of system is to keep all changes well away from program source code and store them in include programs instead.

     To this end, SAP developers create various includes that fulfill the naming conventions for programs and function groups.

     The last two letters in the name of the include refer to the include that the customer should use: "Z" is usually found here.

    Example: Program SAPM45A

    Include M45AFZB

    This naming convention guarantees that SAP developers will not touch this include in the future. For this reason, includes of this nature are not adjusted during modification upgrade.

     The subroutine call is already implemented in the program. The interface is already defined.

     Normally, subroutines of this type only work with global data.

    If any new user exits are delivered by SAP with a new release, then they are bundled into new includes that adhere to the same naming convention.

    enhancements

    it is used to enhance a sap object without actually modifying the object

    customer exits The 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 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. That is already SAP provided some space to write our own functionality that space is nothing but hooks.

    If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications.

    advantages are

    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.

    Best Regards,

    Amit

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Dear Thalapalli,

      Please have look at the following menu path:

      SPRO --> IMG --> Sales and Distribution --> System Modification --> User Exits

      If you click the page-icon (just before the execute button), you can find the doumentation for the relevant userexits.

      Best Regards,

      Amit