SAP MAP2E_KOMV_TO_BAPICOND Function Module for NOTRANSL: komv -> bapimepocond

Search SAP Function Modules

MAP2E_KOMV_TO_BAPICOND is a standard map2e komv to bapicond 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: komv -> bapimepocond 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 komv to bapicond FM, simply by entering the name MAP2E_KOMV_TO_BAPICOND into the relevant SAP transaction such as SE37 or SE38.

Function Group: 2012
Program Name: SAPL2012
Main Program: SAPL2012
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP2E_KOMV_TO_BAPICOND 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_KOMV_TO_BAPICOND'"NOTRANSL: komv -> bapimepocond
  EXPORTING
   KOMV =  "Pricing Communications-Condition Record

CHANGING
   BAPIMEPOCOND =  "Conditions in Purchase Order

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPL2012_001 Customer Exit for Creating an Enjoy Purchase Order Using BAPI_PO_CREATE1
EXIT_SAPL2012_002 Customer Exit for Changing an Enjoy Purchase Order Using BAPI_PO_CHANGE
EXIT_SAPL2012_003 Customer Exit for Creating an Enjoy Purchase Order Using BAPI_PO_CREATE1
EXIT_SAPL2012_004 Customer Exit for Changing an Enjoy Purchase Order Using BAPI_PO_CHANGE

IMPORTING Parameters details for MAP2E_KOMV_TO_BAPICOND

KOMV - Pricing Communications-Condition Record

Data type: KOMV
Optional: No
Call by Reference: Yes

CHANGING Parameters details for MAP2E_KOMV_TO_BAPICOND

BAPIMEPOCOND - Conditions in Purchase Order

Data type: BAPIMEPOCOND
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MAP2E_KOMV_TO_BAPICOND 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.

ABAP code using 7.40 inline data declarations to call FM MAP2E_KOMV_TO_BAPICOND

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