SAP ME_CONFIRMATION_READ_GR Function Module for NOTRANSL: Lesen Bestellbestätigung für Wareneingang

Search SAP Function Modules

ME_CONFIRMATION_READ_GR is a standard me confirmation read gr 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: Lesen Bestellbestätigung für Wareneingang 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 confirmation read gr FM, simply by entering the name ME_CONFIRMATION_READ_GR into the relevant SAP transaction such as SE37 or SE38.

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

Function ME_CONFIRMATION_READ_GR 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_CONFIRMATION_READ_GR'"NOTRANSL: Lesen Bestellbestätigung für Wareneingang
  EXPORTING
   I_BSTAE =  "Confirmation control
   I_EBELN =  "Purchase order/scheduling agreement
   I_EBELP =  "Item
*  I_VBELN = ' ' "Shipping notification
*  I_VBELP = '000000' "Shipping notification item

 IMPORTING
   E_LAMNG =  "Cumulative shipping notification quantity
   E_LWMNG =  "Cumulative GR quantity to the payment advice
   E_KZVOR =  "

CHANGING
*  C_CONF =  "

TABLES
   XEKES =  "

EXCEPTIONS
   NO_CONFIRMATION = 1 

.

IMPORTING Parameters details for ME_CONFIRMATION_READ_GR

I_BSTAE - Confirmation control

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

I_EBELN - Purchase order/scheduling agreement

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

I_EBELP - Item

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

I_VBELN - Shipping notification

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

I_VBELP - Shipping notification item

Data type: EKES-VBELP
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ME_CONFIRMATION_READ_GR

E_LAMNG - Cumulative shipping notification quantity

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

E_LWMNG - Cumulative GR quantity to the payment advice

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

E_KZVOR -

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

CHANGING Parameters details for ME_CONFIRMATION_READ_GR

C_CONF -

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

TABLES Parameters details for ME_CONFIRMATION_READ_GR

XEKES -

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

EXCEPTIONS details

NO_CONFIRMATION -

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

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

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