Get Example source ABAP code based on a different SAP table
VERSION 5 OUT
ABAP_AMDP - BAdIs In addition to the option of implementing BAdI methods of a regular BAdI as AMDP procedure implementations and making these methods callable by using CALL BADI, it is also possible to create special AMDP BAdIs. An AMDP BAdI is a BAdI that is labeled accordingly in BAdI Builder and has the following properties:
Definition and implementation
An AMDP BAdI does not have any filters.
Fallback BAdI implementation classes must be specified.
Every BAdI method of an AMDP BAdI must be an AMDP procedure implementation.
Every AMDP method must be implemented for the same database system.
Call BAdI methods
The AMDP procedure implementations of an AMDP BAdI can be called like regular BAdI methods with GET BADI and CALL BADI.
The AMDP procedures of an AMDP BAdI created on the database can be called, like all AMDP procedures, from other AMDP methods in the same database system. These AMDP procedures are specified using the name of a BAdI implementation class. The usage must be declared after the addition USING of the calling method. In both cases, execution takes place in accordance with the rules of the ABAP Enhancement Framework and the corresponding switch in Switch Framework. If no enhancement is available, the mandatory fallback implementation class is implemented.
Latest notes:
AMDP BAdIs are primarily used to execute calls of AMDP procedures from AMDP procedures or functions, in accordance with the rules of the switch-based ABAP Enhancement Framework. Switch-based calls of AMDP procedure implementations are possible from ABAP programs without AMDP BAdIs. However, switch-based calls of AMDP procedure implementations from AMDP procedures or functions are only possible using AMDP BAdIs. The AMDP framework ensures that the relevant database procedure for the current database switch setting is created on the database.
Before the AMDP procedure of an AMDP BAdI can be called from other AMDP procedures or functions without syntax errors, it must already exist on the database when the calling method is created. For this reason, fallback BAdI implementation classes are mandatory for AMDP BAdIs, whose AMDP procedures can be created on the database whenever required.
AMDP BADIs do not currently support AMDP function implementations. ABAP_HINT_END
