Reason SAP introduced the new BAdi technology are as follows:

• New BAdi technology results in improved performance.
• New BAdi technology provides some additional functions, as follows
• Enhanced filter concept
• Option to inherit attributes from sample implementation classes
• New BAdis are integrated into the new Enhancement framework along with enhancement points and enhancement sections.

Overview of BAdis in the Enhancement Framework

Unlike classic BAdis, new BAdis always belong to, and are managed by, enhancement spots. Although SAP will create new BAdis going forward, there are still many enhancements provided by classic BAdis, and therefore they are still very important.

Classic BAdis

A BAdi definition and an interface are created using SE18. The creation of the BAdi and interface results in the automatic generation BAdi adapter class and a corresponding bridging method, which the SAP application call to branch to the relevant code. The only task of this bridging method is to call the existing active implementations of industry solutions, partners, and customers, one after the other. The sequence in which they will be called cannot be guaranteed.

Classic BAdi Program exit – Call syntax in the SAP program

This figure shows the syntax that is used to prepare and call the bridging method in the SAP program. In the SAP program, a reference variable is defined using the type of the BAdi interface, which has already been defined.

When the GET_INSTANCE static method of the standard class CL_EXITHANDLER is called, an instance of the adapter class is created. The bridging method is then called through the BAdi instance, and it branches to the relevant implementations.

To search for a classic BAdi Program Exit

• To perform a free search for BAdIs, use transaction SE84
• To list BADIs for a specific application, use transaction SE81, followed by transaction SE84
• To perform a program-related search:
1. Search for GET_INSTANCE globally in the program.
2. To navigate to the BADI interface, double click on the reference variable returned by the GET_INSTANCE method, and then double click on the interface which is used to type this reference variable
3. Perform a where-used search to determine where the interface is used in classes named CL_EX_<BADI_name>
4. Read the BADI documentation in SE18

Alternatively, you can set a breakpoint for method GET_INSTANCE and get the BADI name

Steps to implement a classic BADI Program Exit:

1. Display the BADI definition in SE18
2. Choose implementation -> Create, which takes you to transaction SE19
3. Specify the name for the BADI implementation
4. Double click the method names on the interface tab page to implement them
5. Activate the methods and implementation class
6. Activate the BADI implementation