Application Development and Automation 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: 
Read only

hi

Former Member
0 Likes
667

hi,

can anyone tell the diff b/w USER EXIT & CUSTOMER EXIT

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
643

hI,

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.

MORE >>>>>>>>>>>>

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 ❤️ digit suffix>

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.

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

A customer exit is a type of user exit. A user exit is a handle that SAP put into their code, allowing a customer to add their own routines

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

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.

they both are the same thing. Only in the program they are written as CALL CUSTOMER FUNCTION, thats why many times they referred as customer exit.

rewards if useful,

regards,

nazeer

hi,

can anyone tell the diff b/w USER EXIT & CUSTOMER EXIT

4 REPLIES 4
Read only

Former Member
0 Likes
644

hI,

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.

MORE >>>>>>>>>>>>

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 ❤️ digit suffix>

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.

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

A customer exit is a type of user exit. A user exit is a handle that SAP put into their code, allowing a customer to add their own routines

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

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.

they both are the same thing. Only in the program they are written as CALL CUSTOMER FUNCTION, thats why many times they referred as customer exit.

rewards if useful,

regards,

nazeer

Read only

Former Member
0 Likes
643

Hi,

<u><b>Difference between user exits & customer exits:</b></u>

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.

Regards,

Bhaskar

Read only

Former Member
0 Likes
643

Hi soni,

The differences between customer exit and user exit is mentioned below.

<b>Customer exit :</b>

1) customer exits are enhancement to the system.

2)upward compatability is guaranted.

3) Adding our won functionality to SAP std business applications without having to modify the original applicaiton.

4) Provided to the customer in the form of function module which holds the include in the customer namespace.

<b>User Exit :</b>

1) User Exit are modification to the system.

2) upward compatability is not guaranted.

3) Modification is done here.

4) It is given in the form of empty subroutine.

Regards....

Arun.

Reward points if useful.

Read only

Former Member
0 Likes
643

hi

good

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:

-


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.

Replacement Path :

Using Replacement Path in your Text and Formula variables, replace values held in a characteristic. The Characteristic value variables are replaced by the results of a query at run-time.

Check this,

http://www.sd-solutions.com/documents/SDS_BW_Replacement Path Variables.html

Authorization :

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

thanks

mrutyun^