How To Fix RSM758 - Reconstruction canceled: InfoCubes & requests &

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 758

• Message text: Reconstruction canceled: InfoCubes & requests &

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSM758 - Reconstruction canceled: InfoCubes & requests & ?

  The SAP error message RSM758, which states "Reconstruction canceled: InfoCubes & requests &," typically occurs during the process of data reconstruction in SAP BW (Business Warehouse). This error can arise due to various reasons, and understanding the cause is essential for resolving the issue.
  Causes:
  
  Data Inconsistencies: There may be inconsistencies in the data stored in the InfoCubes, which can prevent successful reconstruction.
  Request Issues: The data requests being processed may have errors or may not be in a state that allows for reconstruction.
  Locking Issues: If the InfoCube is locked by another process or user, it can lead to cancellation of the reconstruction.
  Technical Errors: There may be technical issues such as system performance problems, memory issues, or database connectivity problems.
  Configuration Issues: Incorrect settings in the InfoCube or the data loading process can also lead to this error.
  
  Solutions:
  
  Check Data Consistency: Use transaction codes like RSA1 to check the consistency of the InfoCubes and the data requests. You can also use the RSMO transaction to monitor the status of data requests.
  Review Request Status: Check the status of the data requests associated with the InfoCube. Ensure that they are in a valid state and not canceled or failed.
  Release Locks: If the InfoCube is locked, identify the process or user that is holding the lock and release it if possible. You can use transaction SM12 to view and manage locks.
  Check System Performance: Monitor system performance and resource usage. If the system is under heavy load, consider scheduling the reconstruction during off-peak hours.
  Reconfigure Settings: Review the configuration settings for the InfoCube and the data loading process to ensure they are set up correctly.
  Re-run the Reconstruction: After addressing the underlying issues, attempt to re-run the reconstruction process.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), RSMO (Monitor Data Load), and SM12 (Display and Manage Locks).
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message. You can search the SAP Support Portal for updates or patches.
  Logs and Traces: Review logs and traces for more detailed error messages that can provide insights into the root cause of the issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation and support.