SAP ME_UPDATE_EKRS Function Module for NOTRANSL: Verbuchen der Indizes für ERS
ME_UPDATE_EKRS is a standard me update ekrs 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: Verbuchen der Indizes für ERS 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 update ekrs FM, simply by entering the name ME_UPDATE_EKRS into the relevant SAP transaction such as SE37 or SE38.
Function Group: EINU
Program Name: SAPLEINU
Main Program: SAPLEINU
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function ME_UPDATE_EKRS 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_UPDATE_EKRS'"NOTRANSL: Verbuchen der Indizes für ERS.
EXPORTING
* I_INSERT = ' ' "
* I_DELETE = ' ' "Entries will be deleted
TABLES
T_EKRS = "
IMPORTING Parameters details for ME_UPDATE_EKRS
I_INSERT -
Data type: BEKPO-UPDKZDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DELETE - Entries will be deleted
Data type: BEKPO-UPDKZDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ME_UPDATE_EKRS
T_EKRS -
Data type: EKRSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_UPDATE_EKRS 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_t_ekrs | TYPE STANDARD TABLE OF EKRS, " | |||
| lv_i_insert | TYPE BEKPO-UPDKZ, " ' ' | |||
| lv_i_delete | TYPE BEKPO-UPDKZ. " ' ' |
|   CALL FUNCTION 'ME_UPDATE_EKRS' "NOTRANSL: Verbuchen der Indizes für ERS |
| EXPORTING | ||
| I_INSERT | = lv_i_insert | |
| I_DELETE | = lv_i_delete | |
| TABLES | ||
| T_EKRS | = lt_t_ekrs | |
| . " ME_UPDATE_EKRS | ||
ABAP code using 7.40 inline data declarations to call FM ME_UPDATE_EKRS
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 UPDKZ FROM BEKPO INTO @DATA(ld_i_insert). | ||||
| DATA(ld_i_insert) | = ' '. | |||
| "SELECT single UPDKZ FROM BEKPO INTO @DATA(ld_i_delete). | ||||
| DATA(ld_i_delete) | = ' '. | |||
Search for further information about these or an SAP related objects