SAP GRPCRTA_DATA_DISPLAY Function Module for Display result
GRPCRTA_DATA_DISPLAY is a standard grpcrta data display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display result 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 data display FM, simply by entering the name GRPCRTA_DATA_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPCRTA_UI_COMMON
Program Name: SAPLGRPCRTA_UI_COMMON
Main Program: SAPLGRPCRTA_UI_COMMON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRPCRTA_DATA_DISPLAY 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_DATA_DISPLAY'"Display result.
EXPORTING
* I_PROGRAM = "Program/transaction in SQL trace analysis
IT_RULEVARIABLES = "Structure for Rule Variables
IT_TRANS = "PC 2.5 Rule Set
IT_DEFICIENCY = "Deficiency
* I_DETAIL_FORM = "Program/transaction in SQL trace analysis
* I_USER_FORM = "Program/transaction in SQL trace analysis
I_FROMDATE = "From date
I_TODATE = "To Date
I_FREQUENCY_TYPE = "Frequency type
I_CURRENCY_KEY = "Currency key
IS_COMPLIANCE = "Compliance Parameters
IS_HEADER = "Structure for XML Header Data
CHANGING
IT_DATA = "
IT_FIELDCAT = "Field catalog for ListViewer control
* IT_SORT = "ALV control: Table of sort criteria
IMPORTING Parameters details for GRPCRTA_DATA_DISPLAY
I_PROGRAM - Program/transaction in SQL trace analysis
Data type: PROGRAMOptional: Yes
Call by Reference: Yes
IT_RULEVARIABLES - Structure for Rule Variables
Data type: GRPCRTA_T_RULEVARIABLESOptional: No
Call by Reference: Yes
IT_TRANS - PC 2.5 Rule Set
Data type: GRPCRTA_T_TRANSOptional: No
Call by Reference: Yes
IT_DEFICIENCY - Deficiency
Data type: GRPCRTA_T_DEFDSOptional: No
Call by Reference: Yes
I_DETAIL_FORM - Program/transaction in SQL trace analysis
Data type: PROGRAMOptional: Yes
Call by Reference: Yes
I_USER_FORM - Program/transaction in SQL trace analysis
Data type: PROGRAMOptional: Yes
Call by Reference: Yes
I_FROMDATE - From date
Data type: GRPCRTA_FROMDATEOptional: No
Call by Reference: Yes
I_TODATE - To Date
Data type: GRPCRTA_TODATEOptional: No
Call by Reference: Yes
I_FREQUENCY_TYPE - Frequency type
Data type: GRPCRTA_FREQOptional: No
Call by Reference: Yes
I_CURRENCY_KEY - Currency key
Data type: WAERS_CURCOptional: No
Call by Reference: Yes
IS_COMPLIANCE - Compliance Parameters
Data type: GRPCRTA_S_COMPPAROptional: No
Call by Reference: Yes
IS_HEADER - Structure for XML Header Data
Data type: GRPCRTA_XML_HEADEROptional: No
Call by Reference: Yes
CHANGING Parameters details for GRPCRTA_DATA_DISPLAY
IT_DATA -
Data type: TABLEOptional: No
Call by Reference: Yes
IT_FIELDCAT - Field catalog for ListViewer control
Data type: LVC_T_FCATOptional: No
Call by Reference: Yes
IT_SORT - ALV control: Table of sort criteria
Data type: LVC_T_SORTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for GRPCRTA_DATA_DISPLAY 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_it_data | TYPE TABLE, " | |||
| lv_i_program | TYPE PROGRAM, " | |||
| lv_it_rulevariables | TYPE GRPCRTA_T_RULEVARIABLES, " | |||
| lv_it_trans | TYPE GRPCRTA_T_TRANS, " | |||
| lv_it_deficiency | TYPE GRPCRTA_T_DEFDS, " | |||
| lv_it_fieldcat | TYPE LVC_T_FCAT, " | |||
| lv_i_detail_form | TYPE PROGRAM, " | |||
| lv_it_sort | TYPE LVC_T_SORT, " | |||
| lv_i_user_form | TYPE PROGRAM, " | |||
| lv_i_fromdate | TYPE GRPCRTA_FROMDATE, " | |||
| lv_i_todate | TYPE GRPCRTA_TODATE, " | |||
| lv_i_frequency_type | TYPE GRPCRTA_FREQ, " | |||
| lv_i_currency_key | TYPE WAERS_CURC, " | |||
| lv_is_compliance | TYPE GRPCRTA_S_COMPPAR, " | |||
| lv_is_header | TYPE GRPCRTA_XML_HEADER. " |
|   CALL FUNCTION 'GRPCRTA_DATA_DISPLAY' "Display result |
| EXPORTING | ||
| I_PROGRAM | = lv_i_program | |
| IT_RULEVARIABLES | = lv_it_rulevariables | |
| IT_TRANS | = lv_it_trans | |
| IT_DEFICIENCY | = lv_it_deficiency | |
| I_DETAIL_FORM | = lv_i_detail_form | |
| I_USER_FORM | = lv_i_user_form | |
| I_FROMDATE | = lv_i_fromdate | |
| I_TODATE | = lv_i_todate | |
| I_FREQUENCY_TYPE | = lv_i_frequency_type | |
| I_CURRENCY_KEY | = lv_i_currency_key | |
| IS_COMPLIANCE | = lv_is_compliance | |
| IS_HEADER | = lv_is_header | |
| CHANGING | ||
| IT_DATA | = lv_it_data | |
| IT_FIELDCAT | = lv_it_fieldcat | |
| IT_SORT | = lv_it_sort | |
| . " GRPCRTA_DATA_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM GRPCRTA_DATA_DISPLAY
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