SAP ME_READ_RELEASE_QUANTITY Function Module for NOTRANSL: Ermitteln der abgerufenen Menge zu einer Kontraktposition
ME_READ_RELEASE_QUANTITY is a standard me read release 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: Ermitteln der abgerufenen Menge zu einer Kontraktposition 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 read release quantity FM, simply by entering the name ME_READ_RELEASE_QUANTITY into the relevant SAP transaction such as SE37 or SE38.
Function Group: EINR
Program Name: SAPLEINR
Main Program: SAPLEINR
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_READ_RELEASE_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_READ_RELEASE_QUANTITY'"NOTRANSL: Ermitteln der abgerufenen Menge zu einer Kontraktposition.
EXPORTING
I_KONNR = "Number of Principal Purchase Agreement
* I_KTPNR = "Item Number of Principal Purchase Agreement
* I_KTPNV = "Item Number of Principal Purchase Agreement
* I_KTPNB = "Item Number of Principal Purchase Agreement
* I_ALL_ENTRIES = "
IMPORTING
E_ABMNG = "Target Quantity
TABLES
* T_ABMNG = "Quantities Released Against a Contract Item
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_SAPLEINR_001 Calculation of Default GR Quantity and Over-/Underdelivery Tolerance
EXIT_SAPLEINR_002 Adopt Batch Numbers from Shipping Notification When Posting Goods Receipt
EXIT_SAPLEINR_003 Adjustm. of Qty. and Date for Price Determination, GR Against Sched. Agmt.
EXIT_SAPLEINR_004 Determine Earliest Delivery Date, GR Check (PO Only)
EXIT_SAPLEINR_400 Exit for IS-Oil re-pricing at MM Invoice Verification
IMPORTING Parameters details for ME_READ_RELEASE_QUANTITY
I_KONNR - Number of Principal Purchase Agreement
Data type: EKPO-KONNROptional: No
Call by Reference: No ( called with pass by value option)
I_KTPNR - Item Number of Principal Purchase Agreement
Data type: EKPO-KTPNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_KTPNV - Item Number of Principal Purchase Agreement
Data type: EKPO-KTPNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_KTPNB - Item Number of Principal Purchase Agreement
Data type: EKPO-KTPNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_ALL_ENTRIES -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ME_READ_RELEASE_QUANTITY
E_ABMNG - Target Quantity
Data type: EKPO-KTMNGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ME_READ_RELEASE_QUANTITY
T_ABMNG - Quantities Released Against a Contract Item
Data type: EKABMOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_READ_RELEASE_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_e_abmng | TYPE EKPO-KTMNG, " | |||
| lv_i_konnr | TYPE EKPO-KONNR, " | |||
| lt_t_abmng | TYPE STANDARD TABLE OF EKABM, " | |||
| lv_i_ktpnr | TYPE EKPO-KTPNR, " | |||
| lv_i_ktpnv | TYPE EKPO-KTPNR, " | |||
| lv_i_ktpnb | TYPE EKPO-KTPNR, " | |||
| lv_i_all_entries | TYPE EKPO. " |
|   CALL FUNCTION 'ME_READ_RELEASE_QUANTITY' "NOTRANSL: Ermitteln der abgerufenen Menge zu einer Kontraktposition |
| EXPORTING | ||
| I_KONNR | = lv_i_konnr | |
| I_KTPNR | = lv_i_ktpnr | |
| I_KTPNV | = lv_i_ktpnv | |
| I_KTPNB | = lv_i_ktpnb | |
| I_ALL_ENTRIES | = lv_i_all_entries | |
| IMPORTING | ||
| E_ABMNG | = lv_e_abmng | |
| TABLES | ||
| T_ABMNG | = lt_t_abmng | |
| . " ME_READ_RELEASE_QUANTITY | ||
ABAP code using 7.40 inline data declarations to call FM ME_READ_RELEASE_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 KTMNG FROM EKPO INTO @DATA(ld_e_abmng). | ||||
| "SELECT single KONNR FROM EKPO INTO @DATA(ld_i_konnr). | ||||
| "SELECT single KTPNR FROM EKPO INTO @DATA(ld_i_ktpnr). | ||||
| "SELECT single KTPNR FROM EKPO INTO @DATA(ld_i_ktpnv). | ||||
| "SELECT single KTPNR FROM EKPO INTO @DATA(ld_i_ktpnb). | ||||
Search for further information about these or an SAP related objects