How To Fix /SAPAPO/PP_OPTIMIZER813 - Starting partial search

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/PP_OPTIMIZER -

• Message number: 813

• Message text: Starting partial search

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/PP_OPTIMIZER813 - Starting partial search ?

  The SAP error message /SAPAPO/PP_OPTIMIZER813 Starting partial search typically occurs in the context of the SAP Advanced Planning and Optimization (APO) module, particularly when using the PP/DS (Production Planning and Detailed Scheduling) optimizer. This message indicates that the optimizer is starting a partial search, which can happen for various reasons.
  Cause:
  
  Insufficient Resources: The optimizer may not have enough resources (like capacity or materials) to perform a full search, leading it to initiate a partial search.
  Complexity of the Problem: The planning problem may be too complex or large, causing the optimizer to limit its search to find a feasible solution within a reasonable time.
  Configuration Issues: Incorrect or suboptimal configuration settings in the optimizer can lead to partial searches.
  Data Issues: Inconsistent or incomplete master data (like BOMs, routing, or resource availability) can also trigger this message.
  
  Solution:
  
  Review Resource Availability: Check the availability of resources, materials, and capacities to ensure that they are sufficient for the planned production.
  Optimize Configuration Settings: Review and adjust the configuration settings of the optimizer. This may include parameters related to search strategies, time buckets, and planning horizons.
  Simplify the Planning Problem: If possible, break down the planning problem into smaller, more manageable parts. This can help the optimizer perform a full search.
  Data Consistency Check: Ensure that all relevant master data is complete and consistent. This includes checking BOMs, routing, and resource definitions.
  Run the Optimizer in Debug Mode: If the issue persists, consider running the optimizer in debug mode to gather more detailed logs and identify the root cause of the partial search.
  Consult SAP Notes: Check for any relevant SAP Notes or updates that may address known issues related to the optimizer.
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for the PP/DS optimizer for detailed information on configuration and troubleshooting.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Performance Tuning: Consider performance tuning of the optimizer settings to improve its efficiency and ability to handle larger planning problems.
  
  If the issue continues after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.