How To Fix /SAPAPO/SNP_CCMS058 - Number of entries for the planning version in level 2 queues is too high

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/SNP_CCMS -

• Message number: 058

• Message text: Number of entries for the planning version in level 2 queues is too high

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 /SAPAPO/SNP_CCMS058 - Number of entries for the planning version in level 2 queues is too high ?

  The SAP error message /SAPAPO/SNP_CCMS058 indicates that the number of entries for the planning version in level 2 queues is too high. This typically occurs in the context of SAP Advanced Planning and Optimization (APO), particularly in the Supply Network Planning (SNP) module. 
  Cause:
  
  High Volume of Data: The error is often caused by a large volume of planning data that exceeds the threshold set for level 2 queues. This can happen if there are many planning objects or if the planning version is being heavily used.
  Inefficient Planning Runs: If planning runs are not optimized or if there are too many concurrent planning processes, it can lead to an accumulation of entries in the queues.
  Configuration Issues: Incorrect configuration settings for the planning version or the SNP can also lead to this issue.
  
  Solution:
  
  
  Monitor and Optimize Planning Runs:
  
  Review the planning runs to ensure they are optimized. Consider scheduling them during off-peak hours to reduce the load on the system.
  Limit the number of concurrent planning runs if possible.
  
  
  
  Increase Queue Limits:
  
  If the high number of entries is expected due to business requirements, consider increasing the limits for the level 2 queues. This can be done through configuration settings in the SAP system.
  
  
  
  Clean Up Queues:
  
  Regularly monitor and clean up the queues to remove any unnecessary entries. This can help in managing the number of entries effectively.
  
  
  
  Check Configuration:
  
  Review the configuration settings for the planning version and ensure they are set correctly. This includes checking the settings for the SNP and ensuring they align with the business processes.
  
  
  
  System Performance:
  
  Ensure that the system has adequate resources (CPU, memory, etc.) to handle the planning processes efficiently. Performance tuning may be necessary.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may provide additional guidance or patches related to this error message.
  
  
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like /SAPAPO/CCMS to monitor the queues and /SAPAPO/SNP for SNP-related configurations.
  SAP Documentation: Refer to the official SAP documentation for detailed information on managing planning versions and queues in SAP APO.
  SAP Community: Engage with the SAP Community for insights and experiences from other users who may have encountered similar issues.
  
  By addressing the underlying causes and implementing the suggested solutions, you should be able to resolve the error message and improve the performance of your planning processes in SAP APO.