What is diff b/w user & customer exit

[Former Member]

Hi

Good afternoon everybody,

Plz differentiate user exit and customer exit.

What is the way to findout user exits and how to modify it.

Thanks in advance

Venkat

[Former Member]

Hi

Good afternoon everybody,

Plz differentiate user exit and customer exit.

What is the way to findout user exits and how to modify it.

Thanks in advance

Venkat

[Former Member]

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."

Customer exits are implemented in Z-includes and are ENHANCEMENTS to the system.

User-exits were firstly intended to be developed for the SD module. You make your coding in includes in SAP namespace (e.g MV*). That's why, user exits are MODIFICATIONS to the system. In includes for user exits there are empty subroutines ( generally with the name convention "userexit_...") and you code using global variables of the main program.

But, generally developers use these terms without this distinction. So, someone may mean a "customer exit" when (s)he says "user exit" or vice-versa.

[Former Member]

Generally the Form exits (Mostly in SD) is called user exits. You can find the documentation from the appropriate link in SPRO, where as the FM exits is called Customer exits(SMOD/CMOD).

Warm Reards

Anup Varghese

[Former Member]

Some good reads from the forum;

Hope this helps.

Sudha

[Former Member]

Hi Venkat,

Check the following description

Customer exits: 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.

If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard R/3 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.

In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System.

User exits: 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.

I hope this helps.

Regards,

Kinshuk

[Former Member]

Once ur querery is resolved close the thread....ok

[Former Member]

HI,

Refer this link for the difference..

how to check the predefined user exits for a particular transaction

Type the transaction : system->status-> <PROG. NAME>

2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.

3. Open CMOD utilities->SAP enhancements

EDIT->All selections

4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.

5. The displayed list contains the enhancements names for the transaction You were looking for.

6. Create a project in CMOD and the code in default include->activate.

here is a link for the program to find the user exit for a particular transaction

Rgds,

Prakash.

<b>Note:- reward if helpful.</b>

[Former Member]

HI,

Customer Exits :

Pre-planned enhancement to the standard SAP system.

SAP anticipates potential customer requests not already implemented in the standard system by predefining them as 'empty modification modules'. Customers fill these modules with their own logic according to their own requirements.

SAP creates customer exits with transaction SMOD. From these customer exits, customers then use transaction CMOD to choose the enhancements they want to process, assign them to enhancement projects, edit the components, and activate the relevant projects.

Using customer exits guarantees upwards compatibility. This is because jumps to exits are predefined in the standard software and the validity of the call interface are both retained, even in future release upgrades.