SAP META_BAPI_DISPATCH Function Module for Meta BAPI Dispatch
META_BAPI_DISPATCH is a standard meta bapi dispatch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Meta BAPI Dispatch processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for meta bapi dispatch FM, simply by entering the name META_BAPI_DISPATCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_BD_DISPATCHER
Program Name: SAPLBBP_BD_DISPATCHER
Main Program: SAPLBBP_BD_DISPATCHER
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function META_BAPI_DISPATCH pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'META_BAPI_DISPATCH'"Meta BAPI Dispatch.
EXPORTING
OBJECT = "Object key
METHOD = "Object method
* LOGICAL_SYSTEM = "
* SYSTEM_TYPE = "Systemart
IMPORTING
FUNCTIONNAME = "
TABLES
CONTROL_RECORD = "Control record
EXCEPTIONS
OBJECT_NOT_FOUND = 1 BAD_SYS_TYPE = 2
IMPORTING Parameters details for META_BAPI_DISPATCH
OBJECT - Object key
Data type: BDI_BAPI-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
METHOD - Object method
Data type: BDI_BAPI-METHODOptional: No
Call by Reference: No ( called with pass by value option)
LOGICAL_SYSTEM -
Data type: BBP_BACKEND_DEST-LOG_SYSOptional: Yes
Call by Reference: No ( called with pass by value option)
SYSTEM_TYPE - Systemart
Data type: BBP_SYSTEM_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for META_BAPI_DISPATCH
FUNCTIONNAME -
Data type: TFDIR-FUNCNAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for META_BAPI_DISPATCH
CONTROL_RECORD - Control record
Data type: BBP_CONTROL_RECORDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BAD_SYS_TYPE - Different given and derived system type
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for META_BAPI_DISPATCH Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_object | TYPE BDI_BAPI-OBJECT, " | |||
| lv_functionname | TYPE TFDIR-FUNCNAME, " | |||
| lt_control_record | TYPE STANDARD TABLE OF BBP_CONTROL_RECORD, " | |||
| lv_object_not_found | TYPE BBP_CONTROL_RECORD, " | |||
| lv_method | TYPE BDI_BAPI-METHOD, " | |||
| lv_bad_sys_type | TYPE BDI_BAPI, " | |||
| lv_logical_system | TYPE BBP_BACKEND_DEST-LOG_SYS, " | |||
| lv_system_type | TYPE BBP_SYSTEM_TYPE. " |
|   CALL FUNCTION 'META_BAPI_DISPATCH' "Meta BAPI Dispatch |
| EXPORTING | ||
| OBJECT | = lv_object | |
| METHOD | = lv_method | |
| LOGICAL_SYSTEM | = lv_logical_system | |
| SYSTEM_TYPE | = lv_system_type | |
| IMPORTING | ||
| FUNCTIONNAME | = lv_functionname | |
| TABLES | ||
| CONTROL_RECORD | = lt_control_record | |
| EXCEPTIONS | ||
| OBJECT_NOT_FOUND = 1 | ||
| BAD_SYS_TYPE = 2 | ||
| . " META_BAPI_DISPATCH | ||
ABAP code using 7.40 inline data declarations to call FM META_BAPI_DISPATCH
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single OBJECT FROM BDI_BAPI INTO @DATA(ld_object). | ||||
| "SELECT single FUNCNAME FROM TFDIR INTO @DATA(ld_functionname). | ||||
| "SELECT single METHOD FROM BDI_BAPI INTO @DATA(ld_method). | ||||
| "SELECT single LOG_SYS FROM BBP_BACKEND_DEST INTO @DATA(ld_logical_system). | ||||
Search for further information about these or an SAP related objects