Identifying standard Business Add-Ins (BADIs) is an essential step for SAP developers when enhancing standard SAP functionality without modifying the core code. Below are the steps to find and identify standard BADIs in SAP systems:

1. Use Transaction Code SE24 (Class Builder)

Purpose:
Many BADIs are implemented as classes that extend the SAP application. You can use the Class Builder (SE24) to search for BADI-related classes.

Steps:

• Go to transaction SE24.
• Enter CL_EXITHANDLER as the class.
• Click on Display.
• Choose the Methods tab and look for the method GET_INSTANCE.
• Set a breakpoint on this method.
• Now run the transaction for which you want to find a BADI. When the breakpoint is triggered, you can check the BADI name in the debugger (by inspecting the method parameters and variables).

Usage:
This method helps you find BADIs that are invoked when the transaction or process is executed. By debugging, you can see the BADI that is triggered in real-time.

2. Use Transaction Code SE18 (BADI Definition)

Purpose:
Transaction SE18 allows you to directly search for a BADI definition or explore the existing BADIs in the SAP system.

Steps:

• Go to transaction SE18.
• In the Definition Name field, leave it blank or enter a partial name if known.
• Click on the F4 (Search Help) button to browse all available BADIs.
• You can filter based on keywords or business processes.
• Select the BADI definition from the list to view more details about its methods and interfaces.

Usage:
Use this method when you know part of the BADI definition name or want to explore the list of BADIs related to specific business functionality.

3. Use Transaction Code SE84 (Repository Information System)

Purpose:
Transaction SE84 provides a structured view of all the objects in SAP, including BADIs. It’s useful for exploring available enhancements systematically.

Steps:

• Go to transaction SE84 (or SE80, depending on the system).
• Expand the Enhancements tree on the left pane.
• Click on Business Add-Ins.
• Select Definitions to view a list of all BADI definitions in the system.
• You can also search by specific areas (like MM, SD, FI) by entering relevant search criteria.
• Select a BADI from the list to view its definition and associated implementations.

Usage:
SE84 is ideal for exploring all enhancements in a structured way, filtering through functional modules or business areas.

4. Use Transaction Code SE93 (Transaction Code Search)

Purpose:
Often, you can find a BADI by analyzing the transaction code for which you want to make enhancements.

Steps:

• Go to transaction SE93.
• Enter the transaction code you are working with (e.g., VA01 for sales order creation).
• Click Display.
• You will see the program associated with the transaction.
• Note the program name.
• Use SE80 or SE38 to open the program and check for enhancement points or calls to BADIs using keywords like CALL BADI.

Usage:
This method is useful when you want to find the BADI associated with a specific transaction or program.

5. Use Transaction Code SU24 (Authorization Check)

Purpose:
In some cases, BADIs are linked with authorization objects or checks. You can find BADIs related to authorization processes using SU24.

Steps:

• Go to transaction SU24.
• Enter the transaction code for which you want to find the associated BADIs.
• Click on Execute.
• In the results, look for authorization objects related to BADIs.
• Note the authorization objects or programs that trigger a BADI during execution.

Usage:
This method is helpful if you’re working on user roles, security, or authorization checks where BADIs are linked.

6. Debugging Technique Using Transaction Code SE37 (Function Module)

Purpose:
You can use function modules related to exit and BADI handlers to identify active BADIs during a transaction.

Steps:

• Go to transaction SE37.
• Enter the function module SXV_GET_CLIF_BY_NAME.
• Set a breakpoint in this function module.
• Now execute the transaction for which you want to find a BADI.
• When the breakpoint is triggered, check the BADI name in the debugger (inspect variables and table contents).

Usage:
This technique allows real-time monitoring of which BADIs are triggered during specific processes, making it ideal for complex transactions.

7. Check SAP Standard Documentation

Purpose:
SAP provides extensive documentation that lists standard BADIs for specific modules or applications. Checking the SAP help documentation or SAP Notes can give you direct insight into the standard BADIs available for your scenario.

Steps:

• Go to the SAP Help Portal or SAP Notes.
• Search for standard BADIs relevant to your business process (e.g., “MM BADIs” or “SD BADIs”).
• Review the documentation for details on the available BADIs, their usage, and their methods.

Usage:
This is useful when you want a documented approach to identifying standard BADIs within specific SAP modules or industry solutions.

8. Use Transaction Code SE11 (Data Dictionary)

Purpose:
Sometimes, BADIs are linked to specific database tables or structures. You can use SE11 to find BADIs related to data processing.

Steps:

• Go to transaction SE11.
• Enter the table or structure name you are working with.
• Check for enhancement options linked to the table.
• In many cases, you will find BADIs related to table processing, updates, or validations.

Usage:
This method is helpful when you are looking for BADIs that are triggered based on table events (e.g., insert, update, or delete operations).

Conclusion

By following these steps, you can effectively identify standard BADIs in SAP systems to enhance and extend SAP’s functionality according to your business needs.