SAP ME_READ_RELEASE_DOCU Function Module for NOTRANSL: Lesen Abrufdokumentation und Summenermittlung
ME_READ_RELEASE_DOCU is a standard me read release docu 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 Abrufdokumentation und Summenermittlung 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 docu FM, simply by entering the name ME_READ_RELEASE_DOCU into the relevant SAP transaction such as SE37 or SE38.
Function Group: EINR
Program Name: SAPLEINR
Main Program: SAPLEINR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_READ_RELEASE_DOCU 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_DOCU'"NOTRANSL: Lesen Abrufdokumentation und Summenermittlung.
EXPORTING
BUKRS = "Company Code
EBELN = "Purchasing Document Number
* EBELP = 00000 "Item Number of Purchasing Document
WAERS = "Currency Key
WKURS = "Exchange Rate
* IV_HIPO_CALL = "Checkbox
* IV_RESET_DATA = "Checkbox
IMPORTING
SUWRT = "Target Value for Header Area per Distribution
TABLES
* XADO = "Release Documentation in Foreign Currency
* XADOS = "Totals, Release Documentation
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_DOCU
BUKRS - Company Code
Data type: EKKO-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
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-EBELPDefault: 00000
Optional: Yes
Call by Reference: No ( called with pass by value option)
WAERS - Currency Key
Data type: EKKO-WAERSOptional: No
Call by Reference: No ( called with pass by value option)
WKURS - Exchange Rate
Data type: EKKO-WKURSOptional: No
Call by Reference: No ( called with pass by value option)
IV_HIPO_CALL - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: Yes
IV_RESET_DATA - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ME_READ_RELEASE_DOCU
SUWRT - Target Value for Header Area per Distribution
Data type: EKKO-KTWRTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ME_READ_RELEASE_DOCU
XADO - Release Documentation in Foreign Currency
Data type: EKABFOptional: Yes
Call by Reference: No ( called with pass by value option)
XADOS - Totals, Release Documentation
Data type: EKABSOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_READ_RELEASE_DOCU 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: | ||||
| lt_xado | TYPE STANDARD TABLE OF EKABF, " | |||
| lv_bukrs | TYPE EKKO-BUKRS, " | |||
| lv_suwrt | TYPE EKKO-KTWRT, " | |||
| lv_ebeln | TYPE EKKO-EBELN, " | |||
| lt_xados | TYPE STANDARD TABLE OF EKABS, " | |||
| lv_ebelp | TYPE EKPO-EBELP, " 00000 | |||
| lv_waers | TYPE EKKO-WAERS, " | |||
| lv_wkurs | TYPE EKKO-WKURS, " | |||
| lv_iv_hipo_call | TYPE XFELD, " | |||
| lv_iv_reset_data | TYPE XFELD. " |
|   CALL FUNCTION 'ME_READ_RELEASE_DOCU' "NOTRANSL: Lesen Abrufdokumentation und Summenermittlung |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| EBELN | = lv_ebeln | |
| EBELP | = lv_ebelp | |
| WAERS | = lv_waers | |
| WKURS | = lv_wkurs | |
| IV_HIPO_CALL | = lv_iv_hipo_call | |
| IV_RESET_DATA | = lv_iv_reset_data | |
| IMPORTING | ||
| SUWRT | = lv_suwrt | |
| TABLES | ||
| XADO | = lt_xado | |
| XADOS | = lt_xados | |
| . " ME_READ_RELEASE_DOCU | ||
ABAP code using 7.40 inline data declarations to call FM ME_READ_RELEASE_DOCU
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 BUKRS FROM EKKO INTO @DATA(ld_bukrs). | ||||
| "SELECT single KTWRT FROM EKKO INTO @DATA(ld_suwrt). | ||||
| "SELECT single EBELN FROM EKKO INTO @DATA(ld_ebeln). | ||||
| "SELECT single EBELP FROM EKPO INTO @DATA(ld_ebelp). | ||||
| DATA(ld_ebelp) | = 00000. | |||
| "SELECT single WAERS FROM EKKO INTO @DATA(ld_waers). | ||||
| "SELECT single WKURS FROM EKKO INTO @DATA(ld_wkurs). | ||||
Search for further information about these or an SAP related objects