SAP GRPC_API_RLCR_QUERY Function Module for Get list of rule criteria









GRPC_API_RLCR_QUERY is a standard grpc api rlcr query 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 list of rule criteria 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 rlcr query FM, simply by entering the name GRPC_API_RLCR_QUERY into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRPC_API_RLCR
Program Name: SAPLGRPC_API_RLCR
Main Program: SAPLGRPC_API_RLCR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function GRPC_API_RLCR_QUERY 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_RLCR_QUERY'"Get list of rule criteria
  EXPORTING
*  I_SESSION_ID =  "GRPC unique session ID
*  I_SEARCH_PATTERN =  "Search pattern for the Query APIs
*  IV_RULEVAR =  "Rule Criteria
*  IV_RULEVAR_DESC =  "Rule Criteria Description
*  IV_ISORGUNIT =  "Organization Level System Parameter Indicator
*  I_REGULATION_ID =  "GRPC ID of the individual object

 IMPORTING
   E_RETURN_CODE =  "Natural number

TABLES
*  ET_RLCR_DATA_LIST =  "Rule Criteria Data Structure
*  ET_RLCRSYSA_LIST =  "Rule Criteria System Type Assignment Table
*  ET_MESSAGE =  "Table with BAPI Return Information
.



IMPORTING Parameters details for GRPC_API_RLCR_QUERY

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_SEARCH_PATTERN - Search pattern for the Query APIs

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

IV_RULEVAR - Rule Criteria

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

IV_RULEVAR_DESC - Rule Criteria Description

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

IV_ISORGUNIT - Organization Level System Parameter Indicator

Data type: GRPC_ISORGUNIT
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_RLCR_QUERY

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_RLCR_QUERY

ET_RLCR_DATA_LIST - Rule Criteria Data Structure

Data type: GRPC_T_API_RLCR_DATA
Optional: Yes
Call by Reference: Yes

ET_RLCRSYSA_LIST - Rule Criteria System Type Assignment Table

Data type: GRPC_T_API_RLCRSYSA
Optional: Yes
Call by Reference: Yes

ET_MESSAGE - Table with BAPI Return Information

Data type: BAPIRETTAB
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for GRPC_API_RLCR_QUERY 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_rlcr_data_list  TYPE STANDARD TABLE OF GRPC_T_API_RLCR_DATA, "   
lt_et_rlcrsysa_list  TYPE STANDARD TABLE OF GRPC_T_API_RLCRSYSA, "   
lv_i_search_pattern  TYPE GRPC_API_SEARCH_PATTERN, "   
lt_et_message  TYPE STANDARD TABLE OF BAPIRETTAB, "   
lv_iv_rulevar  TYPE GRPC_RULEVAR, "   
lv_iv_rulevar_desc  TYPE GRPC_RULEVAR_DESC, "   
lv_iv_isorgunit  TYPE GRPC_ISORGUNIT, "   
lv_i_regulation_id  TYPE GRPC_API_OBJECT_ID. "   

  CALL FUNCTION 'GRPC_API_RLCR_QUERY'  "Get list of rule criteria
    EXPORTING
         I_SESSION_ID = lv_i_session_id
         I_SEARCH_PATTERN = lv_i_search_pattern
         IV_RULEVAR = lv_iv_rulevar
         IV_RULEVAR_DESC = lv_iv_rulevar_desc
         IV_ISORGUNIT = lv_iv_isorgunit
         I_REGULATION_ID = lv_i_regulation_id
    IMPORTING
         E_RETURN_CODE = lv_e_return_code
    TABLES
         ET_RLCR_DATA_LIST = lt_et_rlcr_data_list
         ET_RLCRSYSA_LIST = lt_et_rlcrsysa_list
         ET_MESSAGE = lt_et_message
. " GRPC_API_RLCR_QUERY




ABAP code using 7.40 inline data declarations to call FM GRPC_API_RLCR_QUERY

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!