SAP EDI_DOCUMENT_STATUS_DISPLAY Function Module for Display last status record for current IDoc
EDI_DOCUMENT_STATUS_DISPLAY is a standard edi document status display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display last status record for current IDoc 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 edi document status display FM, simply by entering the name EDI_DOCUMENT_STATUS_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDI5
Program Name: SAPLEDI5
Main Program: SAPLEDI5
Appliation area: S
Release date: 25-Sep-1996
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EDI_DOCUMENT_STATUS_DISPLAY 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 'EDI_DOCUMENT_STATUS_DISPLAY'"Display last status record for current IDoc.
EXPORTING
DOCNUM = "Number of current IDoc
* ACTIONS = ' ' "6 bytes facilitating further processing
* STATUS_KEY = ' ' "Display should begin with this status record
* CALL_ASYN = ' ' "in new session - internal use only -
* TREE_DISPLAY = 'Y' "Use tree display?
IMPORTING
ACTION = "Action to be executed
EXCEPTIONS
NO_STATUS_RECORD_FOUND = 1
IMPORTING Parameters details for EDI_DOCUMENT_STATUS_DISPLAY
DOCNUM - Number of current IDoc
Data type: EDIDD-DOCNUMOptional: No
Call by Reference: No ( called with pass by value option)
ACTIONS - 6 bytes facilitating further processing
Data type: EDI_STFLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
STATUS_KEY - Display should begin with this status record
Data type: EDIDS_KEYDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
CALL_ASYN - in new session - internal use only -
Data type: EDI_HELP-ERROR_FLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TREE_DISPLAY - Use tree display?
Data type: EDI_HELP-DBR_OPTIONDefault: 'Y'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EDI_DOCUMENT_STATUS_DISPLAY
ACTION - Action to be executed
Data type: SY-UCOMMOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_STATUS_RECORD_FOUND - No status record exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EDI_DOCUMENT_STATUS_DISPLAY 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_action | TYPE SY-UCOMM, " | |||
| lv_docnum | TYPE EDIDD-DOCNUM, " | |||
| lv_no_status_record_found | TYPE EDIDD, " | |||
| lv_actions | TYPE EDI_STFLAG, " ' ' | |||
| lv_status_key | TYPE EDIDS_KEY, " ' ' | |||
| lv_call_asyn | TYPE EDI_HELP-ERROR_FLAG, " ' ' | |||
| lv_tree_display | TYPE EDI_HELP-DBR_OPTION. " 'Y' |
|   CALL FUNCTION 'EDI_DOCUMENT_STATUS_DISPLAY' "Display last status record for current IDoc |
| EXPORTING | ||
| DOCNUM | = lv_docnum | |
| ACTIONS | = lv_actions | |
| STATUS_KEY | = lv_status_key | |
| CALL_ASYN | = lv_call_asyn | |
| TREE_DISPLAY | = lv_tree_display | |
| IMPORTING | ||
| ACTION | = lv_action | |
| EXCEPTIONS | ||
| NO_STATUS_RECORD_FOUND = 1 | ||
| . " EDI_DOCUMENT_STATUS_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM EDI_DOCUMENT_STATUS_DISPLAY
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 UCOMM FROM SY INTO @DATA(ld_action). | ||||
| "SELECT single DOCNUM FROM EDIDD INTO @DATA(ld_docnum). | ||||
| DATA(ld_actions) | = ' '. | |||
| DATA(ld_status_key) | = ' '. | |||
| "SELECT single ERROR_FLAG FROM EDI_HELP INTO @DATA(ld_call_asyn). | ||||
| DATA(ld_call_asyn) | = ' '. | |||
| "SELECT single DBR_OPTION FROM EDI_HELP INTO @DATA(ld_tree_display). | ||||
| DATA(ld_tree_display) | = 'Y'. | |||
Search for further information about these or an SAP related objects