How To Fix RSM1198 - No aggregation info for request &1 and DSO &2; no activation

RSM1198 - Overview

• Message type: E = Error

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

• Message number: 198

• Message text: No aggregation info for request &1 and DSO &2; no activation

What causes this issue?

For the &V1& request and the &V2& DataStore object, no information
exists in the <ZH>RSODSACTUPDTYPE</> table about the aggregation of key
figures.

System Response

The activation of the &V1& request is not possible without this entry.
You create the entries when you write the request to the DataStore
object activation queue.

How to fix this error?

Delete the request from the DataStore object and update it again from
the PSA into the DataStore object.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSM1198 - No aggregation info for request &1 and DSO &2; no activation ?

  The SAP error message RSM1198 indicates that there is no aggregation information available for a specific request and DataStore Object (DSO), which prevents the activation of the request. This error typically occurs in the context of SAP BW (Business Warehouse) when you are trying to activate a data load request that requires aggregation but cannot find the necessary aggregation information.
  
  Cause:
  
  Missing Aggregation Info: The most common cause of this error is that the DSO does not have the required aggregation settings defined. This can happen if the DSO was not properly configured or if the aggregation settings were inadvertently deleted or not set up.
  Data Model Changes: If there have been recent changes to the data model, such as changes to InfoObjects or the DSO structure, it may lead to inconsistencies that result in missing aggregation information.
  Request Issues: The request being processed may not be compatible with the DSO's current configuration, leading