SAP RS_VC_GET_QUERY_VIEW_DATA Function Module for Get Data for a Query or View
RS_VC_GET_QUERY_VIEW_DATA is a standard rs vc get query view 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 Get Data for a Query or View 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 rs vc get query view data FM, simply by entering the name RS_VC_GET_QUERY_VIEW_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: RS_VC
Program Name: SAPLRS_VC
Main Program: SAPLRS_VC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RS_VC_GET_QUERY_VIEW_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 'RS_VC_GET_QUERY_VIEW_DATA'"Get Data for a Query or View.
EXPORTING
* I_INFOPROVIDER = "Technical Name of InfoProvider
* I_QUERY = "Technical Name of Query
* I_VIEW_ID = "Technical Name of a View
* I_T_PARAMETER = "Parameterization of Request
IMPORTING
E_AXIS_INFO = "Information on Axes
E_CELL_DATA = "Data Cells
E_AXIS_DATA = "Axis Data
E_TXT_SYMBOLS = "Text Symbols
TABLES
* E_T_MESSAGES = "Message Collector
EXCEPTIONS
NO_APPLICABLE_DATA = 1 INVALID_VARIABLE_VALUES = 2 NO_AUTHORITY = 3 ABORT = 4 INVALID_INPUT = 5 INVALID_VIEW = 6
IMPORTING Parameters details for RS_VC_GET_QUERY_VIEW_DATA
I_INFOPROVIDER - Technical Name of InfoProvider
Data type: RSINFOPROVOptional: Yes
Call by Reference: No ( called with pass by value option)
I_QUERY - Technical Name of Query
Data type: RSZCOMPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_VIEW_ID - Technical Name of a View
Data type: RSZVIEWIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_T_PARAMETER - Parameterization of Request
Data type: RRXW3TQUERYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RS_VC_GET_QUERY_VIEW_DATA
E_AXIS_INFO - Information on Axes
Data type: RRWS_THX_AXIS_INFOOptional: No
Call by Reference: No ( called with pass by value option)
E_CELL_DATA - Data Cells
Data type: RRWS_T_CELLOptional: No
Call by Reference: No ( called with pass by value option)
E_AXIS_DATA - Axis Data
Data type: RRWS_THX_AXIS_DATAOptional: No
Call by Reference: No ( called with pass by value option)
E_TXT_SYMBOLS - Text Symbols
Data type: RRWS_T_TEXT_SYMBOLSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RS_VC_GET_QUERY_VIEW_DATA
E_T_MESSAGES - Message Collector
Data type: SMESGOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_APPLICABLE_DATA - No Applicable Data
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_VARIABLE_VALUES - Invalid Variable Values
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY - No Authorization for Data
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ABORT - Cancellation
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_INPUT - Invalid Call Parameters
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_VIEW - Invalid View
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RS_VC_GET_QUERY_VIEW_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_e_axis_info | TYPE RRWS_THX_AXIS_INFO, " | |||
| lt_e_t_messages | TYPE STANDARD TABLE OF SMESG, " | |||
| lv_i_infoprovider | TYPE RSINFOPROV, " | |||
| lv_no_applicable_data | TYPE RSINFOPROV, " | |||
| lv_i_query | TYPE RSZCOMPID, " | |||
| lv_e_cell_data | TYPE RRWS_T_CELL, " | |||
| lv_invalid_variable_values | TYPE RRWS_T_CELL, " | |||
| lv_i_view_id | TYPE RSZVIEWID, " | |||
| lv_e_axis_data | TYPE RRWS_THX_AXIS_DATA, " | |||
| lv_no_authority | TYPE RRWS_THX_AXIS_DATA, " | |||
| lv_abort | TYPE RRWS_THX_AXIS_DATA, " | |||
| lv_e_txt_symbols | TYPE RRWS_T_TEXT_SYMBOLS, " | |||
| lv_i_t_parameter | TYPE RRXW3TQUERY, " | |||
| lv_invalid_input | TYPE RRXW3TQUERY, " | |||
| lv_invalid_view | TYPE RRXW3TQUERY. " |
|   CALL FUNCTION 'RS_VC_GET_QUERY_VIEW_DATA' "Get Data for a Query or View |
| EXPORTING | ||
| I_INFOPROVIDER | = lv_i_infoprovider | |
| I_QUERY | = lv_i_query | |
| I_VIEW_ID | = lv_i_view_id | |
| I_T_PARAMETER | = lv_i_t_parameter | |
| IMPORTING | ||
| E_AXIS_INFO | = lv_e_axis_info | |
| E_CELL_DATA | = lv_e_cell_data | |
| E_AXIS_DATA | = lv_e_axis_data | |
| E_TXT_SYMBOLS | = lv_e_txt_symbols | |
| TABLES | ||
| E_T_MESSAGES | = lt_e_t_messages | |
| EXCEPTIONS | ||
| NO_APPLICABLE_DATA = 1 | ||
| INVALID_VARIABLE_VALUES = 2 | ||
| NO_AUTHORITY = 3 | ||
| ABORT = 4 | ||
| INVALID_INPUT = 5 | ||
| INVALID_VIEW = 6 | ||
| . " RS_VC_GET_QUERY_VIEW_DATA | ||
ABAP code using 7.40 inline data declarations to call FM RS_VC_GET_QUERY_VIEW_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