How To Fix RSM1026 - Min/max aggregation used in the update rules; cancellation not possible

RSM1026 - Overview

• Message type: E = Error

• Message class: RSM1 - Messages for AWB, Scheduler and Monitor (new)

• Message number: 026

• Message text: Min/max aggregation used in the update rules; cancellation not possible

What causes this issue?

Minimum / maximum aggregation is used in the update rules, which means
it is not possible to cancel this request (or not useful, as the
minimum/maximum aggregation is not removed when the data is updated
negatively, and, as a result, incorrect data would appear in the
InfoCube).

System Response

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

How to fix this error?

Delete the request from the InfoCube.
If aggregates exist, it is not possible to delete the InfoCube. If this
is the case, deactivate the aggregate, delete the request from the
InfoCube, and reconstruct the aggregate.
If the request is compressed, it is no longer possible to delete it,
because the request ID is no longer available in the InfoCube, and the
system can no longer identify the data that you want to delete.
The only option is to delete the contents of the InfoCube completely,
and reconstruct the InfoCube from the PSA or the ALE inbound
processing, or to reload the data from the source system.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSM1026 - Min/max aggregation used in the update rules; cancellation not possible ?

  The SAP error message RSM1026, which states "Min/max aggregation used in the update rules; cancellation not possible," typically occurs in the context of SAP BW (Business Warehouse) when you are trying to cancel or reverse a data update that involves min/max aggregation in the update rules.
  
  Cause:
  The error arises because the update rules defined for the InfoObject or InfoProvider are set to use min/max aggregation. In this case, the system does not allow the cancellation of data records because min/max aggregation does not support the reversal of data. This is due to the nature of how min/max aggregation works; it calculates the minimum or maximum value from a set of data, and reversing this operation is not straightforward.
  
  Solution:
  To resolve this issue, you can consider the following approaches:
  
  
  Check Update Rules: Review the update rules for the InfoObject or InfoProvider in question. If min/max aggregation is not necessary for your reporting needs, consider