SAP G_REPORT_EXPORT_PARAMETER Function Module for Export of the Report Cluster Parameter into the MEMORY
G_REPORT_EXPORT_PARAMETER is a standard g report export parameter SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Export of the Report Cluster Parameter into the MEMORY 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 g report export parameter FM, simply by entering the name G_REPORT_EXPORT_PARAMETER into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRWC
Program Name: SAPLGRWC
Main Program:
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_REPORT_EXPORT_PARAMETER 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 'G_REPORT_EXPORT_PARAMETER'"Export of the Report Cluster Parameter into the MEMORY.
EXPORTING
* SENDER_JOB = "
SENDER_LIBRARY = "Library of the sender report.
SENDER_REPORT = "Name of the sender report.
SENDER_TABLE = "Table (database) of the sender report.
TABLE_COUNTER = "Field string with the counters of interface.
TABLE_POINTER = "Field string with the pointers of interface.
TABLES
COL_TAB = "Table of the sender column elements.
DIM_TAB = "Table of the dimensions of the sender.
GLO_TAB = "Table of the global of the sender.
ROW_TAB = "Table of the sender row elements.
SEL_TAB = "Table of the sneder selection elements.
SET_TAB = "
IMPORTING Parameters details for G_REPORT_EXPORT_PARAMETER
SENDER_JOB -
Data type: T803J-RGJNROptional: Yes
Call by Reference: No ( called with pass by value option)
SENDER_LIBRARY - Library of the sender report.
Data type: T801K-LIBOptional: No
Call by Reference: No ( called with pass by value option)
SENDER_REPORT - Name of the sender report.
Data type: T800T-RNAMEOptional: No
Call by Reference: No ( called with pass by value option)
SENDER_TABLE - Table (database) of the sender report.
Data type: RGSMH-TABLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLE_COUNTER - Field string with the counters of interface.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLE_POINTER - Field string with the pointers of interface.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for G_REPORT_EXPORT_PARAMETER
COL_TAB - Table of the sender column elements.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DIM_TAB - Table of the dimensions of the sender.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GLO_TAB - Table of the global of the sender.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ROW_TAB - Table of the sender row elements.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SEL_TAB - Table of the sneder selection elements.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SET_TAB -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_REPORT_EXPORT_PARAMETER 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_col_tab | TYPE STANDARD TABLE OF STRING, " | |||
| lv_sender_job | TYPE T803J-RGJNR, " | |||
| lt_dim_tab | TYPE STANDARD TABLE OF T803J, " | |||
| lv_sender_library | TYPE T801K-LIB, " | |||
| lt_glo_tab | TYPE STANDARD TABLE OF T801K, " | |||
| lv_sender_report | TYPE T800T-RNAME, " | |||
| lt_row_tab | TYPE STANDARD TABLE OF T800T, " | |||
| lv_sender_table | TYPE RGSMH-TABLE, " | |||
| lt_sel_tab | TYPE STANDARD TABLE OF RGSMH, " | |||
| lv_table_counter | TYPE RGSMH, " | |||
| lt_set_tab | TYPE STANDARD TABLE OF RGSMH, " | |||
| lv_table_pointer | TYPE RGSMH. " |
|   CALL FUNCTION 'G_REPORT_EXPORT_PARAMETER' "Export of the Report Cluster Parameter into the MEMORY |
| EXPORTING | ||
| SENDER_JOB | = lv_sender_job | |
| SENDER_LIBRARY | = lv_sender_library | |
| SENDER_REPORT | = lv_sender_report | |
| SENDER_TABLE | = lv_sender_table | |
| TABLE_COUNTER | = lv_table_counter | |
| TABLE_POINTER | = lv_table_pointer | |
| TABLES | ||
| COL_TAB | = lt_col_tab | |
| DIM_TAB | = lt_dim_tab | |
| GLO_TAB | = lt_glo_tab | |
| ROW_TAB | = lt_row_tab | |
| SEL_TAB | = lt_sel_tab | |
| SET_TAB | = lt_set_tab | |
| . " G_REPORT_EXPORT_PARAMETER | ||
ABAP code using 7.40 inline data declarations to call FM G_REPORT_EXPORT_PARAMETER
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 RGJNR FROM T803J INTO @DATA(ld_sender_job). | ||||
| "SELECT single LIB FROM T801K INTO @DATA(ld_sender_library). | ||||
| "SELECT single RNAME FROM T800T INTO @DATA(ld_sender_report). | ||||
| "SELECT single TABLE FROM RGSMH INTO @DATA(ld_sender_table). | ||||
Search for further information about these or an SAP related objects