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.
Showing results for 
Search instead for 
Did you mean: 

hi guru's i am learner

Former Member
0 Kudos

hi guru's i am learner i want to learn user exists plz help me


Former Member
0 Kudos

Former Member
0 Kudos

Former Member
0 Kudos


give me ur mail id i will send you all material.



0 Kudos

hi paras , my mail id is @

i am waiting for ur...

Former Member
0 Kudos


User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...

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

SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.

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.

which gives the list of exits for a tcode

For information on Exits, check these links


These links will help you to learn more on user exits.

Also please check these threads for more details about user exits.

1. Document on UserExits in FI/CO

2. Finding User Exits...

3. List of all User Exits...