SAP RSDRI_CUBE_WRITE_PACKAGE_RFC Function Module for Write a Data Package to the Specified InfoCube (RFC)
RSDRI_CUBE_WRITE_PACKAGE_RFC is a standard rsdri cube write package rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Write a Data Package to the Specified InfoCube (RFC) 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 rsdri cube write package rfc FM, simply by entering the name RSDRI_CUBE_WRITE_PACKAGE_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDRI_DBA
Program Name: SAPLRSDRI_DBA
Main Program: SAPLRSDRI_DBA
Appliation area: B
Release date: 17-Mar-2008
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RSDRI_CUBE_WRITE_PACKAGE_RFC 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 'RSDRI_CUBE_WRITE_PACKAGE_RFC'"Write a Data Package to the Specified InfoCube (RFC).
EXPORTING
I_INFOCUBE = "InfoCube
* I_CURR_CONVERSION = RS_C_TRUE "Convert Currency Indicator into DB Format Yes/No
* I_RFCDATA_UC = "Unicode-Compatible Coding of Entry Data (Alternative to I_T_RFCDATA)
* I_DEBUG = RS_C_FALSE "Boolean
* I_DELTA = RS_C_FALSE "Write Delta for existing Cube content
* I_MDATA_CHECK = RS_C_FALSE "Error if No Master Data Exists
IMPORTING
E_REQUID = "Request ID Under Which the Data Was Inserted
E_RECORDS = "Number of Records Written
TABLES
* I_T_RFCDATA = "Data (Alternative to I_RFCDATA_UC)
* E_T_MSG = "Message Table for InfoCube Writes
EXCEPTIONS
INFOCUBE_NOT_FOUND = 1 ILLEGAL_INPUT = 2 ROLLBACK_ERROR = 3 GENERATION_ERROR = 4 DUPLICATE_RECORDS = 5 REQUEST_LOCKED = 6 NOT_TRANSACTIONAL = 7 X_MESSAGE = 8
IMPORTING Parameters details for RSDRI_CUBE_WRITE_PACKAGE_RFC
I_INFOCUBE - InfoCube
Data type: RSINFOCUBEOptional: No
Call by Reference: No ( called with pass by value option)
I_CURR_CONVERSION - Convert Currency Indicator into DB Format Yes/No
Data type: RS_BOOLDefault: RS_C_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RFCDATA_UC - Unicode-Compatible Coding of Entry Data (Alternative to I_T_RFCDATA)
Data type: XSTRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DEBUG - Boolean
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DELTA - Write Delta for existing Cube content
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MDATA_CHECK - Error if No Master Data Exists
Data type: RSDRI_MDATA_CHECKDefault: RS_C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSDRI_CUBE_WRITE_PACKAGE_RFC
E_REQUID - Request ID Under Which the Data Was Inserted
Data type: RSREQUNROptional: No
Call by Reference: No ( called with pass by value option)
E_RECORDS - Number of Records Written
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RSDRI_CUBE_WRITE_PACKAGE_RFC
I_T_RFCDATA - Data (Alternative to I_RFCDATA_UC)
Data type: RSDRI_T_RFCDATAOptional: Yes
Call by Reference: Yes
E_T_MSG - Message Table for InfoCube Writes
Data type: RSDRI_T_MSG_RFCOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INFOCUBE_NOT_FOUND - InfoCube does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_INPUT - Incorrect Input Parameter
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ROLLBACK_ERROR - Error Deleting Request from Cube
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GENERATION_ERROR - Error when generating program
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DUPLICATE_RECORDS - Duplicates When Writing in the Cube
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
REQUEST_LOCKED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_TRANSACTIONAL - No transactions can be written
Data type:Optional: No
Call by Reference: Yes
X_MESSAGE - Error from Called Routine
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSDRI_CUBE_WRITE_PACKAGE_RFC 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_requid | TYPE RSREQUNR, " | |||
| lv_i_infocube | TYPE RSINFOCUBE, " | |||
| lt_i_t_rfcdata | TYPE STANDARD TABLE OF RSDRI_T_RFCDATA, " | |||
| lv_infocube_not_found | TYPE RSDRI_T_RFCDATA, " | |||
| lt_e_t_msg | TYPE STANDARD TABLE OF RSDRI_T_MSG_RFC, " | |||
| lv_e_records | TYPE I, " | |||
| lv_illegal_input | TYPE I, " | |||
| lv_i_curr_conversion | TYPE RS_BOOL, " RS_C_TRUE | |||
| lv_i_rfcdata_uc | TYPE XSTRING, " | |||
| lv_rollback_error | TYPE XSTRING, " | |||
| lv_i_debug | TYPE RS_BOOL, " RS_C_FALSE | |||
| lv_generation_error | TYPE RS_BOOL, " | |||
| lv_i_delta | TYPE RS_BOOL, " RS_C_FALSE | |||
| lv_duplicate_records | TYPE RS_BOOL, " | |||
| lv_i_mdata_check | TYPE RSDRI_MDATA_CHECK, " RS_C_FALSE | |||
| lv_request_locked | TYPE RSDRI_MDATA_CHECK, " | |||
| lv_not_transactional | TYPE RSDRI_MDATA_CHECK, " | |||
| lv_x_message | TYPE RSDRI_MDATA_CHECK. " |
|   CALL FUNCTION 'RSDRI_CUBE_WRITE_PACKAGE_RFC' "Write a Data Package to the Specified InfoCube (RFC) |
| EXPORTING | ||
| I_INFOCUBE | = lv_i_infocube | |
| I_CURR_CONVERSION | = lv_i_curr_conversion | |
| I_RFCDATA_UC | = lv_i_rfcdata_uc | |
| I_DEBUG | = lv_i_debug | |
| I_DELTA | = lv_i_delta | |
| I_MDATA_CHECK | = lv_i_mdata_check | |
| IMPORTING | ||
| E_REQUID | = lv_e_requid | |
| E_RECORDS | = lv_e_records | |
| TABLES | ||
| I_T_RFCDATA | = lt_i_t_rfcdata | |
| E_T_MSG | = lt_e_t_msg | |
| EXCEPTIONS | ||
| INFOCUBE_NOT_FOUND = 1 | ||
| ILLEGAL_INPUT = 2 | ||
| ROLLBACK_ERROR = 3 | ||
| GENERATION_ERROR = 4 | ||
| DUPLICATE_RECORDS = 5 | ||
| REQUEST_LOCKED = 6 | ||
| NOT_TRANSACTIONAL = 7 | ||
| X_MESSAGE = 8 | ||
| . " RSDRI_CUBE_WRITE_PACKAGE_RFC | ||
ABAP code using 7.40 inline data declarations to call FM RSDRI_CUBE_WRITE_PACKAGE_RFC
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.| DATA(ld_i_curr_conversion) | = RS_C_TRUE. | |||
| DATA(ld_i_debug) | = RS_C_FALSE. | |||
| DATA(ld_i_delta) | = RS_C_FALSE. | |||
| DATA(ld_i_mdata_check) | = RS_C_FALSE. | |||
Search for further information about these or an SAP related objects