You are on page 1of 26

User Exits & BADI’s

Types of Exits:
• USER EXITS
• CUSTOMER EXITS
• Screen Exits
• Menu Exits
• Function Module Exits
• Field Exits
Function Module Exits:

- Format: CALL CUSTOMER-FUNCTION '910‘

- The naming standard of function modules for


function module exits is:

EXIT_<program name>_<3 digit suffix>


Function Module Exit:
Customer Exits will b looking like this in program
To implement the exit:
• Take the package name from the program name
• Go to SMOD and get the appropriate enhancement
• Go to CMOD and create a project and assign the enhancement to the
project.
• An enhancement can only be assigned to one project.
• Once assigned, Save and activate the project.
Getting the package:
SMOD:
Get the relevant enhancement from the hit list:

For e.g.: For the below function module: In the hit list search for the relevant descriptions
CMOD:
All must be green if the project is activated
• User Exits are called FORM exits where the piece of code will always
be inside the Form… Endform…

• E.g. - USEREXIT_SAVE_DOCUMENT_PREPARE
ZSD_USER_EXIT Table
Routines: (e.g.: VTFL (Copy criteria From delivery to Billing))
BADI’s
• We can find the BADI’s that are getting triggered with the help of
below function module.
Else put a break-point on ‘Get Instance’ Method of class ‘CL_EXITHANDLER’
ZBADI followed in our project for substitution

e.g.: ZF_SUB1_BADI_DEF
Use SE19 to implement the BADI
11:42 AM

You might also like