SAP GRPC_API_QRY_COLUMNS_RETRIEVE Function Module for GRPC Read query columns
GRPC_API_QRY_COLUMNS_RETRIEVE is a standard grpc api qry columns retrieve SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for GRPC Read query columns 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 grpc api qry columns retrieve FM, simply by entering the name GRPC_API_QRY_COLUMNS_RETRIEVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_QUERY_INTEGRATION
Program Name: SAPLGRPC_QUERY_INTEGRATION
Main Program: SAPLGRPC_QUERY_INTEGRATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GRPC_API_QRY_COLUMNS_RETRIEVE 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 'GRPC_API_QRY_COLUMNS_RETRIEVE'"GRPC Read query columns.
EXPORTING
I_SESSION_ID = "GRPC unique session ID
I_SYSTYPE = "System Type
I_CONNECTOR = "Logical Destination (Specified in Function Call)
I_USERGROUP = "SAP Query (S): Name of a user group
* I_WORK' ' = ' ' "SAP Query (S): Work Area ID
I_QUERYNAME = "Query Name
IMPORTING
E_RETURN_CODE = "Natural number
TABLES
* ET_QUERY_SELFIELDS = "Table of GRPC Query Columns
* ET_QUERY_PARAMETRS = "Table of GRPC Query Columns
* ET_MESSAGE = "Table with BAPI Return Information
IMPORTING Parameters details for GRPC_API_QRY_COLUMNS_RETRIEVE
I_SESSION_ID - GRPC unique session ID
Data type: GRPC_API_SESSION_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_SYSTYPE - System Type
Data type: GRPC_SYSTEMTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_CONNECTOR - Logical Destination (Specified in Function Call)
Data type: GRPC_CONNECTOROptional: No
Call by Reference: No ( called with pass by value option)
I_USERGROUP - SAP Query (S): Name of a user group
Data type: AQADEF-BGNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_WORKSPACE - SAP Query (S): Work Area ID
Data type: AQADEF-WSIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_QUERYNAME - Query Name
Data type: GRPC_QRY_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPC_API_QRY_COLUMNS_RETRIEVE
E_RETURN_CODE - Natural number
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GRPC_API_QRY_COLUMNS_RETRIEVE
ET_QUERY_SELFIELDS - Table of GRPC Query Columns
Data type: GRPC_T_QUERY_COLUMNOptional: Yes
Call by Reference: Yes
ET_QUERY_PARAMETRS - Table of GRPC Query Columns
Data type: GRPC_T_QUERY_COLUMNOptional: Yes
Call by Reference: Yes
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for GRPC_API_QRY_COLUMNS_RETRIEVE 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_i_session_id | TYPE GRPC_API_SESSION_ID, " | |||
| lv_e_return_code | TYPE INT4, " | |||
| lt_et_query_selfields | TYPE STANDARD TABLE OF GRPC_T_QUERY_COLUMN, " | |||
| lv_i_systype | TYPE GRPC_SYSTEMTYPE, " | |||
| lt_et_query_parametrs | TYPE STANDARD TABLE OF GRPC_T_QUERY_COLUMN, " | |||
| lt_et_message | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_i_connector | TYPE GRPC_CONNECTOR, " | |||
| lv_i_usergroup | TYPE AQADEF-BGNAME, " | |||
| lv_i_workspace | TYPE AQADEF-WSID, " SPACE | |||
| lv_i_queryname | TYPE GRPC_QRY_NAME. " |
|   CALL FUNCTION 'GRPC_API_QRY_COLUMNS_RETRIEVE' "GRPC Read query columns |
| EXPORTING | ||
| I_SESSION_ID | = lv_i_session_id | |
| I_SYSTYPE | = lv_i_systype | |
| I_CONNECTOR | = lv_i_connector | |
| I_USERGROUP | = lv_i_usergroup | |
| I_WORKSPACE | = lv_i_workspace | |
| I_QUERYNAME | = lv_i_queryname | |
| IMPORTING | ||
| E_RETURN_CODE | = lv_e_return_code | |
| TABLES | ||
| ET_QUERY_SELFIELDS | = lt_et_query_selfields | |
| ET_QUERY_PARAMETRS | = lt_et_query_parametrs | |
| ET_MESSAGE | = lt_et_message | |
| . " GRPC_API_QRY_COLUMNS_RETRIEVE | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_API_QRY_COLUMNS_RETRIEVE
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 BGNAME FROM AQADEF INTO @DATA(ld_i_usergroup). | ||||
| "SELECT single WSID FROM AQADEF INTO @DATA(ld_i_workspace). | ||||
| DATA(ld_i_workspace) | = ' '. | |||
Search for further information about these or an SAP related objects