SAP GRPC_API_RULE_CREATE Function Module for Create Rules









GRPC_API_RULE_CREATE is a standard grpc api rule create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Rules 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 create FM, simply by entering the name GRPC_API_RULE_CREATE 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_CREATE 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_CREATE'"Create Rules
  EXPORTING
*  I_SESSION_ID =  "GRPC unique session ID
*  I_RULE_ID =  "Rule ID
*  IV_AUTO_GENERATE_RULE =  "Supplement for True Boolean Type: 'X' == True '' == False
*  IS_API_RULE =  "API Rule ID
*  IT_API_RULESET =  "Rule Parameter Table
*  IT_API_RLCRVAL =  "Rule Criteria Value Table
*  I_REGULATION_ID =  "GRPC ID of the individual object

 IMPORTING
   E_RETURN_CODE =  "Natural number

TABLES
*  ET_MESSAGE =  "Table with BAPI Return Information
.



IMPORTING Parameters details for GRPC_API_RULE_CREATE

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_RULE_ID - Rule ID

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

IV_AUTO_GENERATE_RULE - Supplement for True Boolean Type: 'X' == True '' == False

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

IS_API_RULE - API Rule ID

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

IT_API_RULESET - Rule Parameter Table

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

IT_API_RLCRVAL - Rule Criteria Value Table

Data type: GRPC_T_API_RLCRVAL
Optional: 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_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for GRPC_API_RULE_CREATE

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_RULE_CREATE

ET_MESSAGE - Table with BAPI Return Information

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

Copy and paste ABAP code example for GRPC_API_RULE_CREATE 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_return_code  TYPE INT4, "   
lv_i_rule_id  TYPE GRPC_API_OBJECT_ID, "   
lv_iv_auto_generate_rule  TYPE BOOLE_D, "   
lv_is_api_rule  TYPE GRPC_S_API_RULE, "   
lv_it_api_ruleset  TYPE GRPC_T_API_RULESET, "   
lv_it_api_rlcrval  TYPE GRPC_T_API_RLCRVAL, "   
lv_i_regulation_id  TYPE GRPC_API_OBJECT_ID. "   

  CALL FUNCTION 'GRPC_API_RULE_CREATE'  "Create Rules
    EXPORTING
         I_SESSION_ID = lv_i_session_id
         I_RULE_ID = lv_i_rule_id
         IV_AUTO_GENERATE_RULE = lv_iv_auto_generate_rule
         IS_API_RULE = lv_is_api_rule
         IT_API_RULESET = lv_it_api_ruleset
         IT_API_RLCRVAL = lv_it_api_rlcrval
         I_REGULATION_ID = lv_i_regulation_id
    IMPORTING
         E_RETURN_CODE = lv_e_return_code
    TABLES
         ET_MESSAGE = lt_et_message
. " GRPC_API_RULE_CREATE




ABAP code using 7.40 inline data declarations to call FM GRPC_API_RULE_CREATE

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



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!