SAP MEPOBADI_PROCESS_KOMP Function Module for Processing of Item Data for Price Determination (KOMP)









MEPOBADI_PROCESS_KOMP is a standard mepobadi process komp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Processing of Item Data for Price Determination (KOMP) 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 mepobadi process komp FM, simply by entering the name MEPOBADI_PROCESS_KOMP into the relevant SAP transaction such as SE37 or SE38.

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



Function MEPOBADI_PROCESS_KOMP 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 'MEPOBADI_PROCESS_KOMP'"Processing of Item Data for Price Determination (KOMP)
  EXPORTING
*  IM_EKPO =  "Purchasing Document Item
*  IM_T001W =  "Plants/Subsidiaries
*  IM_EKKO =  "Purchasing Document Header
*  IM_KOMK =  "Communication Header for Pricing
*  IM_MT06E =  "Material Master Fields: Purchasing
*  IM_EINA =  "Purchasing Info Record: General Data
*  IM_EINE =  "Purchasing Info Record - Purchasing Organization Data

CHANGING
   CH_KOMP =  "Communication Item for Pricing
   CH_CUST_IMPL =  "

TABLES
*  T_KNT =  "Account Assignment
.



IMPORTING Parameters details for MEPOBADI_PROCESS_KOMP

IM_EKPO - Purchasing Document Item

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

IM_T001W - Plants/Subsidiaries

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

IM_EKKO - Purchasing Document Header

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

IM_KOMK - Communication Header for Pricing

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

IM_MT06E - Material Master Fields: Purchasing

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

IM_EINA - Purchasing Info Record: General Data

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

IM_EINE - Purchasing Info Record - Purchasing Organization Data

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

CHANGING Parameters details for MEPOBADI_PROCESS_KOMP

CH_KOMP - Communication Item for Pricing

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

CH_CUST_IMPL -

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

TABLES Parameters details for MEPOBADI_PROCESS_KOMP

T_KNT - Account Assignment

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

Copy and paste ABAP code example for MEPOBADI_PROCESS_KOMP 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:
lt_t_knt  TYPE STANDARD TABLE OF MMPUR_EKKNU, "   
lv_ch_komp  TYPE KOMP, "   
lv_im_ekpo  TYPE EKPO, "   
lv_im_t001w  TYPE T001W, "   
lv_ch_cust_impl  TYPE MMPUR_BOOL, "   
lv_im_ekko  TYPE EKKO, "   
lv_im_komk  TYPE KOMK, "   
lv_im_mt06e  TYPE MT06E, "   
lv_im_eina  TYPE EINA, "   
lv_im_eine  TYPE EINE. "   

  CALL FUNCTION 'MEPOBADI_PROCESS_KOMP'  "Processing of Item Data for Price Determination (KOMP)
    EXPORTING
         IM_EKPO = lv_im_ekpo
         IM_T001W = lv_im_t001w
         IM_EKKO = lv_im_ekko
         IM_KOMK = lv_im_komk
         IM_MT06E = lv_im_mt06e
         IM_EINA = lv_im_eina
         IM_EINE = lv_im_eine
    CHANGING
         CH_KOMP = lv_ch_komp
         CH_CUST_IMPL = lv_ch_cust_impl
    TABLES
         T_KNT = lt_t_knt
. " MEPOBADI_PROCESS_KOMP




ABAP code using 7.40 inline data declarations to call FM MEPOBADI_PROCESS_KOMP

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!