SAP Function Modules

comments icon Comments

GRPC_API_SAPQUERY_EXECUTE SAP Function module - Execute SAP Query Control







GRPC_API_SAPQUERY_EXECUTE 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 GRPC_API_SAPQUERY_EXECUTE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: GRPC_API_SAPQEURY
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM GRPC_API_SAPQUERY_EXECUTE - GRPC API SAPQUERY EXECUTE 





CALL FUNCTION 'GRPC_API_SAPQUERY_EXECUTE' "Execute SAP Query Control
  EXPORTING
    i_session_id =              " grpc_api_session_id  GRPC unique session ID
    i_connector =               " string        Target Connector
*   i_queryname =               " grfn_sqname   Query Name
*   i_usergroup =               " grfn_squsergroup  SAP Query (S): Name of a user group
*   i_queryarea = SPACE         " grfn_sqworkspace  SAP Query (S): Work Area ID
*   i_variant =                 " grfn_sqvariant  Variant name
*   i_script =                  " string
    i_maxrows = 100             " int4          Natural number
    it_queryparams =            " grpc_t_query_param_value  rsparams Table
  IMPORTING
    e_return_code =             " sysubrc       Natural number
    et_message =                " bapirettab    Table with BAPI Return Information
    et_data =                   " data          SAP Query (L): Data line for download to memory
    et_param_out =              " if_grfn_cci_proxy=>t_script_param_out
    .  "  GRPC_API_SAPQUERY_EXECUTE

ABAP code example for Function Module GRPC_API_SAPQUERY_EXECUTE





The ABAP code below is a full code listing to execute function module GRPC_API_SAPQUERY_EXECUTE 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_e_return_code    TYPE SYSUBRC
,
ld_et_message    TYPE BAPIRETTAB
,
ld_et_data    TYPE DATA
,
ld_et_param_out    TYPE IF_GRFN_CCI_PROXY=>T_SCRIPT_PARAM_OUT
.




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

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

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

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

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

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

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

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

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

CALL FUNCTION 'GRPC_API_SAPQUERY_EXECUTE'
  EXPORTING
    i_session_id =               ld_i_session_id
    i_connector =                ld_i_connector
*   i_queryname =                ld_i_queryname
*   i_usergroup =                ld_i_usergroup
*   i_queryarea =                ld_i_queryarea
*   i_variant =                  ld_i_variant
*   i_script =                   ld_i_script
    i_maxrows =                  ld_i_maxrows
    it_queryparams =             ld_it_queryparams
  IMPORTING
    e_return_code =              ld_e_return_code
    et_message =                 ld_et_message
    et_data =                    ld_et_data
    et_param_out =               ld_et_param_out
    .  "  GRPC_API_SAPQUERY_EXECUTE

IF SY-SUBRC EQ 0.
  "All OK
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_e_return_code  TYPE SYSUBRC ,
ld_i_session_id  TYPE GRPC_API_SESSION_ID ,
ld_et_message  TYPE BAPIRETTAB ,
ld_i_connector  TYPE STRING ,
ld_et_data  TYPE DATA ,
ld_i_queryname  TYPE GRFN_SQNAME ,
ld_et_param_out  TYPE IF_GRFN_CCI_PROXY=>T_SCRIPT_PARAM_OUT ,
ld_i_usergroup  TYPE GRFN_SQUSERGROUP ,
ld_i_queryarea  TYPE GRFN_SQWORKSPACE ,
ld_i_variant  TYPE GRFN_SQVARIANT ,
ld_i_script  TYPE STRING ,
ld_i_maxrows  TYPE INT4 ,
ld_it_queryparams  TYPE GRPC_T_QUERY_PARAM_VALUE .




ld_i_session_id = 'Check type of data required'.
ld_i_connector = 'Check type of data required'.
ld_i_queryname = 'Check type of data required'.
ld_i_usergroup = 'Check type of data required'.
ld_i_queryarea = 'Check type of data required'.
ld_i_variant = 'Check type of data required'.
ld_i_script = 'Check type of data required'.
ld_i_maxrows = 'Check type of data required'.
ld_it_queryparams = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name GRPC_API_SAPQUERY_EXECUTE or its description.


   
 

GRPC_API_SAPQUERY_EXECUTE - Execute SAP Query Control
GRPC_API_RULE_UPDATE - Update Rules
GRPC_API_RULE_RETRIEVE - Get the single rule data
GRPC_API_RULE_QUERY - Get list of the rules
GRPC_API_RULE_DELETE - Delete Rules
GRPC_API_RULE_CREATE - Create Rules