How To Fix RSDU_REPART034 - Partitioning cannot be applied

RSDU_REPART034 - Overview

• Message type: E = Error

• Message class: RSDU_REPART - Messages for Repartitioning InfoProviders

• Message number: 034

• Message text: Partitioning cannot be applied

What causes this issue?

If InfoCubes already contain data, it is not possible to apply
partitioning changes using a normal activation.
If InfoCubes already contain data, you cannot normally change the
partitioning using InfoCube maintenance in the system. However, you can
import changes from the upstream test and development systems by using
transports if:

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

a) The InfoCube in the upstream systems does not contain any data, the
partitioning in these systems could therefore be changed using InfoCube
maintenance.
or
b) The partitioning in the upstream systems was changed using the
repartitioning tool.
Oartitioning of InfoCubes is a local system property that cannot be
transported for the following reasons:
In a productive system with a large volume of data, you will often want
to use different partitioning to that used in the development system
(which has a smaller volume of data), because partitioning can be
counterproductive if there is only a small volume of data.
Changing the partitioning usually means reorganizing the fact tables,
meaning that all data records have to be copied. Since the runtime on
the database depends linearly on the size of the InfoCube in the target
system and can last several hours, actions of this kind should be
scheduled and executed at times when there is less burden on the system,
for example at weekends. Otherwise, this can impair the runtime behavior
of the entire productive system.
During reorganization, all data records are copied, indexes are rebuilt,
and database statistics are calculated. This requires additional memory,
which is not always available. This can lead to system termination.
During reorganization, the relevant InfoCubes are locked to protect them
from modification actions (such as loading data, deleting data,
compressing, rolling up in aggregates, building aggregates or change
runs). This is the only way to guarantee data consistency. These 'dead
times' should be planned.
Changes to the partitioning can inadvertently enter the productive
system in transport requests. Example: Person A changes the partitioning
of InfoCube CUBE in the development system, but does not write this
change to a transport request, since s/he is aware of the consequences
for the productive system. Person B adds an additional key figure to
InfoCube CUBE and writes the InfoCube to a transport request so that the
change becomes active in the downstream systems. The change to the
partitioning would then also enter the productive system with this
transport request, without the consequences being clear to person B, who
triggered the transport request.
Changes made to the partitioning of InfoCubes by transports are only
applied if InfoCubes in the target system do not contain any data. This
behavior is an exception to the concept of 'local system partitioning
properties', but should support BW administrators in broadcasting all
settings of an InfoCube over the system landscape when a new InfoCube is
created. If an InfoCube already exists in the target system and does not
contain any data, both fact tables of the InfoCube are deleted during
the import and are rebuilt according to the new description (including
the modified partitioning).

System Response

The changes to the partitioning are not applied to the active InfoCube.
All other changes are activated. There is no negative impact on the
productive system. The InfoCube can continue to be used without
restrictions.

How to fix this error?

If you want to adjust the partitioning of the InfoCube in the system,
use the repartitioning function (transaction RSA1 --> >Administration
(bottom left) -- >Repartitioning). Make sure that you have read the
documentation and SAP Note 1008833 before doing this.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

RSDU_REPART034 - Details

• The SAP error message RSDU_REPART034, which states "Partitioning cannot be applied," typically occurs in the context of data warehousing and is related to the partitioning of InfoProviders in SAP BW (Business Warehouse). This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  Inconsistent Data: The data in the InfoProvider may not be consistent or may not meet the criteria required for partitioning.
  Incorrect Partitioning Settings: The settings for partitioning may not be correctly configured, such as the partitioning key or the range of data.
  Data Model Changes: Changes in the data model or structure of the InfoProvider can lead to issues with partitioning.
  Data Volume: If the volume of data is too small or does not meet the minimum requirements for partitioning, the system may not allow partitioning.
  Technical Issues: There may be underlying technical issues or bugs in the SAP system that prevent partitioning from being