SAP GRPC_API_BWQUERY_RETRIEVE Function Module for Retrieve BW query
GRPC_API_BWQUERY_RETRIEVE is a standard grpc api bwquery 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 Retrieve BW query 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 bwquery retrieve FM, simply by entering the name GRPC_API_BWQUERY_RETRIEVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_BWQUERY
Program Name: SAPLGRPC_API_BWQUERY
Main Program: SAPLGRPC_API_BWQUERY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRPC_API_BWQUERY_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_BWQUERY_RETRIEVE'"Retrieve BW query.
EXPORTING
I_SESSION_ID = "GRPC unique session ID
I_CONNECTOR = "Connector
I_SCRIPT = "Script ID
IMPORTING
E_RETURN_CODE = "Return Value of ABAP Statements
ET_MESSAGE = "Table with BAPI Return Information
E_TXT = "
E_DESCR = "
E_FURTHER_INFO = "
ET_PARAM_IN = "
ET_PARAM_OUT = "
IMPORTING Parameters details for GRPC_API_BWQUERY_RETRIEVE
I_SESSION_ID - GRPC unique session ID
Data type: GRPC_API_SESSION_IDOptional: No
Call by Reference: Yes
I_CONNECTOR - Connector
Data type: STRINGOptional: No
Call by Reference: Yes
I_SCRIPT - Script ID
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for GRPC_API_BWQUERY_RETRIEVE
E_RETURN_CODE - Return Value of ABAP Statements
Data type: SYSUBRCOptional: No
Call by Reference: Yes
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
E_TXT -
Data type: STRINGOptional: No
Call by Reference: Yes
E_DESCR -
Data type: STRINGOptional: No
Call by Reference: Yes
E_FURTHER_INFO -
Data type: STRINGOptional: No
Call by Reference: Yes
ET_PARAM_IN -
Data type: IF_GRFN_CCI_PROXY=>T_SCRIPT_PARAM_INOptional: No
Call by Reference: Yes
ET_PARAM_OUT -
Data type: IF_GRFN_CCI_PROXY=>T_SCRIPT_PARAM_OUTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GRPC_API_BWQUERY_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 SYSUBRC, " | |||
| lv_et_message | TYPE BAPIRETTAB, " | |||
| lv_i_connector | TYPE STRING, " | |||
| lv_e_txt | TYPE STRING, " | |||
| lv_i_script | TYPE STRING, " | |||
| lv_e_descr | TYPE STRING, " | |||
| lv_e_further_info | TYPE STRING, " | |||
| lv_et_param_in | TYPE IF_GRFN_CCI_PROXY=>T_SCRIPT_PARAM_IN, " | |||
| lv_et_param_out | TYPE IF_GRFN_CCI_PROXY=>T_SCRIPT_PARAM_OUT. " |
|   CALL FUNCTION 'GRPC_API_BWQUERY_RETRIEVE' "Retrieve BW query |
| EXPORTING | ||
| I_SESSION_ID | = lv_i_session_id | |
| I_CONNECTOR | = lv_i_connector | |
| I_SCRIPT | = lv_i_script | |
| IMPORTING | ||
| E_RETURN_CODE | = lv_e_return_code | |
| ET_MESSAGE | = lv_et_message | |
| E_TXT | = lv_e_txt | |
| E_DESCR | = lv_e_descr | |
| E_FURTHER_INFO | = lv_e_further_info | |
| ET_PARAM_IN | = lv_et_param_in | |
| ET_PARAM_OUT | = lv_et_param_out | |
| . " GRPC_API_BWQUERY_RETRIEVE | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_API_BWQUERY_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.Search for further information about these or an SAP related objects