SAP SPRT_DR_QUERY_PROCESSOR Function Module for
SPRT_DR_QUERY_PROCESSOR is a standard sprt dr query processor 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 sprt dr query processor FM, simply by entering the name SPRT_DR_QUERY_PROCESSOR into the relevant SAP transaction such as SE37 or SE38.
Function Group: SPRT
Program Name: SAPLSPRT
Main Program: SAPLSPRT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SPRT_DR_QUERY_PROCESSOR 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 'SPRT_DR_QUERY_PROCESSOR'".
EXPORTING
SOURCETYPE = "
TARGETTYPE = "
* ORDERBY = 1 "
* MAXRESULT = 500 "
TABLES
RESULTLIST = "
RELATIONS = "
SOURCELIST = "
EXCEPTIONS
UNKNOWN_SOURCE = 1 UNKNOWN_TARGET = 2 RELATION_NOT_SUPPORTED = 3 INVALID_SOURCE_KEY = 4 INVALID_RELATION = 5 NO_QUERY_AUTHORITY = 6 ERROR_GET_PROPERTY = 7 ERROR_GET_KEY = 8
IMPORTING Parameters details for SPRT_DR_QUERY_PROCESSOR
SOURCETYPE -
Data type: SPRTL4-SOURCETYPEOptional: No
Call by Reference: No ( called with pass by value option)
TARGETTYPE -
Data type: SPRTL4-TARGETTYPEOptional: No
Call by Reference: No ( called with pass by value option)
ORDERBY -
Data type: RSEUMOD-TBMAXSELDefault: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)
MAXRESULT -
Data type: RSEUMOD-TBMAXSELDefault: 500
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SPRT_DR_QUERY_PROCESSOR
RESULTLIST -
Data type: SPRTL6Optional: No
Call by Reference: No ( called with pass by value option)
RELATIONS -
Data type: SPRTL7Optional: No
Call by Reference: No ( called with pass by value option)
SOURCELIST -
Data type: SPRTL11Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UNKNOWN_SOURCE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_TARGET -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RELATION_NOT_SUPPORTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_SOURCE_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_RELATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_QUERY_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_GET_PROPERTY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_GET_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SPRT_DR_QUERY_PROCESSOR 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_resultlist | TYPE STANDARD TABLE OF SPRTL6, " | |||
| lv_sourcetype | TYPE SPRTL4-SOURCETYPE, " | |||
| lv_unknown_source | TYPE SPRTL4, " | |||
| lt_relations | TYPE STANDARD TABLE OF SPRTL7, " | |||
| lv_targettype | TYPE SPRTL4-TARGETTYPE, " | |||
| lv_unknown_target | TYPE SPRTL4, " | |||
| lv_orderby | TYPE RSEUMOD-TBMAXSEL, " 1 | |||
| lt_sourcelist | TYPE STANDARD TABLE OF SPRTL11, " | |||
| lv_relation_not_supported | TYPE SPRTL11, " | |||
| lv_maxresult | TYPE RSEUMOD-TBMAXSEL, " 500 | |||
| lv_invalid_source_key | TYPE RSEUMOD, " | |||
| lv_invalid_relation | TYPE RSEUMOD, " | |||
| lv_no_query_authority | TYPE RSEUMOD, " | |||
| lv_error_get_property | TYPE RSEUMOD, " | |||
| lv_error_get_key | TYPE RSEUMOD. " |
|   CALL FUNCTION 'SPRT_DR_QUERY_PROCESSOR' " |
| EXPORTING | ||
| SOURCETYPE | = lv_sourcetype | |
| TARGETTYPE | = lv_targettype | |
| ORDERBY | = lv_orderby | |
| MAXRESULT | = lv_maxresult | |
| TABLES | ||
| RESULTLIST | = lt_resultlist | |
| RELATIONS | = lt_relations | |
| SOURCELIST | = lt_sourcelist | |
| EXCEPTIONS | ||
| UNKNOWN_SOURCE = 1 | ||
| UNKNOWN_TARGET = 2 | ||
| RELATION_NOT_SUPPORTED = 3 | ||
| INVALID_SOURCE_KEY = 4 | ||
| INVALID_RELATION = 5 | ||
| NO_QUERY_AUTHORITY = 6 | ||
| ERROR_GET_PROPERTY = 7 | ||
| ERROR_GET_KEY = 8 | ||
| . " SPRT_DR_QUERY_PROCESSOR | ||
ABAP code using 7.40 inline data declarations to call FM SPRT_DR_QUERY_PROCESSOR
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 SOURCETYPE FROM SPRTL4 INTO @DATA(ld_sourcetype). | ||||
| "SELECT single TARGETTYPE FROM SPRTL4 INTO @DATA(ld_targettype). | ||||
| "SELECT single TBMAXSEL FROM RSEUMOD INTO @DATA(ld_orderby). | ||||
| DATA(ld_orderby) | = 1. | |||
| "SELECT single TBMAXSEL FROM RSEUMOD INTO @DATA(ld_maxresult). | ||||
| DATA(ld_maxresult) | = 500. | |||
Search for further information about these or an SAP related objects