Short Reference


GET BADI badi [FILTERS f1 = x1 f2 = x2 ...]
              [CONTEXT con].


... CONTEXT con


: This statement generates a new BAdI object and sets the BAdI reference to the object in a BAdI reference variable badi. The static type of the reference variable badi must be a BAdI and determines which BAdI is used. In a context-free BAdI, the addition CONTEXT must not be specified, and in a context-dependent BAdI it must be specified.

After the addition FILTERS, elementary data objects x1, x2, ...must be specified for all filters f1, f2, etc. of the BAdI. If a filter in the BAdI has the property constant filter value at call, then you can specify only literals and constants. The data objects must be compatible with the data type of the filter. FILTERS cannot be specified for a BAdI without filters.

After instancing, the program searches for BAdI implementation classes for the BAdI as follows:

  1. Only BAdI implementation classes are selected that are assigned to a BAdI implementation that has the status active.

  2. Only BAdI implementation classes are selected that are assigned to a BAdI implementation (an enhancement) that have a switch in the status on. If no switch is assigned to a BAdI implementation, it is treated in the same way as an implementation with a switch in the status on.

  3. All BAdI implementations are selected that satisfy the above requirements and for which the filter condition of the BAdI implementation fits the values specified after FILTERS. If no BAdI implementations are found with the filter specifications, the system searches for BAdI implementations that are marked as standard implementations. If there are also none of these, the standard BAdI implementation class of the BAdI is used (if one exists).

  4. If for a BAdI defined for single use several BAdI implementation classes with matching filter conditions have been found, then a conflict solution is carried out. A successful conflict solution results in exactly one priority conflict-solving enhancement implementation and only its BAdI implementation class is selected. If several conflict-solving enhancement implementations have the same priority or if there are no conflict-solving enhancement implementations at all, then a correct conflict solution is not possible and several BAdI implementation classes will remain in the hit list.

If the resulting hit list is suitable for the definition of the BAdI which means:

then references to object plug-ins of the found BAdI implementations are saved in the BAdI object. Object plug-ins that do not yet exist are generated for this purpose. Whether an existing object plug-in is generated or reused, or whether a new object plug-in is generated, depends on whether the BAdI is context-free or context-dependent, and depends on the CONTEXT addition. The exact semantics is described in the addition.

If the hit list contains no or several BAdI implementations although the BAdI is defined for single use, an exception occurs. If the BAdI reference variable badi receives a valid BAdI reference before the statement in an exception case, this is retained, otherwise it is initialized.



... CONTEXT con


: With the addition CONTEXT, for context-dependent BAdIs, an object reference variable con must be specified, the static type of which is, or includes, the tag interface IF_BADI_CONTEXT, and which contains a reference to a BAdI context object. If con is initial, an exception occurs. The addition CONTEXT can not be entered for context-free BAdIs.

The addition CONTEXT controls the generation of the object plug-ins as follows:

If a BAdI implementation class implements multiple BAdI interfaces and GET BADI is executed within one internal session for several of these BAdIs, then multiple BAdI objects can point to the same object plug-in. This enables the sharing of data between different BAdIs. For context-free BAdIs, this is only the case for reuse. For context-dependent BAdIs, several BAdI objects from the same context can point to the same object plug-ins.



Catchable Exceptions