How To Fix RSDU_REPART679 - Compress all historical movement requests before converting to flat

RSDU_REPART679 - Overview

• Message type: E = Error

• Message class: RSDU_REPART - Messages for Repartitioning InfoProviders

• Message number: 679

• Message text: Compress all historical movement requests before converting to flat

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.

RSDU_REPART679 - Details

• The SAP error message RSDU_REPART679 indicates that there are historical movement requests that need to be compressed before you can convert them to a flat format. This typically occurs in the context of data warehousing, particularly when working with SAP BW (Business Warehouse) and involves the process of data extraction and loading.
  
  Cause:
  The error arises when you attempt to convert data requests (specifically, historical movement requests) into a flat format without first compressing them. Historical movement requests are data requests that have been loaded into the system but have not yet been compressed. Compression is necessary to optimize storage and improve performance.
  
  Solution:
  To resolve this error, you need to compress all historical movement requests before proceeding with the conversion. Here are the steps to do this:
  
  
  Access the Data Warehousing Workbench:
  
  Go to the SAP BW system and navigate to the Data Warehousing Workbench.
  
  
  
  Open the InfoProvider:
  
  Locate the InfoProvider (e.g., InfoCube) that contains the historical