0% found this document useful (0 votes)
2 views

Enhancements_Doc

The document outlines the enhancements available in SAP's standard business applications, focusing on User Exits and Customer Exits. User Exits allow for custom code insertion in empty subroutines specific to the SD module, while Customer Exits are available across all modules and involve adding functionality through function modules. It also details the steps to find, verify, and implement these enhancements, along with the differences between User Exits and Customer Exits.

Uploaded by

arun r m
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views

Enhancements_Doc

The document outlines the enhancements available in SAP's standard business applications, focusing on User Exits and Customer Exits. User Exits allow for custom code insertion in empty subroutines specific to the SD module, while Customer Exits are available across all modules and involve adding functionality through function modules. It also details the steps to find, verify, and implement these enhancements, along with the differences between User Exits and Customer Exits.

Uploaded by

arun r m
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Enhancements:

 Allows to add own functionality to SAP's standard business applications without having to
modify the original applications

Types of Enhancements:

1. User Exit:
 Initially SAP implemented enhancements in the form of User Exits
 User exits are implemented in the form of subroutines and hence are also called as
FORM EXITS
 User exits are empty subroutines that SAP developers have provided for you, you can
add your own source code in the empty subroutines
 All user exits start with the word USEREXIT.
 Only available in SD module

Steps to find User Exit:

1. Find the User Exit


a. SE93  Enter the Transaction code ( Eg: VA01 )  Display
b. Double click on Program name
c. Click on Find Icon , Enter “USEREXIT” in Find field & select main program
radio button  Click Yes
2. Verify the User Exit
a. Place the break-point on FORM
b. Create order in VA01 T code & Click SAVE. Waiting for break point to trigger
c. Verified the FORM EXIT
3. Implementation
a. Place custom / own code between FORM….ENDFORM

FORM USEREXIT_XXX_YYY

****** Custom Code *************

ENDFORM

2. Customer Exit:
 Available in all SAP modules
 Customer Exit are Function Modules with a custom empty include program, you can add
your own functionality in these include programs.
 Also called as FUNCTION EXIT
 Starts with CALL CUSTOMER word
Real-Time projects:
 Country & Destination validation for customer creation ( XD01 / XD02 )

Steps to find and implement Customer Exit:

1. Find the Function Exit


a. SE93  Enter the transaction code ( Eg: XD01 ) Display
b. Double click on program name
c. Click on Find Icon , Enter “CALL CUSTOMER” in Find field & select main
program radio button  Click Yes
d. List of function module will be shown and choose one function module
2. Verify the Customer Exit
a. Place the break-point on Function module
b. Take any one customer code and enter in XD01 T code & Click Enter.
Waiting for break point to trigger
c. Verify the function module
3. Find the Enhancement name
a. Double click on Function module  get the function module name
b. SE16 MODSAP  Enter the function module name  get the
Enhancement name
c. If any project available. SE16  MODACT  Enter the Enhancement name
 get the Project name
4. Create project & Implement - Customer Exit
a. CMOD  Provide Project name and click create button
b. Click on Enhancement assignment button  add enhancement name &
click Enter
c. Click on Components button you will find the function module name 
double click FM will find Include program  we can add custom/own
code in the Include program, SAVE & ACTIVATE

Difference:

User Exit Customer Exit


User Exit implemented in the form of Customer Exit implemented as Function Exit, Screen
Subroutine Exit, Menu Exit, Field Exit
Syntax: PERFORM USEREXIT_XXX_YYY Syntax: CALL Customer function “XXX’.
INCLUDE XXXX.
User exit is considered a modification and not Customer Exit is considered an enhancement because
an enhancement because we are changing the we are adding additional functionality to the existing
existing code. one, not changing any thing
User Exit will be activated automatically To activate a function exit, you need to create a
whenever you activate the application project in CMOD and activate the project.
(program).
Implicit Enhancement:

Steps:

1. SE37  Function module name


2. Select Enhance source code button
3. Edit  Enhancement Operations  Show Implicit Enhancement Options
4. Edit Enhancement Operations Create Enhancement  Enter the Enhancement name
5. Place custom code in the section

ENHANCEMENT 1 ZXXXX_YYYY.

*****Custom Code********

ENDENHANCEMENT.

6. Save & activate the function module and will find the implicit enhancements.

Explicit Enhancement:

Types:

1. Customer Exit
2. User Exit
3. BADI

User Exit:

 Implemented in the form of subroutines


 Known as FORM EXITs.
 Generally collected in includes and attached to the standard program by the SAP.
 Originally developed for the R/3 SD (Sales and distribution) module
 User exits start with the word USEREXIT_XXX

Syntax:

FORM USEREXIT_XXX….

INCLUDE ZZUSEREXIT…

ENDFORM.

Ways to find User Exit:

Steps:

1. T.code --- SE80


2. Select Package --VMOD

You might also like