How To Fix /SAPAPO/PDRP066 - Planning lock: Virtual child location &1 &2 from BOD subtree not planned

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/PDRP -

• Message number: 066

• Message text: Planning lock: Virtual child location &1 &2 from BOD subtree not planned

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/PDRP066 - Planning lock: Virtual child location &1 &2 from BOD subtree not planned ?

  The SAP error message /SAPAPO/PDRP066 Planning lock: Virtual child location &1 &2 from BOD subtree not planned typically occurs in the context of SAP Advanced Planning and Optimization (APO) when there is an issue with planning locks related to virtual child locations in a Bill of Distribution (BOD) subtree. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Planning Lock: The error indicates that there is a planning lock on a virtual child location. This can happen if another planning run is currently processing the same location or if the location is locked due to a previous planning run that did not complete successfully.
  Virtual Child Location: The error specifically mentions a virtual child location, which is a location that does not have physical inventory but is used for planning purposes. If the parent location is being planned, the child locations must also be planned.
  BOD Subtree: The Bill of Distribution subtree refers to the hierarchical structure of locations. If a parent location is locked, it can prevent the planning of its child locations.
  
  Solutions:
  
  Check Locks: Use transaction code SM12 to check for any existing locks on the virtual child location. If you find locks that are no longer needed, you can delete them.
  Planning Run Status: Verify the status of the planning run. If a planning run is still active or has failed, you may need to wait for it to complete or resolve any issues before attempting to plan again.
  Re-run Planning: After resolving any locks or issues, re-run the planning process for the affected locations. You can do this through the relevant planning transaction in SAP APO.
  Check Configuration: Ensure that the configuration for the BOD and the virtual child locations is set up correctly. This includes checking the master data and planning parameters.
  Consult Logs: Review the planning logs for any additional error messages or warnings that may provide more context on the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (for lock entries), SNP1 (for SNP planning), and SNP2 (for planning book).
  SAP Notes: Check for any SAP Notes related to this error message or similar issues. SAP Notes often provide patches or additional guidance for resolving specific errors.
  Documentation: Review the SAP APO documentation for information on planning locks, BOD structures, and virtual locations to better understand the context of the error.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or APO support team for further assistance.