SAP GRPC_API_PLANNER_AUTHORIZE Function Module for Check the core PC authorizations
GRPC_API_PLANNER_AUTHORIZE is a standard grpc api planner authorize 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 planner authorize FM, simply by entering the name GRPC_API_PLANNER_AUTHORIZE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_PLANNER
Program Name: SAPLGRPC_API_PLANNER
Main Program: SAPLGRPC_API_PLANNER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRPC_API_PLANNER_AUTHORIZE 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_PLANNER_AUTHORIZE'"Check the core PC authorizations.
EXPORTING
* I_SESSION_ID = "GRPC unique session ID
* I_ENTITY_ID = "GRPC ID of the entity
* I_GROUP_ID = "GUID in 'CHAR' Format in Uppercase
IMPORTING
E_CREATE_ALLOWED = "Create operation allowed
E_UPDATE_ALLOWED = "Update operation allowed
E_DELETE_ALLOWED = "Delete operation allowed
E_RETURN_CODE = "Natural number
TABLES
* ET_MESSAGE = "Table with BAPI Return Information
IMPORTING Parameters details for GRPC_API_PLANNER_AUTHORIZE
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_ENTITY_ID - GRPC ID of the entity
Data type: GRPC_API_ENTITY_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_GROUP_ID - GUID in 'CHAR' Format in Uppercase
Data type: GUID_32Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPC_API_PLANNER_AUTHORIZE
E_CREATE_ALLOWED - Create operation allowed
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
E_UPDATE_ALLOWED - Update operation allowed
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
E_DELETE_ALLOWED - Delete operation allowed
Data type: BOOLE_DOptional: 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)
TABLES Parameters details for GRPC_API_PLANNER_AUTHORIZE
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_PLANNER_AUTHORIZE 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_i_session_id | TYPE GRPC_API_SESSION_ID, " | |||
| lv_e_create_allowed | TYPE BOOLE_D, " | |||
| lv_i_entity_id | TYPE GRPC_API_ENTITY_ID, " | |||
| lv_e_update_allowed | TYPE BOOLE_D, " | |||
| lv_i_group_id | TYPE GUID_32, " | |||
| lv_e_delete_allowed | TYPE BOOLE_D, " | |||
| lv_e_return_code | TYPE INT4. " |
|   CALL FUNCTION 'GRPC_API_PLANNER_AUTHORIZE' "Check the core PC authorizations |
| EXPORTING | ||
| I_SESSION_ID | = lv_i_session_id | |
| I_ENTITY_ID | = lv_i_entity_id | |
| I_GROUP_ID | = lv_i_group_id | |
| IMPORTING | ||
| E_CREATE_ALLOWED | = lv_e_create_allowed | |
| E_UPDATE_ALLOWED | = lv_e_update_allowed | |
| E_DELETE_ALLOWED | = lv_e_delete_allowed | |
| E_RETURN_CODE | = lv_e_return_code | |
| TABLES | ||
| ET_MESSAGE | = lt_et_message | |
| . " GRPC_API_PLANNER_AUTHORIZE | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_API_PLANNER_AUTHORIZE
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