SAP ME_CONFIRMATION_READ_GR_BLOCK Function Module for NOTRANSL: Lesen WE-Sperrbestand
ME_CONFIRMATION_READ_GR_BLOCK is a standard me confirmation read gr block 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 WE-Sperrbestand 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 block FM, simply by entering the name ME_CONFIRMATION_READ_GR_BLOCK into the relevant SAP transaction such as SE37 or SE38.
Function Group: EINB
Program Name: SAPLEINB
Main Program: SAPLEINB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_CONFIRMATION_READ_GR_BLOCK 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_BLOCK'"NOTRANSL: Lesen WE-Sperrbestand.
EXPORTING
I_EBELN = "Purchasing Document Number
I_EBELP = "Item Number of Purchasing Document
I_ETENS = "Sequential Number of Vendor Confirmation
EXCEPTIONS
BLOCKED_STOCK = 1
IMPORTING Parameters details for ME_CONFIRMATION_READ_GR_BLOCK
I_EBELN - Purchasing Document Number
Data type: EKKO-EBELNOptional: No
Call by Reference: Yes
I_EBELP - Item Number of Purchasing Document
Data type: EKPO-EBELPOptional: No
Call by Reference: Yes
I_ETENS - Sequential Number of Vendor Confirmation
Data type: EKES-ETENSOptional: No
Call by Reference: Yes
EXCEPTIONS details
BLOCKED_STOCK -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ME_CONFIRMATION_READ_GR_BLOCK 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_i_ebeln | TYPE EKKO-EBELN, " | |||
| lv_blocked_stock | TYPE EKKO, " | |||
| lv_i_ebelp | TYPE EKPO-EBELP, " | |||
| lv_i_etens | TYPE EKES-ETENS. " |
|   CALL FUNCTION 'ME_CONFIRMATION_READ_GR_BLOCK' "NOTRANSL: Lesen WE-Sperrbestand |
| EXPORTING | ||
| I_EBELN | = lv_i_ebeln | |
| I_EBELP | = lv_i_ebelp | |
| I_ETENS | = lv_i_etens | |
| EXCEPTIONS | ||
| BLOCKED_STOCK = 1 | ||
| . " ME_CONFIRMATION_READ_GR_BLOCK | ||
ABAP code using 7.40 inline data declarations to call FM ME_CONFIRMATION_READ_GR_BLOCK
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 EBELN FROM EKKO INTO @DATA(ld_i_ebeln). | ||||
| "SELECT single EBELP FROM EKPO INTO @DATA(ld_i_ebelp). | ||||
| "SELECT single ETENS FROM EKES INTO @DATA(ld_i_etens). | ||||
Search for further information about these or an SAP related objects