SAP ME_PREPARE_COMMITMENT_WA Function Module for NOTRANSL: ME_PREPARE_COMMITMENT_WA









ME_PREPARE_COMMITMENT_WA is a standard me prepare commitment wa 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: ME_PREPARE_COMMITMENT_WA 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 me prepare commitment wa FM, simply by entering the name ME_PREPARE_COMMITMENT_WA into the relevant SAP transaction such as SE37 or SE38.

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



Function ME_PREPARE_COMMITMENT_WA 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 'ME_PREPARE_COMMITMENT_WA'"NOTRANSL: ME_PREPARE_COMMITMENT_WA
EXPORTING
I_EKKO = "Purchasing Document Header
* I_LFA1 = ' ' "

TABLES
T_EKBE = "
* T_EKBZ_MA = "Delivery Costs at Account Assignment Level
* T_KNT = "
T_EKBES = "
T_EKBNK = "
T_EKBZ = "
T_EKKN = "
T_EKPO = "
T_KOMV = "
* T_EKPV = "
* T_EKBE_MA = "History of Purchasing Document at Account Assignment Level
.




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_SAPLEINS_001 User Exit to Populate Communication Structure, Purchasing Info. System

IMPORTING Parameters details for ME_PREPARE_COMMITMENT_WA

I_EKKO - Purchasing Document Header

Data type: EKKO
Optional: No
Call by Reference: No ( called with pass by value option)

I_LFA1 -

Data type: LFA1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ME_PREPARE_COMMITMENT_WA

T_EKBE -

Data type: EKBE
Optional: No
Call by Reference: No ( called with pass by value option)

T_EKBZ_MA - Delivery Costs at Account Assignment Level

Data type: EKBZ_MA
Optional: Yes
Call by Reference: Yes

T_KNT -

Data type: EKKNU
Optional: Yes
Call by Reference: Yes

T_EKBES -

Data type: EKBES
Optional: No
Call by Reference: No ( called with pass by value option)

T_EKBNK -

Data type: EKBNK
Optional: No
Call by Reference: No ( called with pass by value option)

T_EKBZ -

Data type: EKBZ
Optional: No
Call by Reference: No ( called with pass by value option)

T_EKKN -

Data type: EKKN
Optional: No
Call by Reference: No ( called with pass by value option)

T_EKPO -

Data type: BEKPO
Optional: No
Call by Reference: No ( called with pass by value option)

T_KOMV -

Data type: KOMV
Optional: No
Call by Reference: No ( called with pass by value option)

T_EKPV -

Data type: CEKPV
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_EKBE_MA - History of Purchasing Document at Account Assignment Level

Data type: EKBE_MA_S
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for ME_PREPARE_COMMITMENT_WA 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_i_ekko  TYPE EKKO, "   
lt_t_ekbe  TYPE STANDARD TABLE OF EKBE, "   
lt_t_ekbz_ma  TYPE STANDARD TABLE OF EKBZ_MA, "   
lt_t_knt  TYPE STANDARD TABLE OF EKKNU, "   
lv_i_lfa1  TYPE LFA1, "   SPACE
lt_t_ekbes  TYPE STANDARD TABLE OF EKBES, "   
lt_t_ekbnk  TYPE STANDARD TABLE OF EKBNK, "   
lt_t_ekbz  TYPE STANDARD TABLE OF EKBZ, "   
lt_t_ekkn  TYPE STANDARD TABLE OF EKKN, "   
lt_t_ekpo  TYPE STANDARD TABLE OF BEKPO, "   
lt_t_komv  TYPE STANDARD TABLE OF KOMV, "   
lt_t_ekpv  TYPE STANDARD TABLE OF CEKPV, "   
lt_t_ekbe_ma  TYPE STANDARD TABLE OF EKBE_MA_S. "   

  CALL FUNCTION 'ME_PREPARE_COMMITMENT_WA'  "NOTRANSL: ME_PREPARE_COMMITMENT_WA
    EXPORTING
         I_EKKO = lv_i_ekko
         I_LFA1 = lv_i_lfa1
    TABLES
         T_EKBE = lt_t_ekbe
         T_EKBZ_MA = lt_t_ekbz_ma
         T_KNT = lt_t_knt
         T_EKBES = lt_t_ekbes
         T_EKBNK = lt_t_ekbnk
         T_EKBZ = lt_t_ekbz
         T_EKKN = lt_t_ekkn
         T_EKPO = lt_t_ekpo
         T_KOMV = lt_t_komv
         T_EKPV = lt_t_ekpv
         T_EKBE_MA = lt_t_ekbe_ma
. " ME_PREPARE_COMMITMENT_WA




ABAP code using 7.40 inline data declarations to call FM ME_PREPARE_COMMITMENT_WA

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.

 
 
 
 
DATA(ld_i_lfa1) = ' '.
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!