SAP GRPCRTA_PC_GET_REPORT_RULEIDS Function Module for Get Rules from front end









GRPCRTA_PC_GET_REPORT_RULEIDS is a standard grpcrta pc get report ruleids 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 Rules from front end 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 grpcrta pc get report ruleids FM, simply by entering the name GRPCRTA_PC_GET_REPORT_RULEIDS into the relevant SAP transaction such as SE37 or SE38.

Function Group: GRPCRTA_ECM
Program Name: SAPLGRPCRTA_ECM
Main Program: SAPLGRPCRTA_ECM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function GRPCRTA_PC_GET_REPORT_RULEIDS 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 'GRPCRTA_PC_GET_REPORT_RULEIDS'"Get Rules from front end
  EXPORTING
   I_CONTROL_ID =  "Object ID
   I_RULEID =  "Rule ID
   I_ORGUNITID =  "Object ID
   I_RFCDEST =  "Logical destination (specified in function call)
   I_TIMEFRAME =  "Time Frame
   I_TF_YEAR =  "Time fram year
   I_CONNECTOR =  "Logical Destination (Specified in Function Call)

 IMPORTING
   E_PERIODTYPE =  "Frequency type
   E_PERIOD =  "Period
   E_PERIODYEAR =  "Period Year
   E_PERIOD_DATE =  "Date and time, current (application server) date
   E_FROMDATE =  "Date and time, current (application server) date
   E_TODATE =  "Date and time, current (application server) date
   ES_COMPLIANCE =  "Compliance Parameters
   ES_RETURN =  "Return parameter

TABLES
*  ET_GLOBAL_VALUES =  "Structure for Global variables
*  ET_RULE_VARVALUES =  "Structure for Rule Variables
*  ET_RULE_SCHEMAS =  "Rules Analysis
*  ET_DEFICIENCY =  "Deficiency Type Description
*  ET_SCHEMA_ORDER =  "Schema order structure

EXCEPTIONS
   UNKNOWN_ERROR = 1    RULE_NOT_FOUND = 2    NO_RUNTIME_INFO = 3
.



IMPORTING Parameters details for GRPCRTA_PC_GET_REPORT_RULEIDS

I_CONTROL_ID - Object ID

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

I_RULEID - Rule ID

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

I_ORGUNITID - Object ID

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

I_RFCDEST - Logical destination (specified in function call)

Data type: RFCDES-RFCDEST
Optional: No
Call by Reference: No ( called with pass by value option)

I_TIMEFRAME - Time Frame

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

I_TF_YEAR - Time fram year

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

I_CONNECTOR - Logical Destination (Specified in Function Call)

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

EXPORTING Parameters details for GRPCRTA_PC_GET_REPORT_RULEIDS

E_PERIODTYPE - Frequency type

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

E_PERIOD - Period

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

E_PERIODYEAR - Period Year

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

E_PERIOD_DATE - Date and time, current (application server) date

Data type: SY-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

E_FROMDATE - Date and time, current (application server) date

Data type: SY-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

E_TODATE - Date and time, current (application server) date

Data type: SY-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

ES_COMPLIANCE - Compliance Parameters

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

ES_RETURN - Return parameter

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

TABLES Parameters details for GRPCRTA_PC_GET_REPORT_RULEIDS

ET_GLOBAL_VALUES - Structure for Global variables

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

ET_RULE_VARVALUES - Structure for Rule Variables

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

ET_RULE_SCHEMAS - Rules Analysis

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

ET_DEFICIENCY - Deficiency Type Description

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

ET_SCHEMA_ORDER - Schema order structure

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

EXCEPTIONS details

UNKNOWN_ERROR - Unknown error occured

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

RULE_NOT_FOUND - Rule not found

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

NO_RUNTIME_INFO - Job name not found

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

Copy and paste ABAP code example for GRPCRTA_PC_GET_REPORT_RULEIDS 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_e_periodtype  TYPE GRPCRTA_FREQ, "   
lv_i_control_id  TYPE GRPCRTA_CONTROL_ID, "   
lv_unknown_error  TYPE GRPCRTA_CONTROL_ID, "   
lt_et_global_values  TYPE STANDARD TABLE OF GRPCRTA_S_GLOBALVARIABLES, "   
lv_e_period  TYPE GRPCRTA_PERIOD, "   
lv_i_ruleid  TYPE GRPCRTA_RULEID_2, "   
lv_rule_not_found  TYPE GRPCRTA_RULEID_2, "   
lt_et_rule_varvalues  TYPE STANDARD TABLE OF GRPCRTA_S_RULEVARIABLES, "   
lv_i_orgunitid  TYPE GRPCRTA_ORGUNIT_ID, "   
lv_e_periodyear  TYPE GRPCRTA_YEAR, "   
lt_et_rule_schemas  TYPE STANDARD TABLE OF GRPCRTA_TRANS, "   
lv_no_runtime_info  TYPE GRPCRTA_TRANS, "   
lv_i_rfcdest  TYPE RFCDES-RFCDEST, "   
lt_et_deficiency  TYPE STANDARD TABLE OF GRPCRTA_S_DEFDS, "   
lv_e_period_date  TYPE SY-DATUM, "   
lv_e_fromdate  TYPE SY-DATUM, "   
lv_i_timeframe  TYPE GRPCRTA_TIMEFRAME_1, "   
lt_et_schema_order  TYPE STANDARD TABLE OF GRPCRTA_S_SCHEMAORDER, "   
lv_e_todate  TYPE SY-DATUM, "   
lv_i_tf_year  TYPE GRPCRTA_GRCP_TF_YEAR, "   
lv_i_connector  TYPE RFCDEST, "   
lv_es_compliance  TYPE GRPCRTA_S_COMPPAR, "   
lv_es_return  TYPE BAPIRETURN1. "   

  CALL FUNCTION 'GRPCRTA_PC_GET_REPORT_RULEIDS'  "Get Rules from front end
    EXPORTING
         I_CONTROL_ID = lv_i_control_id
         I_RULEID = lv_i_ruleid
         I_ORGUNITID = lv_i_orgunitid
         I_RFCDEST = lv_i_rfcdest
         I_TIMEFRAME = lv_i_timeframe
         I_TF_YEAR = lv_i_tf_year
         I_CONNECTOR = lv_i_connector
    IMPORTING
         E_PERIODTYPE = lv_e_periodtype
         E_PERIOD = lv_e_period
         E_PERIODYEAR = lv_e_periodyear
         E_PERIOD_DATE = lv_e_period_date
         E_FROMDATE = lv_e_fromdate
         E_TODATE = lv_e_todate
         ES_COMPLIANCE = lv_es_compliance
         ES_RETURN = lv_es_return
    TABLES
         ET_GLOBAL_VALUES = lt_et_global_values
         ET_RULE_VARVALUES = lt_et_rule_varvalues
         ET_RULE_SCHEMAS = lt_et_rule_schemas
         ET_DEFICIENCY = lt_et_deficiency
         ET_SCHEMA_ORDER = lt_et_schema_order
    EXCEPTIONS
        UNKNOWN_ERROR = 1
        RULE_NOT_FOUND = 2
        NO_RUNTIME_INFO = 3
. " GRPCRTA_PC_GET_REPORT_RULEIDS




ABAP code using 7.40 inline data declarations to call FM GRPCRTA_PC_GET_REPORT_RULEIDS

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.

 
 
 
 
 
 
 
 
 
 
 
 
"SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_i_rfcdest).
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_e_period_date).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_e_fromdate).
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_e_todate).
 
 
 
 
 


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!