SAP GRPC_API_SEL_PRC_OBJ_INFO Function Module for Get object information
GRPC_API_SEL_PRC_OBJ_INFO is a standard grpc api sel prc obj 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 Get object information 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 sel prc obj info FM, simply by entering the name GRPC_API_SEL_PRC_OBJ_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_SEL_PRC
Program Name: SAPLGRPC_API_SEL_PRC
Main Program: SAPLGRPC_API_SEL_PRC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRPC_API_SEL_PRC_OBJ_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_SEL_PRC_OBJ_INFO'"Get object information.
EXPORTING
IV_OBJECT_ID = "Object ID
IV_SESSION_ID = "GRPC unique session ID
IV_REGULATION_ID = "Object ID
IV_PLAN_ACTIVITY = "Plan Activity
IMPORTING
ES_OBJ_INFO = "Selection procedure object
EV_SCOPE = "Single-Character Flag
EV_CONTROLTYPE = "Description of the entity
E_RETURN_CODE = "Natural number
TABLES
* ET_MESSAGE = "Table with BAPI Return Information
IMPORTING Parameters details for GRPC_API_SEL_PRC_OBJ_INFO
IV_OBJECT_ID - Object ID
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: Yes
IV_SESSION_ID - GRPC unique session ID
Data type: GRPC_API_SESSION_IDOptional: No
Call by Reference: Yes
IV_REGULATION_ID - Object ID
Data type: GRFN_API_OBJECT_IDOptional: No
Call by Reference: Yes
IV_PLAN_ACTIVITY - Plan Activity
Data type: GRPC_PLAN_ACTIVITYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for GRPC_API_SEL_PRC_OBJ_INFO
ES_OBJ_INFO - Selection procedure object
Data type: GRPC_S_API_SELPRC_OBJECTSOptional: No
Call by Reference: Yes
EV_SCOPE - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
EV_CONTROLTYPE - Description of the entity
Data type: GRPC_API_OBJECT_DESCROptional: No
Call by Reference: Yes
E_RETURN_CODE - Natural number
Data type: INT4Optional: No
Call by Reference: Yes
TABLES Parameters details for GRPC_API_SEL_PRC_OBJ_INFO
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for GRPC_API_SEL_PRC_OBJ_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_es_obj_info | TYPE GRPC_S_API_SELPRC_OBJECTS, " | |||
| lv_iv_object_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lv_ev_scope | TYPE CHAR1, " | |||
| lv_iv_session_id | TYPE GRPC_API_SESSION_ID, " | |||
| lv_ev_controltype | TYPE GRPC_API_OBJECT_DESCR, " | |||
| lv_iv_regulation_id | TYPE GRFN_API_OBJECT_ID, " | |||
| lv_e_return_code | TYPE INT4, " | |||
| lv_iv_plan_activity | TYPE GRPC_PLAN_ACTIVITY. " |
|   CALL FUNCTION 'GRPC_API_SEL_PRC_OBJ_INFO' "Get object information |
| EXPORTING | ||
| IV_OBJECT_ID | = lv_iv_object_id | |
| IV_SESSION_ID | = lv_iv_session_id | |
| IV_REGULATION_ID | = lv_iv_regulation_id | |
| IV_PLAN_ACTIVITY | = lv_iv_plan_activity | |
| IMPORTING | ||
| ES_OBJ_INFO | = lv_es_obj_info | |
| EV_SCOPE | = lv_ev_scope | |
| EV_CONTROLTYPE | = lv_ev_controltype | |
| E_RETURN_CODE | = lv_e_return_code | |
| TABLES | ||
| ET_MESSAGE | = lt_et_message | |
| . " GRPC_API_SEL_PRC_OBJ_INFO | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_API_SEL_PRC_OBJ_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