SAP ME_GET_GR_QUANTITY Function Module for NOTRANSL: kumulierte wareneingangsmenge zum stichtag
ME_GET_GR_QUANTITY is a standard me get gr quantity 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: kumulierte wareneingangsmenge zum stichtag 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 get gr quantity FM, simply by entering the name ME_GET_GR_QUANTITY into the relevant SAP transaction such as SE37 or SE38.
Function Group: EINL
Program Name: SAPLEINL
Main Program: SAPLEINL
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_GET_GR_QUANTITY 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_GET_GR_QUANTITY'"NOTRANSL: kumulierte wareneingangsmenge zum stichtag.
EXPORTING
EBELN = "Purchasing Document Number
EBELP = "Item Number of Purchasing Document
WEBRE = "Indicator: GR-Based Invoice Verification
DATUM = "Posting Date in the Document
* PSTR_CPU = ' ' "Indicator: GR-Based Invoice Verification
* PSTR_BUD = 'X' "Indicator: GR-Based Invoice Verification
* PSTR_BLD = ' ' "Indicator: GR-Based Invoice Verification
IMPORTING
GRCMG = "Agreed Cumulative Quantity
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_SAPLEINL_001 Customer Enhancement: SA Releases: Determ. Sched. Line Type (E.g. Backlog)
IMPORTING Parameters details for ME_GET_GR_QUANTITY
EBELN - Purchasing Document Number
Data type: EKKO-EBELNOptional: No
Call by Reference: No ( called with pass by value option)
EBELP - Item Number of Purchasing Document
Data type: EKPO-EBELPOptional: No
Call by Reference: No ( called with pass by value option)
WEBRE - Indicator: GR-Based Invoice Verification
Data type: EKPO-WEBREOptional: No
Call by Reference: No ( called with pass by value option)
DATUM - Posting Date in the Document
Data type: EKBE-BUDATOptional: No
Call by Reference: No ( called with pass by value option)
PSTR_CPU - Indicator: GR-Based Invoice Verification
Data type: EKPO-WEBREDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
PSTR_BUD - Indicator: GR-Based Invoice Verification
Data type: EKPO-WEBREDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PSTR_BLD - Indicator: GR-Based Invoice Verification
Data type: EKPO-WEBREDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ME_GET_GR_QUANTITY
GRCMG - Agreed Cumulative Quantity
Data type: EKPO-ABFTZOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_GET_GR_QUANTITY 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_ebeln | TYPE EKKO-EBELN, " | |||
| lv_grcmg | TYPE EKPO-ABFTZ, " | |||
| lv_ebelp | TYPE EKPO-EBELP, " | |||
| lv_webre | TYPE EKPO-WEBRE, " | |||
| lv_datum | TYPE EKBE-BUDAT, " | |||
| lv_pstr_cpu | TYPE EKPO-WEBRE, " ' ' | |||
| lv_pstr_bud | TYPE EKPO-WEBRE, " 'X' | |||
| lv_pstr_bld | TYPE EKPO-WEBRE. " ' ' |
|   CALL FUNCTION 'ME_GET_GR_QUANTITY' "NOTRANSL: kumulierte wareneingangsmenge zum stichtag |
| EXPORTING | ||
| EBELN | = lv_ebeln | |
| EBELP | = lv_ebelp | |
| WEBRE | = lv_webre | |
| DATUM | = lv_datum | |
| PSTR_CPU | = lv_pstr_cpu | |
| PSTR_BUD | = lv_pstr_bud | |
| PSTR_BLD | = lv_pstr_bld | |
| IMPORTING | ||
| GRCMG | = lv_grcmg | |
| . " ME_GET_GR_QUANTITY | ||
ABAP code using 7.40 inline data declarations to call FM ME_GET_GR_QUANTITY
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_ebeln). | ||||
| "SELECT single ABFTZ FROM EKPO INTO @DATA(ld_grcmg). | ||||
| "SELECT single EBELP FROM EKPO INTO @DATA(ld_ebelp). | ||||
| "SELECT single WEBRE FROM EKPO INTO @DATA(ld_webre). | ||||
| "SELECT single BUDAT FROM EKBE INTO @DATA(ld_datum). | ||||
| "SELECT single WEBRE FROM EKPO INTO @DATA(ld_pstr_cpu). | ||||
| DATA(ld_pstr_cpu) | = ' '. | |||
| "SELECT single WEBRE FROM EKPO INTO @DATA(ld_pstr_bud). | ||||
| DATA(ld_pstr_bud) | = 'X'. | |||
| "SELECT single WEBRE FROM EKPO INTO @DATA(ld_pstr_bld). | ||||
| DATA(ld_pstr_bld) | = ' '. | |||
Search for further information about these or an SAP related objects