Do you have any question about this error?
Message type: E = Error
Message class: RSAU - Update rules
Message number: 346
Message text: InfoCubes to be updated: & Cube(s)
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
RSAU346
- InfoCubes to be updated: & Cube(s) ?The SAP error message RSAU346 indicates that certain InfoCubes need to be updated. This message typically arises in the context of SAP BW (Business Warehouse) when there are changes in the underlying data or when the InfoCubes are not in sync with the data source.
Cause:
- Data Source Changes: If there have been changes in the data source (like changes in the structure or data model), the InfoCubes may need to be updated to reflect these changes.
- Data Load Issues: If there are issues with data loading processes, such as failed data loads or incomplete data, the InfoCubes may not be updated correctly.
- Metadata Changes: Changes in the metadata of the InfoCubes or the underlying data sources can also trigger this message.
- Data Consistency: The system may detect inconsistencies between the data in the InfoCubes and the data in the source systems.
Solution:
- Update InfoCubes: You can manually trigger the update of the InfoCubes. This can be done through the Data Warehousing Workbench (transaction RSA1) by selecting the InfoCubes and executing the update process.
- Check Data Load Processes: Review the data load processes to ensure that they are running successfully. Check for any errors or warnings in the data load logs.
- Reprocess Data: If there are inconsistencies, you may need to reprocess the data. This can involve reloading the data from the source systems into the InfoCubes.
- Check for Metadata Changes: If there have been changes in the metadata, ensure that the InfoCubes are adjusted accordingly. This may involve modifying the InfoCube structure or reactivating the InfoCube.
- Use Transaction RSRV: You can use transaction RSRV to check for inconsistencies in the InfoCubes and perform necessary repairs.
- Consult Documentation: Review SAP documentation or notes related to the specific version of SAP BW you are using for any additional troubleshooting steps or known issues.
Related Information:
By following these steps, you should be able to resolve the RSAU346 error and ensure that your InfoCubes are updated correctly.
Get instant SAP help. Start your 7-day free trial now.
RSAU345
Update: Start of the user-defined data enhancement
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSAU344
The lock for master data/text table of characteristic & was deleted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSAU347
Start of update-rule processing for InfoProvider &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSAU348
End of update-rule processing for InfoProvider &
What causes this issue? The data to be updated was aggregated to &V2& data records when update rules for InfoProvider &V1& were proce...
Click on this link to search all SAP messages.