SAP SKWR_QUEUE_ENTRIES_GET Function Module for









SKWR_QUEUE_ENTRIES_GET is a standard skwr queue entries get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 skwr queue entries get FM, simply by entering the name SKWR_QUEUE_ENTRIES_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: SKWR_INDEX
Program Name: SAPLSKWR_INDEX
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SKWR_QUEUE_ENTRIES_GET 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 'SKWR_QUEUE_ENTRIES_GET'"
EXPORTING
INDEX_ID = "GUID in 'CHAR' Format in Uppercase
* DOC_STATE_FILTER = "
* RETRY_LEVEL_FILTER = "

IMPORTING
QUEUED_DOCS = "IOs with Queuing Information

EXCEPTIONS
FAILED = 1 XML_ERROR = 2 COMMUNICATION_ERROR = 3
.



IMPORTING Parameters details for SKWR_QUEUE_ENTRIES_GET

INDEX_ID - GUID in 'CHAR' Format in Uppercase

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

DOC_STATE_FILTER -

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

RETRY_LEVEL_FILTER -

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

EXPORTING Parameters details for SKWR_QUEUE_ENTRIES_GET

QUEUED_DOCS - IOs with Queuing Information

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

EXCEPTIONS details

FAILED -

Data type:
Optional: No
Call by Reference: Yes

XML_ERROR -

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SKWR_QUEUE_ENTRIES_GET 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_failed  TYPE STRING, "   
lv_index_id  TYPE GUID_32, "   
lv_queued_docs  TYPE SKWR_QDOCS, "   
lv_xml_error  TYPE SKWR_QDOCS, "   
lv_doc_state_filter  TYPE STRX_DSTAT, "   
lv_retry_level_filter  TYPE I, "   
lv_communication_error  TYPE I. "   

  CALL FUNCTION 'SKWR_QUEUE_ENTRIES_GET'  "
    EXPORTING
         INDEX_ID = lv_index_id
         DOC_STATE_FILTER = lv_doc_state_filter
         RETRY_LEVEL_FILTER = lv_retry_level_filter
    IMPORTING
         QUEUED_DOCS = lv_queued_docs
    EXCEPTIONS
        FAILED = 1
        XML_ERROR = 2
        COMMUNICATION_ERROR = 3
. " SKWR_QUEUE_ENTRIES_GET




ABAP code using 7.40 inline data declarations to call FM SKWR_QUEUE_ENTRIES_GET

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!