How to search for BAdIs? (Trace it)

Introduction

There are multiple ways of searching for BAdIs. My favorite one is using the Performance Trace (formerly known as SQL trace) transaction code ST05.

This analyzing technique is based on the fact that all BAdIs are registrated in SAP database tables. So for each BAdI call these database tables will be accessed. The BAdI database tables are SXS_INTER, SXC_EXIT, SXC_CLASS and SXC_ATTR. These tables are always accessed by the views V_EXT_IMP and V_EXT_ACT. So these two ABAP views (T: SE11) will be the basis for the trace.

This blog will not describe how to implement BAdIs. See https://help.sap.com/ for more information on implementing a BAdI.

The procedure to discover BAdIs by a Performance Trace will be explained by using the example used below.

Example case

I want to know which BAdIs are called in the transaction “Maintain Business Partners” transaction code BP.

Pre checks

• Check if no other users (T:SM04) or batch jobs (T: SM50) are using the same user as you do.

Trace Actions

Start the Performance trace

• Start transaction ST05 (Performance Analysis)
• Set flag field “Buffer trace”

Remark: We need to trace also the buffer calls, because BAdI database tables are buffered. (especially view V_EXT_IMP and V_EXT_ACT)

• Push button “Activate Trace”

Execute the Business transaction

• Start transaction BP in a new GUI session
• Push button “Organization”
• Fill in your test data

• Push button Save

Performance trace

• Go back to the Performance trace session
• Push button “Deactivate Trace”

Analyzing the Trace List

Showing the Trace List

• Push button “Display Trace”

The popup screen “Set Restrictions for Displaying Trace” appears

Now we are going to filter the trace on Objects: V_EXT_IMP and V_EXT_ACT.

• Push button “Multiple selections” button behind field Objects
• Fill: V_EXT_IMP and V_EXT_ACT

• Push button “Copy (F8)”
• Fill Operations: OPEN
• Push button Enter
  See the result:

Interpreting the Trace list

All the interface class names of view V_EXT_IMP start with IF_EX_. This is the standard SAP prefix for BAdI class interfaces. The BAdI name is after the IF_EX_.

So the BAdI name of IF_EX_ADDR_LANGU_TO_VERS is ADDR_LANGU_TO_VERS.

In transaction SE18 you can see the BAdI definition.

(If you can’t find the BAdI definition name, search in table SXS_INTER.)

Exporting the Trace list

If you’d like to keep your analysis, you can export it to Excel file format.

Actually the file will be saved in tab separated file format, but giving the file the extension .xls it will automatically be opened by Excel.

• Start menu: List > Save > Local File
• Select Spreadsheet
• Push Enter
• Fill your preferred file location and file name

• Push button “Generate”
• Open the file (in Excel)

• Delete the columns and rows you don’t need and the result looks like:

View V_EXT_IMP and V_EXT_ACT

The reason for filtering the result not only on the view V_EXT_IMP but also on V_EXT_ACT is necessary, because not all BAdIs are implemented in the same way.

For example:

V_EXT_IMP catches BAdI BPTIME_BP001.

V_EXT_ACT catches BAdI ADDRESS_SEARCH

Tips

• Make a full test entry in the Business transaction before starting the Performance analysis.
  So during the Performance trace you won’t make mistakes. Making mistakes during the recording will cause extra trace lines in your trace list.
• Try to start with an empty Business transaction screen.
  This tip is best explained by an example.
  When I restart transaction BP after I have created, displayed or changed a business partner, the last opened business partner will be displayed automatically. This means also I will get extra trace lines in my trace list.
  To start again with an empty business partner screen you have to close all GUI sessions and login again.
• In the Business transaction you need to fill all required fields so all BAdIs will be called.

Appendix BP analysis

Keywords: BAdI BAdIs BAdI’s Businesses Add In Business Add-In Business Add-Ins how to find BAdI’s