Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

What is the difference between User Exit & Customer exit

Former Member
0 Kudos

Hi All,

What is the difference between User Exit & Customer exit in Idoc related

Regards

1 ACCEPTED SOLUTION

Former Member

1 1.

USER EXITS are FORMS and are called by SAP standard programs

using PERFORM.

CUSTOMER EXITS are FUNCTIONS so they are called using CALL

FUNCTION (or more exactly CALL CUSTOMER FUNCTION).

2.

Inside the form (user exit) you can read and change almost

any global data from host program.

Inside a function (customer exit) you can only acces your

import/export/changing/tables parameters.

3.

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.

Customer exits are more restrictive but you are sure any

change you can make to any parameters will never lead to

inconsistency

4.

User-exit doesnâu20ACu2122t have any classification.

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

, menu exit.

5.

User exits are Basically designed For SD module.

Costomer exits Are available for MM,SD,FI,HRâu20AC¦..Basically

designed for all modules.

Regards,

Shashi..

6 REPLIES 6

former_member181995
Active Contributor
0 Kudos

Vamsi,

please do not throw this kind of threads.before throwing the thread to SDN try to search urself. here i search with term *User Exit & Customer exit * i got answer.

please close this thread.

Amit.

Former Member

1 1.

USER EXITS are FORMS and are called by SAP standard programs

using PERFORM.

CUSTOMER EXITS are FUNCTIONS so they are called using CALL

FUNCTION (or more exactly CALL CUSTOMER FUNCTION).

2.

Inside the form (user exit) you can read and change almost

any global data from host program.

Inside a function (customer exit) you can only acces your

import/export/changing/tables parameters.

3.

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.

Customer exits are more restrictive but you are sure any

change you can make to any parameters will never lead to

inconsistency

4.

User-exit doesnâu20ACu2122t have any classification.

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

, menu exit.

5.

User exits are Basically designed For SD module.

Costomer exits Are available for MM,SD,FI,HRâu20AC¦..Basically

designed for all modules.

Regards,

Shashi..

Former Member
0 Kudos

hi,

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.

Eg: go to any sap std. pgm.Go to edit menu->find next->find for call cutomer-function. you can see different call customer-functions ...these are customer exits.

in some pgms u can see perform userexit_.....these are user exits.

There are different types of customer exits like field exit,function module exit etc

may this helps you.....

regards,

praveena.

Former Member
0 Kudos

Hi,

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.

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

User Exits:

-

-


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 in the enhancement process.

Reward If Helpfull,

Naresh

Former Member
0 Kudos

Thanx

Former Member
0 Kudos

Example for User exit : includes MV45AFZZ,MV45AFZB.... for pricing condition in SD module.