SAP ME_RT_DSD_DISPLAY_QUEUE_DATA Function Module for FM to retrieve the XML data from the queue
ME_RT_DSD_DISPLAY_QUEUE_DATA is a standard me rt dsd display queue data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FM to retrieve the XML data from the queue 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 rt dsd display queue data FM, simply by entering the name ME_RT_DSD_DISPLAY_QUEUE_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: ME_RT_DSD
Program Name: SAPLME_RT_DSD
Main Program: SAPLME_RT_DSD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ME_RT_DSD_DISPLAY_QUEUE_DATA 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_RT_DSD_DISPLAY_QUEUE_DATA'"FM to retrieve the XML data from the queue.
EXPORTING
ME_USER = "merep_char32
SYNC_TYPE = "Sync Type
IMPORTING
PACKAGE_DATA = "
RETURN = "Return Parameter
IMPORTING Parameters details for ME_RT_DSD_DISPLAY_QUEUE_DATA
ME_USER - merep_char32
Data type: MEREP_CHAR32Optional: No
Call by Reference: No ( called with pass by value option)
SYNC_TYPE - Sync Type
Data type: MEREP_SYNC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ME_RT_DSD_DISPLAY_QUEUE_DATA
PACKAGE_DATA -
Data type: XSTRINGOptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_RT_DSD_DISPLAY_QUEUE_DATA 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_me_user | TYPE MEREP_CHAR32, " | |||
| lv_package_data | TYPE XSTRING, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_sync_type | TYPE MEREP_SYNC_TYPE. " |
|   CALL FUNCTION 'ME_RT_DSD_DISPLAY_QUEUE_DATA' "FM to retrieve the XML data from the queue |
| EXPORTING | ||
| ME_USER | = lv_me_user | |
| SYNC_TYPE | = lv_sync_type | |
| IMPORTING | ||
| PACKAGE_DATA | = lv_package_data | |
| RETURN | = lv_return | |
| . " ME_RT_DSD_DISPLAY_QUEUE_DATA | ||
ABAP code using 7.40 inline data declarations to call FM ME_RT_DSD_DISPLAY_QUEUE_DATA
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