How To Fix RSODSO_TOOLS035 - Saving consolidated aggregation data was terminated


SAP Error Message - Details

  • Message type: E = Error

  • Message class: RSODSO_TOOLS -

  • Message number: 035

  • Message text: Saving consolidated aggregation data was terminated

  • Show details Hide details
  • What causes this issue?

    &v1&

    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?

    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 RSODSO_TOOLS035 - Saving consolidated aggregation data was terminated ?

    The SAP error message RSODSO_TOOLS035 indicates that the process of saving consolidated aggregation data was terminated. This error typically occurs in the context of SAP BW (Business Warehouse) when there are issues related to data processing in InfoProviders, particularly when dealing with DataStore Objects (DSOs) or InfoCubes.

    Causes:

    1. Data Consistency Issues: There may be inconsistencies in the data being processed, such as missing or incorrect data records.
    2. Locking Issues: The DSO or InfoCube might be locked by another process, preventing the current process from saving data.
    3. Memory Issues: Insufficient memory or resources on the application server can lead to termination of the process.
    4. Configuration Errors: Incorrect settings in the DSO or aggregation settings can lead to this error.
    5. Data Volume: Large volumes of data being processed at once can cause timeouts or resource exhaustion.

    Solutions:

    1. Check for Locks: Use transaction codes like SM12 to check for any locks on the DSO or InfoCube. If there are locks, you may need to wait for the other process to complete or manually release the locks if appropriate.
    2. Review Data: Check the data being loaded into the DSO or InfoCube for any inconsistencies or errors. You can use transaction codes like RSA1 to monitor data loads and check for errors.
    3. Increase Memory: If memory issues are suspected, consider increasing the memory allocation for the application server or optimizing the data load process.
    4. Adjust Aggregation Settings: Review the aggregation settings in the DSO or InfoCube to ensure they are configured correctly.
    5. Batch Processing: If large volumes of data are causing issues, consider breaking the data load into smaller batches to reduce the load on the system.
    6. Check Logs: Review the application logs (transaction SLG1) for more detailed error messages that can provide insights into the specific cause of the termination.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), SM37 (Job Monitoring), and SLG1 (Application Log).
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide patches and updates.
    • Performance Tuning: Consider performance tuning for your BW system, including optimizing data models and queries to improve overall efficiency.

    If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or 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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker