SAP RSZ_I_COPY_QRY_TO_CUBE Function Module for Returns a Selection of Queries and Copies to New IC
RSZ_I_COPY_QRY_TO_CUBE is a standard rsz i copy qry to cube SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns a Selection of Queries and Copies to New IC 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 rsz i copy qry to cube FM, simply by entering the name RSZ_I_COPY_QRY_TO_CUBE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RZIMPACT
Program Name: SAPLRZIMPACT
Main Program: SAPLRZIMPACT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSZ_I_COPY_QRY_TO_CUBE 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 'RSZ_I_COPY_QRY_TO_CUBE'"Returns a Selection of Queries and Copies to New IC.
EXPORTING
I_SOURCE_INFOCUBE = "Source InfoProvider
I_TARGET_INFOCUBE = "Target InfoProvider
* I_DEFTP = "Type of Component
* I_COPY_REPDIR = "Copy properties from RSRREPDIR
* I_T_COMP_RENAME = "Table of New Technical Names
* I_T_IOBJ_MAPPING = "Table of InfoObjects Mapping
IMPORTING
E_T_MSG = "BW: Table with Messages (Application Log)
EXCEPTIONS
CANCELED = 1 INHERITED_ERROR = 2 INFOCUBE_NOT_FOUND = 3 NOTHING_SELECTED = 4 NO_AUTHORIZATION = 5 INFOCUBE_NOT_COMPLIANT = 6 INCORRECT_INPUT = 7
IMPORTING Parameters details for RSZ_I_COPY_QRY_TO_CUBE
I_SOURCE_INFOCUBE - Source InfoProvider
Data type: RSD_INFOCUBEOptional: No
Call by Reference: Yes
I_TARGET_INFOCUBE - Target InfoProvider
Data type: RSD_INFOCUBEOptional: No
Call by Reference: Yes
I_DEFTP - Type of Component
Data type: RZD1_DEFTPOptional: Yes
Call by Reference: Yes
I_COPY_REPDIR - Copy properties from RSRREPDIR
Data type: RS_BOOLOptional: Yes
Call by Reference: Yes
I_T_COMP_RENAME - Table of New Technical Names
Data type: RZD1_T_COMP_RENAMEOptional: Yes
Call by Reference: Yes
I_T_IOBJ_MAPPING - Table of InfoObjects Mapping
Data type: RZD1_T_IOBJ_MAPPINGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSZ_I_COPY_QRY_TO_CUBE
E_T_MSG - BW: Table with Messages (Application Log)
Data type: RS_T_MSGOptional: No
Call by Reference: Yes
EXCEPTIONS details
CANCELED -
Data type:Optional: No
Call by Reference: Yes
INHERITED_ERROR -
Data type:Optional: No
Call by Reference: Yes
INFOCUBE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
NOTHING_SELECTED -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: Yes
INFOCUBE_NOT_COMPLIANT -
Data type:Optional: No
Call by Reference: Yes
INCORRECT_INPUT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSZ_I_COPY_QRY_TO_CUBE 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_t_msg | TYPE RS_T_MSG, " | |||
| lv_canceled | TYPE RS_T_MSG, " | |||
| lv_i_source_infocube | TYPE RSD_INFOCUBE, " | |||
| lv_inherited_error | TYPE RSD_INFOCUBE, " | |||
| lv_i_target_infocube | TYPE RSD_INFOCUBE, " | |||
| lv_i_deftp | TYPE RZD1_DEFTP, " | |||
| lv_infocube_not_found | TYPE RZD1_DEFTP, " | |||
| lv_i_copy_repdir | TYPE RS_BOOL, " | |||
| lv_nothing_selected | TYPE RS_BOOL, " | |||
| lv_i_t_comp_rename | TYPE RZD1_T_COMP_RENAME, " | |||
| lv_no_authorization | TYPE RZD1_T_COMP_RENAME, " | |||
| lv_i_t_iobj_mapping | TYPE RZD1_T_IOBJ_MAPPING, " | |||
| lv_infocube_not_compliant | TYPE RZD1_T_IOBJ_MAPPING, " | |||
| lv_incorrect_input | TYPE RZD1_T_IOBJ_MAPPING. " |
|   CALL FUNCTION 'RSZ_I_COPY_QRY_TO_CUBE' "Returns a Selection of Queries and Copies to New IC |
| EXPORTING | ||
| I_SOURCE_INFOCUBE | = lv_i_source_infocube | |
| I_TARGET_INFOCUBE | = lv_i_target_infocube | |
| I_DEFTP | = lv_i_deftp | |
| I_COPY_REPDIR | = lv_i_copy_repdir | |
| I_T_COMP_RENAME | = lv_i_t_comp_rename | |
| I_T_IOBJ_MAPPING | = lv_i_t_iobj_mapping | |
| IMPORTING | ||
| E_T_MSG | = lv_e_t_msg | |
| EXCEPTIONS | ||
| CANCELED = 1 | ||
| INHERITED_ERROR = 2 | ||
| INFOCUBE_NOT_FOUND = 3 | ||
| NOTHING_SELECTED = 4 | ||
| NO_AUTHORIZATION = 5 | ||
| INFOCUBE_NOT_COMPLIANT = 6 | ||
| INCORRECT_INPUT = 7 | ||
| . " RSZ_I_COPY_QRY_TO_CUBE | ||
ABAP code using 7.40 inline data declarations to call FM RSZ_I_COPY_QRY_TO_CUBE
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