There are several ways how to find out the correct user exit. In the following article I’ll show few options how to achieve this kind of task
If you know the exit by name
- Run transaction SE80 and go to the “Repository Information system”
- Navigate to Enhancements – Customer Exits – Enhancements
Using FM SXV_GET_CLIF_BY_NAME
- Go to transaction code SE37, enter the following function module name
“SXV_GET_CLIF_BY_NAME” and press Display
- Put a break-point on the first executable line
- Run transaction code (i.e. MIRO) and wait until program stops at the break point that is set in step 2.
- Double click on the name variable – it will display the first BADI used (i.e. in MIRO – MRM_TRANSACT_DEFAULT – BADI name)
Use SE18 to see the BADI attributes.
- Press F8 to get more BADI’s used by MIRO in sequence they are called.
Using Class method CL_EXITHANDLER~GET_INSTANCE
Breakpoing on ABAP call during debugging
- Set debugging on by sending “/h” in the command input box
- Start program (i.e. MIRO) where you want to search for a customer user exit
- When ABAP debugger is started go to top menu -> Breakpoints ->Breakpoint at -> Statement
- Enter command “CALL CUSTOMER-FUNCTION” and confirm
- Press F8 to continue the program – when CALL CUSTOMER-FUNCTION construct is reached in the code, the ABAP debugger is started and you can read the name of user exit.
Find all available user exits for a TCode
If you know the Transaction Code which you’d like to enhance by implementing user exit code, you can find all available user exits for a specific TCode if you follow my instructions in another post: Program to discover all user exits for given TCode