SAP ME_READ_LAST_RELEASE Function Module for NOTRANSL: Lesen des letzten übermittelten Abrufs

Search SAP Function Modules

ME_READ_LAST_RELEASE is a standard me read last release 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 des letzten übermittelten Abrufs 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 last release FM, simply by entering the name ME_READ_LAST_RELEASE 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_READ_LAST_RELEASE 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_LAST_RELEASE'"NOTRANSL: Lesen des letzten übermittelten Abrufs
  EXPORTING
   I_EBELN =  "Purchasing Document Number
   I_EBELP =  "Item Number of Purchasing Document
*  I_FABKZ = ' ' "Indicator: Item Relevant to JIT Delivery Schedules
*  I_ABRDT = '99991230' "Date of Scheduling Agreement Release (Transmission Date)
*  I_ABRZT = '235999' "Time
*  I_WEKZ = ' ' "

 IMPORTING
   E_EKEK =  "Header Data for Scheduling Agreement Releases
   E_OFFMG =  "Scheduled Quantity

TABLES
*  E_EKEH =  "Scheduling Agreement Release Documentation

EXCEPTIONS
   NO_RELEASE = 1 

.

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_READ_LAST_RELEASE

I_EBELN - Purchasing Document Number

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

I_EBELP - Item Number of Purchasing Document

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

I_FABKZ - Indicator: Item Relevant to JIT Delivery Schedules

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

I_ABRDT - Date of Scheduling Agreement Release (Transmission Date)

Data type: EKEK-ABRDT
Default: '99991230'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ABRZT - Time

Data type: EKEK-ABRZT
Default: '235999'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_WEKZ -

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

EXPORTING Parameters details for ME_READ_LAST_RELEASE

E_EKEK - Header Data for Scheduling Agreement Releases

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

E_OFFMG - Scheduled Quantity

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

TABLES Parameters details for ME_READ_LAST_RELEASE

E_EKEH - Scheduling Agreement Release Documentation

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

EXCEPTIONS details

NO_RELEASE -

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

Copy and paste ABAP code example for ME_READ_LAST_RELEASE 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_READ_LAST_RELEASE

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