SAP GRPC_API_ROLE_QUERY Function Module for Obsolete: Load the roles for GRPC entity









GRPC_API_ROLE_QUERY is a standard grpc api role query SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Obsolete: Load the roles for GRPC entity 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 role query FM, simply by entering the name GRPC_API_ROLE_QUERY into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRPC_API_ENTITY_ROLE
Program Name: SAPLGRPC_API_ENTITY_ROLE
Main Program: SAPLGRPC_API_ENTITY_ROLE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function GRPC_API_ROLE_QUERY 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_ROLE_QUERY'"Obsolete: Load the roles for GRPC entity
  EXPORTING
*  I_SESSION_ID =  "GRPC unique session ID
*  I_ROLE =  "Role ID
*  I_TASK =  "Obsolete: Task ID
*  I_PERSON =  "Obsolete: Person ID
*  I_UNAME =  "User Name
*  I_PERS_TXT =  "Search pattern for the Query APIs
*  I_CASES = ABAP_FALSE "Load CASE processors

 IMPORTING
   E_RETURN_CODE =  "Natural number

TABLES
*  ET_ENTITY_ROLE =  "Roles of the orgunit
*  ET_MESSAGE =  "Table with BAPI Return Information

EXCEPTIONS
   CX_BAPI_EXCEPTION = 1
.



IMPORTING Parameters details for GRPC_API_ROLE_QUERY

I_SESSION_ID - GRPC unique session ID

Data type: GRPC_API_SESSION_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ROLE - Role ID

Data type: GRPC_ROLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TASK - Obsolete: Task ID

Data type: GRPC_TASK
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PERSON - Obsolete: Person ID

Data type: GRPC_PERSON_ID_NUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_UNAME - User Name

Data type: SYUNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PERS_TXT - Search pattern for the Query APIs

Data type: GRPC_API_SEARCH_PATTERN
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CASES - Load CASE processors

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for GRPC_API_ROLE_QUERY

E_RETURN_CODE - Natural number

Data type: INT4
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for GRPC_API_ROLE_QUERY

ET_ENTITY_ROLE - Roles of the orgunit

Data type: GRPC_T_API_ENTITY_ROLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ET_MESSAGE - Table with BAPI Return Information

Data type: BAPIRETTAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CX_BAPI_EXCEPTION - Exception Basis Class for BAPI Migration

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GRPC_API_ROLE_QUERY 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_entity_role  TYPE STANDARD TABLE OF GRPC_T_API_ENTITY_ROLE, "   
lv_cx_bapi_exception  TYPE GRPC_T_API_ENTITY_ROLE, "   
lv_i_role  TYPE GRPC_ROLE, "   
lt_et_message  TYPE STANDARD TABLE OF BAPIRETTAB, "   
lv_i_task  TYPE GRPC_TASK, "   
lv_i_person  TYPE GRPC_PERSON_ID_NUM, "   
lv_i_uname  TYPE SYUNAME, "   
lv_i_pers_txt  TYPE GRPC_API_SEARCH_PATTERN, "   
lv_i_cases  TYPE ABAP_BOOL. "   ABAP_FALSE

  CALL FUNCTION 'GRPC_API_ROLE_QUERY'  "Obsolete: Load the roles for GRPC entity
    EXPORTING
         I_SESSION_ID = lv_i_session_id
         I_ROLE = lv_i_role
         I_TASK = lv_i_task
         I_PERSON = lv_i_person
         I_UNAME = lv_i_uname
         I_PERS_TXT = lv_i_pers_txt
         I_CASES = lv_i_cases
    IMPORTING
         E_RETURN_CODE = lv_e_return_code
    TABLES
         ET_ENTITY_ROLE = lt_et_entity_role
         ET_MESSAGE = lt_et_message
    EXCEPTIONS
        CX_BAPI_EXCEPTION = 1
. " GRPC_API_ROLE_QUERY




ABAP code using 7.40 inline data declarations to call FM GRPC_API_ROLE_QUERY

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.

 
 
 
 
 
 
 
 
 
 
DATA(ld_i_cases) = ABAP_FALSE.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!