BAdI – Business Add In’s
Overview on use
BAdIs are contained in the system and are fully operational as of Release 4.6B.
They are activated as soon as an active implementation exists in the system. These implementations are imported into the system by transport requests, which a third party usually delivers. An implementation can be in an active or an inactive form in the transport request – usually, however, they are transported actively.
Transaction – SE18 – Use this to define the BAdI.
These contain the business add-in interface. In the application code the instance variable is typed according to this interface. You can create several implementations for each add-in definition.
There are two main types of BADI definitions:
- Multiple use – that is, there can be several active implementations
- Filter-dependent – that is, you apply a filter value to each method called (for example, a country). A different (active) implementation is then called for each value. Possible filter values are characterized by the filter type.
Transaction - SE19 – Use this to activate/deactivate the BAdI Implementation.
Here you create the BADi implementations. They are created with reference to a business add-in definition. You can create several implementations for each business add-in definition.