What does it do? Calls a BAdI method>. The statement has a static and a dynamic variant. In both variants, a BAdI reference variable> must be specified for badi>.
In the static variant, a BAdI reference variable> of the static type of a concrete BAdI class> must be specified for badi >, and for meth> a BAdI method of the corresponding BAdI> must be specified directly. BEGIN_SECTION ID CALL-BADI-DYN
In the dynamic variant, a BAdI reference variable> of the static type of the abstract superclass CL_BADI_BASE> must be specified for badi>. For meth_name >, a character-like data object must be specified that must contain the name of a BAdI method in uppercase letters when the statement is executed. END_SECTION ID CALL-BADI-DYN With respect to the addressing of BAdI methods, the BAdI reference variable behaves statically as well as dynamically like an interface reference variable> with the static type of the affected BAdI interface>. A BAdI method that is declared as a component of the corresponding BAdI interface is addressed directly using its name. BAdI methods declared in component interfaces> of the BAdI interface can be addressed using the interface component selector> or any alias names>. The additions parameter_list> > or parameter_tables>> assign actual parameters to the formal parameters of the BAdI method or handle non-class-based exceptions exactly as described in the method call>. The exceptions that can occur in dynamic accesses are also the same as those of CALL METHOD>>. The statement CALL BADI> calls the specified method in all object plug-ins> to which the BAdI object> referenced by the badi> refers.