Do you have any question about this error?
Message type: E = Error
Message class: RSM -
Message number: 849
Message text: New aggregation for aggregates in InfoCube & successfully completed
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.
RSM849
- New aggregation for aggregates in InfoCube & successfully completed ?The SAP error message RSM849 typically relates to issues encountered during the process of aggregating data in an InfoCube. This message indicates that there is a problem with the new aggregation process for the aggregates in the InfoCube, but it also states that the process has been completed successfully, which can be somewhat confusing.
Cause:
- Data Inconsistencies: There may be inconsistencies or issues with the data in the InfoCube that prevent the aggregation from being performed correctly.
- Configuration Issues: Incorrect settings or configurations in the InfoCube or the aggregates can lead to this error.
- Locks or Conflicts: If there are locks on the InfoCube or if other processes are accessing the data simultaneously, it can cause issues during aggregation.
- Performance Issues: If the system is under heavy load, it may not be able to complete the aggregation process efficiently.
Solution:
- Check Data Consistency: Use transaction codes like
RSA1
to check the InfoCube and ensure that the data is consistent. You can also run theRSMO
transaction to monitor the status of the aggregates.- Review Configuration: Verify the configuration settings for the InfoCube and the aggregates. Ensure that all settings are correct and that there are no discrepancies.
- Clear Locks: If there are locks on the InfoCube, you may need to wait for them to be released or manually clear them if necessary.
- Monitor System Performance: Check the system performance and ensure that it is not overloaded. You may need to schedule the aggregation process during off-peak hours.
- Rebuild Aggregates: If the issue persists, consider rebuilding the aggregates. This can be done through the
RSD1
transaction by selecting the InfoCube and choosing the option to rebuild aggregates.Related Information:
RSA1
: Data Warehousing WorkbenchRSD1
: InfoObject MaintenanceRSMO
: Monitor AggregatesIf the problem continues after trying these solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation and support.
Get instant SAP help. Start your 7-day free trial now.
RSM848
New aggregation for aggregate &(&) for InfoCube & started
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSM847
Incorrect start date: &1; Start time &2
What causes this issue? The start date of this job probably lies in the past.System Response The system issues an error message and will not allow y...
RSM850
* Workflow messages **************************************************
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSM851
Inconsistency in table & for request no. &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.