SAP GRPC_API_OBJECT_INFO Function Module for Check the core PC authorizations
GRPC_API_OBJECT_INFO is a standard grpc api object info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check the core PC authorizations 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 object info FM, simply by entering the name GRPC_API_OBJECT_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_SERVICES
Program Name: SAPLGRPC_API_SERVICES
Main Program: SAPLGRPC_API_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRPC_API_OBJECT_INFO 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_OBJECT_INFO'"Check the core PC authorizations.
EXPORTING
* I_SESSION_ID = "GRPC unique session ID
* I_OBJECT_ID = "GRPC ID of the individual object
* I_ORGUNIT_ID = "GRPC ID of the individual object
* I_REGULATION_ID = "GRPC ID of the individual object
IMPORTING
E_ENTITY_ID = "GRPC ID of the entity
E_CENTRAL_ID = "Central ID
E_LOCAL_ID = "Local ID
E_RESP_PERS = "Owner ID
E_RESP_UNAME = "Owner ID
E_RETURN_CODE = "Natural number
E_ENTITY_TXT = "Description of the entity
E_OBJECT_ID = "Description of the entity
E_OBJECT_TXT = "Description of the entity
E_OBJECT_DESC = "Description
E_ORGUNIT_ID = "GRPC ID of the individual object
E_ORGUNIT_TXT = "Description of the entity
E_PARENT_ID = "GRPC ID of the individual object
E_PARENT_TXT = "Description of the entity
TABLES
* ET_MESSAGE = "Table with BAPI Return Information
IMPORTING Parameters details for GRPC_API_OBJECT_INFO
I_SESSION_ID - GRPC unique session ID
Data type: GRPC_API_SESSION_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJECT_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ORGUNIT_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REGULATION_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPC_API_OBJECT_INFO
E_ENTITY_ID - GRPC ID of the entity
Data type: GRPC_API_ENTITY_IDOptional: No
Call by Reference: No ( called with pass by value option)
E_CENTRAL_ID - Central ID
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
E_LOCAL_ID - Local ID
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
E_RESP_PERS - Owner ID
Data type: GRPC_REP_RESP_PERS_IDOptional: No
Call by Reference: No ( called with pass by value option)
E_RESP_UNAME - Owner ID
Data type: GRPC_REP_RESP_UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
E_RETURN_CODE - Natural number
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
E_ENTITY_TXT - Description of the entity
Data type: GRPC_API_OBJECT_DESCROptional: No
Call by Reference: No ( called with pass by value option)
E_OBJECT_ID - Description of the entity
Data type: GRPC_API_OBJECT_DESCROptional: No
Call by Reference: No ( called with pass by value option)
E_OBJECT_TXT - Description of the entity
Data type: GRPC_API_OBJECT_DESCROptional: No
Call by Reference: No ( called with pass by value option)
E_OBJECT_DESC - Description
Data type: GRPC_LONG_TEXTOptional: No
Call by Reference: No ( called with pass by value option)
E_ORGUNIT_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
E_ORGUNIT_TXT - Description of the entity
Data type: GRPC_API_OBJECT_DESCROptional: No
Call by Reference: No ( called with pass by value option)
E_PARENT_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
E_PARENT_TXT - Description of the entity
Data type: GRPC_API_OBJECT_DESCROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GRPC_API_OBJECT_INFO
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRPC_API_OBJECT_INFO 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: | ||||
| lt_et_message | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_e_entity_id | TYPE GRPC_API_ENTITY_ID, " | |||
| lv_i_session_id | TYPE GRPC_API_SESSION_ID, " | |||
| lv_e_central_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lv_e_local_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lv_e_resp_pers | TYPE GRPC_REP_RESP_PERS_ID, " | |||
| lv_e_resp_uname | TYPE GRPC_REP_RESP_UNAME, " | |||
| lv_e_return_code | TYPE INT4, " | |||
| lv_i_object_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lv_e_entity_txt | TYPE GRPC_API_OBJECT_DESCR, " | |||
| lv_e_object_id | TYPE GRPC_API_OBJECT_DESCR, " | |||
| lv_i_orgunit_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lv_e_object_txt | TYPE GRPC_API_OBJECT_DESCR, " | |||
| lv_i_regulation_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lv_e_object_desc | TYPE GRPC_LONG_TEXT, " | |||
| lv_e_orgunit_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lv_e_orgunit_txt | TYPE GRPC_API_OBJECT_DESCR, " | |||
| lv_e_parent_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lv_e_parent_txt | TYPE GRPC_API_OBJECT_DESCR. " |
|   CALL FUNCTION 'GRPC_API_OBJECT_INFO' "Check the core PC authorizations |
| EXPORTING | ||
| I_SESSION_ID | = lv_i_session_id | |
| I_OBJECT_ID | = lv_i_object_id | |
| I_ORGUNIT_ID | = lv_i_orgunit_id | |
| I_REGULATION_ID | = lv_i_regulation_id | |
| IMPORTING | ||
| E_ENTITY_ID | = lv_e_entity_id | |
| E_CENTRAL_ID | = lv_e_central_id | |
| E_LOCAL_ID | = lv_e_local_id | |
| E_RESP_PERS | = lv_e_resp_pers | |
| E_RESP_UNAME | = lv_e_resp_uname | |
| E_RETURN_CODE | = lv_e_return_code | |
| E_ENTITY_TXT | = lv_e_entity_txt | |
| E_OBJECT_ID | = lv_e_object_id | |
| E_OBJECT_TXT | = lv_e_object_txt | |
| E_OBJECT_DESC | = lv_e_object_desc | |
| E_ORGUNIT_ID | = lv_e_orgunit_id | |
| E_ORGUNIT_TXT | = lv_e_orgunit_txt | |
| E_PARENT_ID | = lv_e_parent_id | |
| E_PARENT_TXT | = lv_e_parent_txt | |
| TABLES | ||
| ET_MESSAGE | = lt_et_message | |
| . " GRPC_API_OBJECT_INFO | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_API_OBJECT_INFO
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