SAP ME_FILL_KOMK_IN Function Module for NOTRANSL: Füllen der KOMK für Infosätze

Search SAP Function Modules

ME_FILL_KOMK_IN is a standard me fill komk in 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: Füllen der KOMK für Infosätze 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 fill komk in FM, simply by entering the name ME_FILL_KOMK_IN into the relevant SAP transaction such as SE37 or SE38.

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

Function ME_FILL_KOMK_IN 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_FILL_KOMK_IN'"NOTRANSL: Füllen der KOMK für Infosätze
  EXPORTING
   I_EINA =  "Purchasing Info Record: General Data
*  I_T001W =  "Plants/Branches
   I_EINE =  "Purchasing Info Record: Purchasing Organization Data
   I_LFA1 =  "Vendor Master (General Section)
   I_T001 =  "Company Codes
   I_LFM1 =  "Vendor master record purchasing organization data
   I_KALSM =  "Procedure (Pricing, Output Control, Acct. Det., Costing,...)
*  I_KAPPL = 'M' "Application
*  I_EGIMP =  "
*  I_PRSDT =  "Date for pricing and exchange rate

 IMPORTING
   E_KOMK =  "Communication Header for Pricing

.

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_FILL_KOMK_IN

I_EINA - Purchasing Info Record: General Data

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

I_T001W - Plants/Branches

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

I_EINE - Purchasing Info Record: Purchasing Organization Data

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

I_LFA1 - Vendor Master (General Section)

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

I_T001 - Company Codes

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

I_LFM1 - Vendor master record purchasing organization data

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

I_KALSM - Procedure (Pricing, Output Control, Acct. Det., Costing,...)

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

I_KAPPL - Application

Data type: T681F-KAPPL
Default: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_EGIMP -

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

I_PRSDT - Date for pricing and exchange rate

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

EXPORTING Parameters details for ME_FILL_KOMK_IN

E_KOMK - Communication Header for Pricing

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

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

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