GRPC_API_QUERY_CATALOG_SEARCH SAP Function module - Read the List of Queries based on given input params

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

Associated Function Group: GRPC_QUERY_INTEGRATION
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM GRPC_API_QUERY_CATALOG_SEARCH - GRPC API QUERY CATALOG SEARCH

CALL FUNCTION 'GRPC_API_QUERY_CATALOG_SEARCH' "Read the List of Queries based on given input params
  EXPORTING
*   i_session_id =              " grpc_api_session_id  GRPC unique session ID
    i_systype =                 " grpc_systemtype  System Type
    i_connector =               " grpc_connector  Logical Destination (Specified in Function Call)
*   i_usergroup =               " aqadef-bgname  SAP Query (S): Name of a user group
*   i_query_name =              " grpc_qry_name  Query Name
*   i_workspace = SPACE         " aqadef-wsid   SAP Query (S): Work Area ID
*   i_generic_funcarea =        " aqadef-sgname  SAP Query (S): InfoSet
*   i_with_system_objects = SPACE  " aqadef-flag  SAP Query (S): Flag
  IMPORTING
    e_return_code =             " int4          Natural number
  TABLES
    et_grpc_query =             " grpc_t_query_list  GRPC Query List
    et_message =                " bapirettab    Table with BAPI Return Information
    .  "  GRPC_API_QUERY_CATALOG_SEARCH

ABAP code example for Function Module GRPC_API_QUERY_CATALOG_SEARCH

The ABAP code below is a full code listing to execute function module GRPC_API_QUERY_CATALOG_SEARCH 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 INT4
,
it_et_grpc_query  
 
 TYPE STANDARD TABLE OF GRPC_T_QUERY_LIST,"TABLES PARAM
wa_et_grpc_query
 
 LIKE LINE OF it_et_grpc_query
,
it_et_message  
 
 TYPE STANDARD TABLE OF BAPIRETTAB,"TABLES PARAM
wa_et_message
 
 LIKE LINE OF it_et_message
.


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

DATA(ld_i_systype) = 'some text here'.

DATA(ld_i_connector) = 'some text here'.


DATA(ld_i_usergroup) = some text here

DATA(ld_i_query_name) = 'some text here'.


DATA(ld_i_workspace) = some text here


DATA(ld_i_generic_funcarea) = some text here


DATA(ld_i_with_system_objects) = some text here
 

"populate fields of struture and append to itab
append wa_et_grpc_query to it_et_grpc_query.
 

"populate fields of struture and append to itab
append wa_et_message to it_et_message.
.

CALL FUNCTION 'GRPC_API_QUERY_CATALOG_SEARCH'
  EXPORTING
*   i_session_id =               ld_i_session_id
    i_systype =                  ld_i_systype
    i_connector =                ld_i_connector
*   i_usergroup =                ld_i_usergroup
*   i_query_name =               ld_i_query_name
*   i_workspace =                ld_i_workspace
*   i_generic_funcarea =         ld_i_generic_funcarea
*   i_with_system_objects =      ld_i_with_system_objects
  IMPORTING
    e_return_code =              ld_e_return_code
  TABLES
    et_grpc_query =              it_et_grpc_query
    et_message =                 it_et_message
    .  "  GRPC_API_QUERY_CATALOG_SEARCH

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 INT4 ,
ld_i_session_id
 
 TYPE GRPC_API_SESSION_ID ,
it_et_grpc_query
 
 TYPE STANDARD TABLE OF GRPC_T_QUERY_LIST ,
wa_et_grpc_query
 
 LIKE LINE OF it_et_grpc_query,
ld_i_systype
 
 TYPE GRPC_SYSTEMTYPE ,
it_et_message
 
 TYPE STANDARD TABLE OF BAPIRETTAB ,
wa_et_message
 
 LIKE LINE OF it_et_message,
ld_i_connector
 
 TYPE GRPC_CONNECTOR ,
ld_i_usergroup
 
 TYPE AQADEF-BGNAME ,
ld_i_query_name
 
 TYPE GRPC_QRY_NAME ,
ld_i_workspace
 
 TYPE AQADEF-WSID ,
ld_i_generic_funcarea
 
 TYPE AQADEF-SGNAME ,
ld_i_with_system_objects
 
 TYPE AQADEF-FLAG .


ld_i_session_id = 'some text here'. 

"populate fields of struture and append to itab
append wa_et_grpc_query to it_et_grpc_query.
ld_i_systype = 'some text here'. 

"populate fields of struture and append to itab
append wa_et_message to it_et_message.
ld_i_connector = 'some text here'.

ld_i_usergroup = some text here
ld_i_query_name = 'some text here'.

ld_i_workspace = some text here

ld_i_generic_funcarea = some text here

ld_i_with_system_objects = some text here