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: 

Hi

Former Member
0 Kudos

Hi

Can any one tel me the procedure for adding customizations through user exit and customer exit??

The difference between customer exit and user exit??

Thanks and Regrds

Arun Joseph

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

User exits

-

-


User exit are form exits..Like the sales order user exits..USEREXIT_SAVE_DOCMENT_PREPARE...

User exit does not require any project in CMOD.

Customer exits

-

-


Customer exits are function module exits..Like the Po user exits..

EXIT_SAPMM06E_012...This requires the a project in CMOD and should be activated..in order to trigger the code..

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.

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’t 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…..Basically

designed for all modules.

Refer

https://forums.sdn.sap.com/click.jspa?searchID=10997678&messageID=5232834

https://forums.sdn.sap.com/click.jspa?searchID=10997678&messageID=2584155

Regards

Kiran Sure

6 REPLIES 6

Former Member
0 Kudos

Hi,

User exits

-

-


User exit are form exits..Like the sales order user exits..USEREXIT_SAVE_DOCMENT_PREPARE...

User exit does not require any project in CMOD.

Customer exits

-

-


Customer exits are function module exits..Like the Po user exits..

EXIT_SAPMM06E_012...This requires the a project in CMOD and should be activated..in order to trigger the code..

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.

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’t 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…..Basically

designed for all modules.

Refer

https://forums.sdn.sap.com/click.jspa?searchID=10997678&messageID=5232834

https://forums.sdn.sap.com/click.jspa?searchID=10997678&messageID=2584155

Regards

Kiran Sure

Former Member
0 Kudos

Hi,

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>

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

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.

To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.

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

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

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.

or execute this report

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

which gives the list of exits for a tcode

http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm

For information on Exits, check these links

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

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.

Please check these links for more information.

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

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

http://www.sap-img.com/abap/what-is-user-exits.htm

Regards,

Satish

Former Member
0 Kudos

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

reward if helpful

Former Member
0 Kudos

usually customizations are done through SPRO

user exit - access key required and used in SD module only

customer exit - key is not required and used in SD, MM and FI also

Former Member
0 Kudos

difference between user exit and customer exit:

1)user exit contains subroutine calls within zincludes,customer exits contains function module calls within zincludes.

2)userexits are available for SD module only..acutually these are obsolete..customer exits are available for all modules.

3)access key required for userexits..but no access key for customer exits.

4)userexits have only function exits...customer exits have functionexit,menuexit,screen exit and field exit.

For to add your own functionality to one standard tcode using customer exit requires one project..so create one project with CMOD tcode...assign enhancement name...enter..now you get fucntion exit..duble click on it..it goes to function module..within this you have to write the code..activate..activate your project.

Reward if useful.

Dara.

0 Kudos

Can any one tel me how to find out a user exit and customer exit??