SAP GRPC_API_RULE_CONTROLS Function Module for get controls by rule
GRPC_API_RULE_CONTROLS is a standard grpc api rule controls 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 controls by rule 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 rule controls FM, simply by entering the name GRPC_API_RULE_CONTROLS into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_API_RULE
Program Name: SAPLGRPC_API_RULE
Main Program: SAPLGRPC_API_RULE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GRPC_API_RULE_CONTROLS 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_RULE_CONTROLS'"get controls by rule.
EXPORTING
* I_SESSION_ID = "GRPC unique session ID
I_RULE_ID = "GRPC ID of the individual object
I_REGULATION_ID = "Object ID
IMPORTING
E_RETURN_CODE = "Natural number
TABLES
* ET_CONTROL_LIST = "Table type of control list
* ET_MESSAGE = "Table with BAPI Return Information
IMPORTING Parameters details for GRPC_API_RULE_CONTROLS
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_RULE_ID - GRPC ID of the individual object
Data type: GRPC_API_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_REGULATION_ID - Object ID
Data type: GRFN_API_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPC_API_RULE_CONTROLS
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_RULE_CONTROLS
ET_CONTROL_LIST - Table type of control list
Data type: GRPC_T_API_CONTROL_LISTOptional: Yes
Call by Reference: Yes
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for GRPC_API_RULE_CONTROLS 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_control_list | TYPE STANDARD TABLE OF GRPC_T_API_CONTROL_LIST, " | |||
| lv_i_rule_id | TYPE GRPC_API_OBJECT_ID, " | |||
| lt_et_message | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_i_regulation_id | TYPE GRFN_API_OBJECT_ID. " |
|   CALL FUNCTION 'GRPC_API_RULE_CONTROLS' "get controls by rule |
| EXPORTING | ||
| I_SESSION_ID | = lv_i_session_id | |
| I_RULE_ID | = lv_i_rule_id | |
| I_REGULATION_ID | = lv_i_regulation_id | |
| IMPORTING | ||
| E_RETURN_CODE | = lv_e_return_code | |
| TABLES | ||
| ET_CONTROL_LIST | = lt_et_control_list | |
| ET_MESSAGE | = lt_et_message | |
| . " GRPC_API_RULE_CONTROLS | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_API_RULE_CONTROLS
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