How To Fix RSMPC109 - Aggregate &1 Does Not Exist And Was Removed From The Variant

SAP Error Message - Details

• Message type: E = Error

• Message class: RSMPC - Messages for Process Chains of Generic Processes

• Message number: 109

• Message text: Aggregate &1 Does Not Exist And Was Removed From The Variant

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSMPC109 - Aggregate &1 Does Not Exist And Was Removed From The Variant ?

  The SAP error message RSMPC109 indicates that a specific aggregate (in this case, identified as &1) does not exist and has been removed from the variant. This typically occurs in the context of SAP BW (Business Warehouse) when working with queries or reports that rely on aggregates for performance optimization.
  Cause:
  
  Deleted Aggregate: The aggregate that the query or report is trying to access has been deleted or is no longer available in the system.
  Transport Issues: If the aggregate was transported from one system to another (e.g., from development to production), it may not have been included in the transport request.
  Data Model Changes: Changes in the underlying data model (like InfoCubes or DataStore Objects) may have led to the removal of the aggregate.
  Incorrect Variant: The variant being used may reference an aggregate that is not valid or has been changed.
  
  Solution:
  
  Check Aggregate Existence: Verify if the aggregate still exists in the system. You can do this by navigating to the relevant InfoCube in the SAP BW modeling tools and checking the aggregates.
  Recreate the Aggregate: If the aggregate has been deleted, you may need to recreate it. This can be done through the InfoCube maintenance transaction (e.g., RSA1).
  Update the Variant: If the aggregate has been changed or removed, you may need to update the variant to reference a valid aggregate. This can be done in the query designer or report settings.
  Transport Check: If the issue arose after a transport, ensure that all necessary objects, including aggregates, were included in the transport request.
  Consult Documentation: Review any documentation or change logs to understand why the aggregate was removed or altered.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like RSA1 (Data Warehousing Workbench) to manage aggregates and InfoCubes.
  Query Designer: Use the Query Designer to check the queries that are using the aggregates and modify them as necessary.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Performance Considerations: Understand that aggregates are used to improve query performance, so removing them can lead to slower query execution times.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or BW team for further investigation.