Do you have any question about this error?
Message type: E = Error
Message class: /SAPAPO/TSM -
Message number: 720
Message text: No aggregate chosen
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.
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.
/SAPAPO/TSM720
- No aggregate chosen ?The SAP error message
/SAPAPO/TSM720 No aggregate chosen
typically occurs in the context of SAP Advanced Planning and Optimization (APO), particularly when working with the Time Series Management (TSM) functionality. This error indicates that the system could not find a suitable aggregate for the time series data being processed.Cause:
- Missing Aggregates: The most common cause of this error is that there are no aggregates defined for the key figures or planning objects you are trying to analyze or process.
- Incorrect Configuration: The aggregates may not be properly configured or activated in the system.
- Data Issues: There may be issues with the data itself, such as missing or incomplete data that prevents the system from identifying the appropriate aggregate.
- Planning Area Issues: The planning area may not be set up correctly, or the aggregates may not be assigned to the planning area.
Solution:
Check Aggregate Definitions:
- Go to the transaction code
/SAPAPO/TSM
and check the aggregate definitions for the relevant planning area.- Ensure that the aggregates are defined for the key figures you are working with.
Create or Activate Aggregates:
- If aggregates are missing, you may need to create them. Use the transaction
/SAPAPO/TSM1
to create new aggregates.- If aggregates exist but are not activated, activate them using the appropriate transaction.
Review Planning Area Configuration:
- Check the configuration of the planning area to ensure that the aggregates are correctly assigned.
- Use transaction
/SAPAPO/MP30
to review the planning area settings.Data Consistency Check:
- Ensure that the data in the key figures is complete and consistent. You may need to run data consistency checks or reprocess the data.
Consult Documentation:
- Review SAP documentation or notes related to the specific version of APO you are using for any additional troubleshooting steps or known issues.
Contact SAP Support:
- If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
Related Information:
Transaction Codes:
/SAPAPO/TSM
: Time Series Management/SAPAPO/TSM1
: Create/Change Aggregates/SAPAPO/MP30
: Planning Area ConfigurationSAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
Documentation: Refer to the SAP Help Portal for detailed documentation on Time Series Management and aggregate handling in SAP APO.
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
/SAPAPO/TSM719
Standard SNP planning level &1 was deactivated for &2
What causes this issue? The transported standard SNP planning level had a different status than that of the planning object structure that the standa...
/SAPAPO/TSM718
Standard SNP planning level &1 was activated for &2
What causes this issue? The transported standard SNP planning level had a different status than that of the planning object structure that the standa...
/SAPAPO/TSM723
Select a hierarchy structure with object type: location product
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/SAPAPO/TSM724
Select a hierarchy structure with object type: PPM or PDS
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.