SAP ML_ENRICH_ITEM_GOODS_RECEIPT Function Module for









ML_ENRICH_ITEM_GOODS_RECEIPT is a standard ml enrich item goods receipt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ml enrich item goods receipt FM, simply by entering the name ML_ENRICH_ITEM_GOODS_RECEIPT into the relevant SAP transaction such as SE37 or SE38.

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



Function ML_ENRICH_ITEM_GOODS_RECEIPT 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 'ML_ENRICH_ITEM_GOODS_RECEIPT'"
EXPORTING
BUDAT = "
BLDAT = "
* ORDERTYP = 'N' "
* F_DBEFU = "
* LIFNR = "

TABLES
* XEBEFU = "
* XACCOUNTING_CR = "
* XACCOUNTING_DC_CR = "
* XEKBNK = "
* XEBEFU_CR = "
* XEKBNK_CR = "
* XDBEFU = "
* XBBEFU = "
* XEKBNK_KDM = "Purch. Fields Inventory Mgmt Overheads Exch. Rate Difference
* XACCOUNTING = "
* XACCOUNTING_DC = "
.



IMPORTING Parameters details for ML_ENRICH_ITEM_GOODS_RECEIPT

BUDAT -

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

BLDAT -

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

ORDERTYP -

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

F_DBEFU -

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

LIFNR -

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

TABLES Parameters details for ML_ENRICH_ITEM_GOODS_RECEIPT

XEBEFU -

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

XACCOUNTING_CR -

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

XACCOUNTING_DC_CR -

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

XEKBNK -

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

XEBEFU_CR -

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

XEKBNK_CR -

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

XDBEFU -

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

XBBEFU -

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

XEKBNK_KDM - Purch. Fields Inventory Mgmt Overheads Exch. Rate Difference

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

XACCOUNTING -

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

XACCOUNTING_DC -

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

Copy and paste ABAP code example for ML_ENRICH_ITEM_GOODS_RECEIPT 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_budat  TYPE BKPF-BUDAT, "   
lt_xebefu  TYPE STANDARD TABLE OF EBEFU, "   
lt_xaccounting_cr  TYPE STANDARD TABLE OF ACCOUNTING_CR, "   
lt_xaccounting_dc_cr  TYPE STANDARD TABLE OF ACCOUNTING_CR, "   
lv_bldat  TYPE BKPF-BLDAT, "   
lt_xekbnk  TYPE STANDARD TABLE OF EKBNK, "   
lv_ordertyp  TYPE C, "   'N'
lt_xebefu_cr  TYPE STANDARD TABLE OF EBEFU_CR, "   
lv_f_dbefu  TYPE DBEFU, "   
lt_xekbnk_cr  TYPE STANDARD TABLE OF EKBNK_CR, "   
lv_lifnr  TYPE LFA1-LIFNR, "   
lt_xdbefu  TYPE STANDARD TABLE OF DBEFU, "   
lt_xbbefu  TYPE STANDARD TABLE OF BBEFU, "   
lt_xekbnk_kdm  TYPE STANDARD TABLE OF EKBNK_KDM, "   
lt_xaccounting  TYPE STANDARD TABLE OF ACCOUNTING, "   
lt_xaccounting_dc  TYPE STANDARD TABLE OF ACCOUNTING. "   

  CALL FUNCTION 'ML_ENRICH_ITEM_GOODS_RECEIPT'  "
    EXPORTING
         BUDAT = lv_budat
         BLDAT = lv_bldat
         ORDERTYP = lv_ordertyp
         F_DBEFU = lv_f_dbefu
         LIFNR = lv_lifnr
    TABLES
         XEBEFU = lt_xebefu
         XACCOUNTING_CR = lt_xaccounting_cr
         XACCOUNTING_DC_CR = lt_xaccounting_dc_cr
         XEKBNK = lt_xekbnk
         XEBEFU_CR = lt_xebefu_cr
         XEKBNK_CR = lt_xekbnk_cr
         XDBEFU = lt_xdbefu
         XBBEFU = lt_xbbefu
         XEKBNK_KDM = lt_xekbnk_kdm
         XACCOUNTING = lt_xaccounting
         XACCOUNTING_DC = lt_xaccounting_dc
. " ML_ENRICH_ITEM_GOODS_RECEIPT




ABAP code using 7.40 inline data declarations to call FM ML_ENRICH_ITEM_GOODS_RECEIPT

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.

"SELECT single BUDAT FROM BKPF INTO @DATA(ld_budat).
 
 
 
 
"SELECT single BLDAT FROM BKPF INTO @DATA(ld_bldat).
 
 
DATA(ld_ordertyp) = 'N'.
 
 
 
 
"SELECT single LIFNR FROM LFA1 INTO @DATA(ld_lifnr).
 
 
 
 
 
 


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!