GRPC_API_RULE_UPDATE SAP Function module - Update Rules

GRPC_API_RULE_UPDATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name GRPC_API_RULE_UPDATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: GRPC_API_RULE
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM GRPC_API_RULE_UPDATE - GRPC API RULE UPDATE

CALL FUNCTION 'GRPC_API_RULE_UPDATE' "Update Rules
* EXPORTING
*   i_session_id =              " grpc_api_session_id  GRPC unique session ID
*   i_rule_id =                 " grpc_api_object_id  Rule
*   i_ruleset_del_ind =         " string
*   is_api_rule =               " grpc_s_api_rule  Rule
*   i_regulation_id =           " grpc_api_object_id  GRPC ID of the individual object
*   it_api_ruleset =            " grpc_t_api_ruleset  Rule Parameter Table
*   it_api_rlcrval =            " grpc_t_api_rlcrval  Rule Criteria Value Table
  IMPORTING
    e_return_code =             " int4          Natural number
* TABLES
*   et_message =                " bapirettab    Table with BAPI Return Information
    .  "  GRPC_API_RULE_UPDATE

ABAP code example for Function Module GRPC_API_RULE_UPDATE

The ABAP code below is a full code listing to execute function module GRPC_API_RULE_UPDATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_return_code  
 
 TYPE INT4
,
it_et_message  
 
 TYPE STANDARD TABLE OF BAPIRETTAB,"TABLES PARAM
wa_et_message
 
 LIKE LINE OF it_et_message
.


DATA(ld_i_session_id) = 'Check type of data required'.

DATA(ld_i_rule_id) = 'Check type of data required'.

DATA(ld_i_ruleset_del_ind) = 'Check type of data required'.

DATA(ld_is_api_rule) = 'Check type of data required'.

DATA(ld_i_regulation_id) = 'Check type of data required'.

DATA(ld_it_api_ruleset) = 'Check type of data required'.

DATA(ld_it_api_rlcrval) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_et_message to it_et_message.
.

CALL FUNCTION 'GRPC_API_RULE_UPDATE'
* EXPORTING
*   i_session_id =               ld_i_session_id
*   i_rule_id =                  ld_i_rule_id
*   i_ruleset_del_ind =          ld_i_ruleset_del_ind
*   is_api_rule =                ld_is_api_rule
*   i_regulation_id =            ld_i_regulation_id
*   it_api_ruleset =             ld_it_api_ruleset
*   it_api_rlcrval =             ld_it_api_rlcrval
  IMPORTING
    e_return_code =              ld_e_return_code
* TABLES
*   et_message =                 it_et_message
    .  "  GRPC_API_RULE_UPDATE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_return_code
 
 TYPE INT4 ,
ld_i_session_id
 
 TYPE GRPC_API_SESSION_ID ,
it_et_message
 
 TYPE STANDARD TABLE OF BAPIRETTAB ,
wa_et_message
 
 LIKE LINE OF it_et_message,
ld_i_rule_id
 
 TYPE GRPC_API_OBJECT_ID ,
ld_i_ruleset_del_ind
 
 TYPE STRING ,
ld_is_api_rule
 
 TYPE GRPC_S_API_RULE ,
ld_i_regulation_id
 
 TYPE GRPC_API_OBJECT_ID ,
ld_it_api_ruleset
 
 TYPE GRPC_T_API_RULESET ,
ld_it_api_rlcrval
 
 TYPE GRPC_T_API_RLCRVAL .


ld_i_session_id = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_message to it_et_message.
ld_i_rule_id = 'Check type of data required'.
ld_i_ruleset_del_ind = 'Check type of data required'.
ld_is_api_rule = 'Check type of data required'.
ld_i_regulation_id = 'Check type of data required'.
ld_it_api_ruleset = 'Check type of data required'.
ld_it_api_rlcrval = 'Check type of data required'.