How To Fix RSDD502 - Cannot determine new proposals for aggregates


SAP Error Message - Details

  • Message type: E = Error

  • Message class: RSDD - Message class for data manager

  • Message number: 502

  • Message text: Cannot determine new proposals for aggregates

  • Show details Hide details


  • 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 RSDD502 - Cannot determine new proposals for aggregates ?

    The SAP error message RSDD502, which states "Cannot determine new proposals for aggregates," typically occurs in the context of SAP BW (Business Warehouse) when there are issues related to the aggregation of data in InfoCubes. This error can arise during the process of data loading, when trying to activate aggregates, or when performing certain operations that involve aggregates.

    Causes:

    1. Missing or Inconsistent Data: The underlying data in the InfoProvider may be incomplete or inconsistent, which can prevent the system from determining the necessary aggregates.
    2. Incorrect Aggregation Settings: The settings for the aggregates may not be configured correctly, leading to issues in determining new proposals.
    3. Changes in Data Model: If there have been recent changes to the data model (e.g., changes in InfoObjects, InfoProviders, or transformations), it may affect the aggregate proposals.
    4. Performance Issues: If the system is under heavy load or if there are performance issues, it may not be able to process the aggregate proposals in a timely manner.
    5. Technical Issues: There may be underlying technical issues, such as database locks or inconsistencies in the metadata.

    Solutions:

    1. Check Data Consistency: Ensure that the data in the InfoCube is consistent and complete. You can run consistency checks or data validation processes to identify any issues.
    2. Review Aggregate Settings: Verify the settings for the aggregates in the InfoCube. Ensure that they are configured correctly and that the necessary InfoObjects are included.
    3. Rebuild Aggregates: If the aggregates are corrupted or not functioning as expected, consider rebuilding them. This can be done by deleting the existing aggregates and creating new ones.
    4. Check for Changes in Data Model: If there have been recent changes to the data model, review those changes to ensure they are compatible with the existing aggregates.
    5. Monitor System Performance: Check the system performance and ensure that it is not under heavy load. If necessary, schedule data loading or aggregate processing during off-peak hours.
    6. Check for Locks: Investigate if there are any database locks that might be preventing the system from processing the aggregates. You can use transaction codes like SM12 to check for locks.
    7. Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases updates and patches that can resolve known issues.

    Related Information:

    • Transaction Codes: You may find it useful to use transaction codes such as RSA1 (Data Warehousing Workbench) to manage InfoProviders and aggregates.
    • SAP BW Documentation: Refer to the official SAP BW documentation for detailed information on aggregates and best practices for managing them.
    • SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found effective.

    If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant