STREX_PHY_QUEUE_ENTRIES_GET SAP Function module

STREX_PHY_QUEUE_ENTRIES_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name STREX_PHY_QUEUE_ENTRIES_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: STREX_INDEX
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM STREX_PHY_QUEUE_ENTRIES_GET - STREX PHY QUEUE ENTRIES GET

CALL FUNCTION 'STREX_PHY_QUEUE_ENTRIES_GET' "
  EXPORTING
    index_id =                  " guid_32       GUID in 'CHAR' Format in Uppercase
*   doc_state_filter =          " strx_dstat
*   retry_level_filter =        " i
*   doc_ids_filter =            " strx_dids
  IMPORTING
    call_return_code =          " strx_rctxt    Return Code with Text
    queued_docs =               " strx_qdocs    Documents with Queuing Information
  EXCEPTIONS
    APPENDING_NODE_FAILED = 1   "
    RENDERING_FAILED = 2        "
    HTTP_SERVER_ERROR = 3       "               Error when Communicating with TRex Server
    PARSING_RESPONSE_FAILED = 4  "
    .  "  STREX_PHY_QUEUE_ENTRIES_GET

ABAP code example for Function Module STREX_PHY_QUEUE_ENTRIES_GET

The ABAP code below is a full code listing to execute function module STREX_PHY_QUEUE_ENTRIES_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_call_return_code  
 
 TYPE STRX_RCTXT
,
ld_queued_docs  
 
 TYPE STRX_QDOCS
.


DATA(ld_index_id) = 'Check type of data required'.

DATA(ld_doc_state_filter) = 'Check type of data required'.

DATA(ld_retry_level_filter) = 'Check type of data required'.

DATA(ld_doc_ids_filter) = 'Check type of data required'.
.

CALL FUNCTION 'STREX_PHY_QUEUE_ENTRIES_GET'
  EXPORTING
    index_id =                   ld_index_id
*   doc_state_filter =           ld_doc_state_filter
*   retry_level_filter =         ld_retry_level_filter
*   doc_ids_filter =             ld_doc_ids_filter
  IMPORTING
    call_return_code =           ld_call_return_code
    queued_docs =                ld_queued_docs
  EXCEPTIONS
    APPENDING_NODE_FAILED =      1
    RENDERING_FAILED =           2
    HTTP_SERVER_ERROR =          3
    PARSING_RESPONSE_FAILED =    4
    .  "  STREX_PHY_QUEUE_ENTRIES_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_call_return_code
 
 TYPE STRX_RCTXT ,
ld_index_id
 
 TYPE GUID_32 ,
ld_queued_docs
 
 TYPE STRX_QDOCS ,
ld_doc_state_filter
 
 TYPE STRX_DSTAT ,
ld_retry_level_filter
 
 TYPE I ,
ld_doc_ids_filter
 
 TYPE STRX_DIDS .


ld_index_id = 'Check type of data required'.
ld_doc_state_filter = 'Check type of data required'.
ld_retry_level_filter = 'Check type of data required'.
ld_doc_ids_filter = 'Check type of data required'.