How To Fix RSDDTPS006 - Key figure &1 is not used for Polestar due to exception aggregation

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDDTPS - Messages for Polestar Index Maintenance

• Message number: 006

• Message text: Key figure &1 is not used for Polestar due to exception aggregation

What causes this issue?

Key figures with exception aggregation cannot be used in BusinessObjects
Polestar since the corresponding aggregation rules depend on other
characteristics and settings. These are not mapped in Polestar.

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 RSDDTPS006 - Key figure &1 is not used for Polestar due to exception aggregation ?

  The SAP error message RSDDTPS006 indicates that a key figure is not being used in a Polestar (or similar) context due to exception aggregation. This typically occurs in SAP BW (Business Warehouse) or SAP BW/4HANA environments when working with queries or data models that involve key figures with specific aggregation rules.
  Cause:
  The error arises when a key figure is defined with exception aggregation, which means that it cannot be aggregated in the standard way due to the nature of the data it represents. Exception aggregation is used for key figures that require special handling, such as maximum, minimum, or specific business rules that do not allow for standard summation or averaging.
  Solution:
  To resolve this error, you can consider the following steps:
  
  
  Review Key Figure Definition:
  
  Check the definition of the key figure in the InfoObject. Ensure that it is set up correctly and that the aggregation type is appropriate for your reporting needs.
  
  
  
  Change Aggregation Type:
  
  If the key figure does not need to be an exception aggregation, you can change its aggregation type to a standard aggregation (like SUM or AVG) in the InfoObject settings.
  
  
  
  Adjust Query Design:
  
  If the key figure must remain as an exception aggregation, you may need to adjust your query design. This could involve:
  
  Removing the key figure from the query.
  Using a different key figure that does not have exception aggregation.
  Modifying the query to handle the exception aggregation appropriately.
  
  
  
  
  
  Check for Dependencies:
  
  Ensure that there are no dependencies or other key figures that rely on the problematic key figure. This may involve reviewing the data model and any transformations or calculations that involve this key figure.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more detailed information on exception aggregation and how it affects key figures in your specific context.
  
  
  
  Testing:
  
  After making changes, test the query or report to ensure that it runs without errors and that the data is accurate.
  
  
  
  Related Information:
  
  Exception Aggregation: This is a concept in SAP BW where certain key figures are aggregated based on specific business rules rather than standard mathematical operations. Common examples include calculating the maximum sales amount or the latest order date.
  Key Figures: In SAP BW, key figures are numerical values that can be aggregated and analyzed. They are essential for reporting and analytics.
  Polestar: This term may refer to a specific reporting tool or framework within SAP. Ensure you are familiar with its requirements and limitations regarding key figures and aggregation.
  
  If the issue persists after following these steps, it may be beneficial to consult with an SAP BW expert or reach out to SAP support for further assistance.