How To Fix RSM867 - InfoCube request ID & is already scheduled; No compression is possible

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 867

• Message text: InfoCube request ID & is already scheduled; No compression is possible

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 RSM867 - InfoCube request ID & is already scheduled; No compression is possible ?

  The SAP error message RSM867 indicates that a request for data loading or processing in an InfoCube is already scheduled, and therefore, no compression can be performed at that moment. This typically occurs in the context of SAP BW (Business Warehouse) when you are trying to compress data in an InfoCube while there is an active data load or another process that is locking the InfoCube.
  Cause:
  
  Active Data Load: A data load request is currently being processed for the InfoCube, which prevents compression.
  Locking Mechanism: SAP BW uses a locking mechanism to ensure data integrity during data loads. If a request is in process, the InfoCube is locked for other operations, including compression.
  Long-running Processes: Sometimes, data loads can take longer than expected, leading to delays in compression.
  
  Solution:
  
  
  Check Active Requests: Use transaction code RSA1 (Data Warehousing Workbench) to check if there are any active data load requests for the InfoCube. You can also use transaction SM37 to monitor background jobs and see if there are any jobs running that are related to the InfoCube.
  
  
  Wait for Completion: If there is an active data load, you may need to wait for it to complete before attempting to compress the InfoCube again.
  
  
  Cancel or Delete Stuck Requests: If you find that a request is stuck or taking too long, you may consider canceling or deleting it. Be cautious with this approach, as it may lead to data inconsistencies if not handled properly.
  
  
  Schedule Compression: Once the active request has completed, you can manually trigger the compression process again. This can be done through transaction RSA1 or by using the appropriate background job.
  
  
  Review Process Chains: If you are using process chains for data loading and compression, ensure that the sequence of tasks is correctly set up to avoid conflicts.
  
  
  Related Information:
  
  Compression in SAP BW: Compression is a process that reduces the size of the data stored in an InfoCube by aggregating and summarizing data. It is important for performance and storage efficiency.
  Monitoring Tools: Utilize monitoring tools like ST22 (Dump Analysis) and SM21 (System Log) to check for any system issues that might be affecting data loads or compression.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  
  By following these steps, you should be able to resolve the RSM867 error and successfully compress your InfoCube.