How to Find User Exits & BADIs in SAP – Complete Guide

User Exits are predefined enhancement points provided by SAP. They are included in standard programs through includes, allowing developers to add custom code.

BADIs are object-oriented enhancement options introduced by SAP to extend applications without changing the original source code.

Use Case:
In Plant 101, store users performing a 311 movement type (material transfer from store to production) want to automatically populate Plant and Material Number in the text field.

1. Go to Transaction Code SPRO
   • Open the SAP GUI and run transaction SPRO.
   • Click on SAP Reference IMG to open the configuration structure.
2. Navigate to the Relevant Configuration Node
   • Locate the module or process you’re customizing (e.g., Inventory Management).
   • This path depends on the business process (e.g., movement types, goods issue, etc.).
3. Click on the Documentation Button
   • Most configuration nodes have a “Documentation” button on the top bar.
   • Click it to open a new window containing related user exits for the selected process.
4. Review the List of Available User Exits
   • SAP provides a detailed list of User Exits tied to the selected process.
   • Read through the exit names and short descriptions to identify the most relevant one.
5. Use SMOD for Technical Details
   • Once you find the name of the enhancement, go to transaction SMOD and enter the exit name.
   • Press Display to see the exact include where you can write custom ABAP code.

Use Case:
Before creating a vendor in SAP using Transaction Code XK01, you want to verify if there’s any user exit where validation logic can be added.

• 2. Navigate to SE37 to Search for Function Module Exits
  
  • Open transaction SE37.
  • In the Function Module field, type:
  • Replace <ProgramName> with the one copied from SE93 (e.g., SAPMF02K becomes EXIT_SAPMF02K_*).

• 3. Use F4 Help to View All Function Module Exits
  • Press F4 to open the list of available function modules.
  • These are potential exits embedded in the program that you can implement using enhancement projects.

• 4. Check Each Exit in Detail
  
  • For each result, double-click to open it.
  • Review its Import/Export parameters and documentation to understand its purpose.

• 5. Implement Exit via CMOD
  
  • Use CMOD to create a project and assign the enhancement to activate and write custom logic.

Use Case:
You want to prevent users from saving an incoming invoice with zero value in Transaction Code MIRO. To do this, you must identify which BADI is triggered during the save action.

Overview of Debugging Keys:

• Enter transaction SE37 and input function module:

• Click Display to view the source code.

• Select the first executable line of code.
• Click the stop icon (breakpoint) in the toolbar to activate debugging.

• In a separate session, run MIRO.
• Enter the relevant invoice details as required.

• When you hit the SAVE button, the system will pause at the breakpoint you set earlier.
• Now you’re inside the debugger mode.

• Look for the variable NAME.
• Double-click on it to inspect its contents.
• Press F8 to loop through and view all BADIs that are triggered during the SAVE process.

• You might discover BADIs like MRM_TRANSACT_DEFAULT or INVOICE_UPDATE.
• Use transaction SE18 to check the BADI’s definition, methods, and available enhancement spots.

• Go to SE19 to implement the BADI and add your validation logic to stop users from saving invoices with zero value.