SAP ME_UPDATE_DOCUMENT_RESPONSE Function Module for NOTRANSL: Fortschreibung der Auftragsbestätigung - EDI Order Response
ME_UPDATE_DOCUMENT_RESPONSE is a standard me update document response 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: Fortschreibung der Auftragsbestätigung - EDI Order Response 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 document response FM, simply by entering the name ME_UPDATE_DOCUMENT_RESPONSE 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_DOCUMENT_RESPONSE 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_DOCUMENT_RESPONSE'"NOTRANSL: Fortschreibung der Auftragsbestätigung - EDI Order Response.
TABLES
XEKPO = "Table of items to be updated
EXCEPTIONS
UPDATE_MISTAKE = 1
TABLES Parameters details for ME_UPDATE_DOCUMENT_RESPONSE
XEKPO - Table of items to be updated
Data type: UEKPOOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UPDATE_MISTAKE - Error during update
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_UPDATE_DOCUMENT_RESPONSE 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_xekpo | TYPE STANDARD TABLE OF UEKPO, " | |||
| lv_update_mistake | TYPE UEKPO. " |
|   CALL FUNCTION 'ME_UPDATE_DOCUMENT_RESPONSE' "NOTRANSL: Fortschreibung der Auftragsbestätigung - EDI Order Response |
| TABLES | ||
| XEKPO | = lt_xekpo | |
| EXCEPTIONS | ||
| UPDATE_MISTAKE = 1 | ||
| . " ME_UPDATE_DOCUMENT_RESPONSE | ||
ABAP code using 7.40 inline data declarations to call FM ME_UPDATE_DOCUMENT_RESPONSE
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