Since SAP NetWeaver 7.0, the Business Add-Ins (BADIs) are used for enhancements in SAP, as they provide modern enhancement technology.
Features of BADIs
- The new and currently used BADIs are incorporated in enhancement framework with enhancement sections and points.
- BADIs give better improved performance and functions like filter and the option to inherit properties from a class.
The BADIs are managed by enhancement spots, unlike classic BADIs. In a classic BADI, both BADI definition and interface are built using transaction code SE18, which generates BADI adapter class.
Call Syntax of Classic BADI Program Exit
In any SAP program, a reference variable is defined using BADI interface type. When the class CL_EXITHANDLER is called, BADI instance is built. Thus, the bridging method is called via BADI instance for implementation.
Steps to search for a Classic BADI Program Exit
- Use SE84 to do BADI free search.
- Use code SE81 followed by SE84, to list out BADIs for a particular application.
- For a program search, look for GET_INSTANCE globally and to go to BADI interface, click the reference variable returned from GET_INSTANCE method.
- Put up a where used search to find out where the interface is used in classes and finally, read BADI implementation using SE18.
#Insight
As an alternate option, you can set a breakpoint for the method GET_INSTANCE in the debugger and then search for uses of reference variables in the program.
Steps to implement Class BADI Program Exit
- Use SE18 to show BADI definition. Then, select CREATE IMPLEMENTATION where you’ll find SE19.
- Select and write a name for BADI implementation.
- For implementation, click on method names of interface tab.
- Finally, activate all the methods, implementation class and BADI implementation.
#Personal Recommendation
One of our personal favorites, the COMPLETE SAP ABAP is the best fit when it comes to learning and concept building, understanding of codes and error correction.
You must be logged in to post a comment.