SAP ME_MAINTAIN_PO_DATA_BUFFER Function Module for Buffering of PO Data for Price Determination









ME_MAINTAIN_PO_DATA_BUFFER is a standard me maintain po data buffer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Buffering of PO Data for Price Determination 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 maintain po data buffer FM, simply by entering the name ME_MAINTAIN_PO_DATA_BUFFER into the relevant SAP transaction such as SE37 or SE38.

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



Function ME_MAINTAIN_PO_DATA_BUFFER 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_MAINTAIN_PO_DATA_BUFFER'"Buffering of PO Data for Price Determination
  EXPORTING
*  IS_EKKO =  "Purchasing Document Header
*  IT_EKPA =  "Partner Data
*  IS_EKPO =  "Purchasing Document Item
*  IF_OUTPUT =  "
*  IT_VALUES_I =  "
*  IF_CAL_SUCC =  "
*  IT_VALUES_E =  "
*  IF_REFRESH =  "Refresh
*  IF_ID =  "Log ID

 IMPORTING
   ES_HEADER =  "Purchasing Document Header
   ET_PARTNER =  "Partner Data
   ET_ITEMS =  "Purchasing Document Item
   ET_VALUES_I =  "
   EF_CAL_SUCC =  "
   ET_VALUES_E =  "
   EF_CHANGED =  "Data Has Changed
   EF_ID =  "Log ID
.




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_SAPLMEKO_001 Extend Communication Structure KOMK for Pricing
EXIT_SAPLMEKO_002 Extend Communication Structure KOMP for Pricing

IMPORTING Parameters details for ME_MAINTAIN_PO_DATA_BUFFER

IS_EKKO - Purchasing Document Header

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

IT_EKPA - Partner Data

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

IS_EKPO - Purchasing Document Item

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

IF_OUTPUT -

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

IT_VALUES_I -

Data type: /SAPSLL/API6800_DUC_VAL_R3_T
Optional: Yes
Call by Reference: Yes

IF_CAL_SUCC -

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

IT_VALUES_E -

Data type: /SAPSLL/API6800_DUC_VAL_R3_T
Optional: Yes
Call by Reference: Yes

IF_REFRESH - Refresh

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

IF_ID - Log ID

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

EXPORTING Parameters details for ME_MAINTAIN_PO_DATA_BUFFER

ES_HEADER - Purchasing Document Header

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

ET_PARTNER - Partner Data

Data type: /SAPSLL/MMPA_R3_T
Optional: No
Call by Reference: Yes

ET_ITEMS - Purchasing Document Item

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

ET_VALUES_I -

Data type: /SAPSLL/API6800_DUC_VAL_R3_T
Optional: No
Call by Reference: Yes

EF_CAL_SUCC -

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

ET_VALUES_E -

Data type: /SAPSLL/API6800_DUC_VAL_R3_T
Optional: No
Call by Reference: Yes

EF_CHANGED - Data Has Changed

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

EF_ID - Log ID

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

Copy and paste ABAP code example for ME_MAINTAIN_PO_DATA_BUFFER 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_is_ekko  TYPE EKKO, "   
lv_es_header  TYPE EKKO, "   
lv_it_ekpa  TYPE MMPUR_T_EKPA, "   
lv_et_partner  TYPE /SAPSLL/MMPA_R3_T, "   
lv_is_ekpo  TYPE EKPO, "   
lv_et_items  TYPE MMPUR_BEKPO, "   
lv_if_output  TYPE BOOLEAN, "   
lv_et_values_i  TYPE /SAPSLL/API6800_DUC_VAL_R3_T, "   
lv_ef_cal_succ  TYPE BOOLEAN, "   
lv_it_values_i  TYPE /SAPSLL/API6800_DUC_VAL_R3_T, "   
lv_et_values_e  TYPE /SAPSLL/API6800_DUC_VAL_R3_T, "   
lv_if_cal_succ  TYPE BOOLEAN, "   
lv_ef_changed  TYPE BOOLEAN, "   
lv_it_values_e  TYPE /SAPSLL/API6800_DUC_VAL_R3_T, "   
lv_ef_id  TYPE INT4, "   
lv_if_refresh  TYPE BOOLEAN, "   
lv_if_id  TYPE INT4. "   

  CALL FUNCTION 'ME_MAINTAIN_PO_DATA_BUFFER'  "Buffering of PO Data for Price Determination
    EXPORTING
         IS_EKKO = lv_is_ekko
         IT_EKPA = lv_it_ekpa
         IS_EKPO = lv_is_ekpo
         IF_OUTPUT = lv_if_output
         IT_VALUES_I = lv_it_values_i
         IF_CAL_SUCC = lv_if_cal_succ
         IT_VALUES_E = lv_it_values_e
         IF_REFRESH = lv_if_refresh
         IF_ID = lv_if_id
    IMPORTING
         ES_HEADER = lv_es_header
         ET_PARTNER = lv_et_partner
         ET_ITEMS = lv_et_items
         ET_VALUES_I = lv_et_values_i
         EF_CAL_SUCC = lv_ef_cal_succ
         ET_VALUES_E = lv_et_values_e
         EF_CHANGED = lv_ef_changed
         EF_ID = lv_ef_id
. " ME_MAINTAIN_PO_DATA_BUFFER




ABAP code using 7.40 inline data declarations to call FM ME_MAINTAIN_PO_DATA_BUFFER

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



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!