SAP MAP2E_KBEDB_TO_BAPI_KBED2 Function Module for NOTRANSL: kbedb -> bapi_kbed
MAP2E_KBEDB_TO_BAPI_KBED2 is a standard map2e kbedb to bapi kbed2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: kbedb -> bapi_kbed 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 map2e kbedb to bapi kbed2 FM, simply by entering the name MAP2E_KBEDB_TO_BAPI_KBED2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRMO
Program Name: SAPLCRMO
Main Program: SAPLCRMO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP2E_KBEDB_TO_BAPI_KBED2 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 'MAP2E_KBEDB_TO_BAPI_KBED2'"NOTRANSL: kbedb -> bapi_kbed.
EXPORTING
KBEDB = "Order: KBED Structure for Document Table
CHANGING
BAPI_KBED = "Capacity records
IMPORTING Parameters details for MAP2E_KBEDB_TO_BAPI_KBED2
KBEDB - Order: KBED Structure for Document Table
Data type: KBEDBOptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP2E_KBEDB_TO_BAPI_KBED2
BAPI_KBED - Capacity records
Data type: BAPI_KBEDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAP2E_KBEDB_TO_BAPI_KBED2 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_kbedb | TYPE KBEDB, " | |||
| lv_bapi_kbed | TYPE BAPI_KBED. " |
|   CALL FUNCTION 'MAP2E_KBEDB_TO_BAPI_KBED2' "NOTRANSL: kbedb -> bapi_kbed |
| EXPORTING | ||
| KBEDB | = lv_kbedb | |
| CHANGING | ||
| BAPI_KBED | = lv_bapi_kbed | |
| . " MAP2E_KBEDB_TO_BAPI_KBED2 | ||
ABAP code using 7.40 inline data declarations to call FM MAP2E_KBEDB_TO_BAPI_KBED2
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.Search for further information about these or an SAP related objects