How To Fix /SAPAPO/PDRP064 - Planning lock for location product &1 &2, BOD subtree not planned

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/PDRP -

• Message number: 064

• Message text: Planning lock for location product &1 &2, 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/PDRP064 - Planning lock for location product &1 &2, BOD subtree not planned ?

  The SAP error message /SAPAPO/PDRP064 indicates that there is a planning lock for a specific location product combination, which prevents the planning process from executing for that particular Business Object Data (BOD) subtree. This error typically occurs in the context of SAP Advanced Planning and Optimization (APO) when the system is unable to plan for a location-product combination due to existing locks.
  Cause:
  
  Planning Lock: The most common cause of this error is that another planning process is currently running and has locked the location-product combination. This can happen if multiple users or processes are trying to plan the same data simultaneously.
  Incomplete Data: If the data for the location-product combination is incomplete or inconsistent, it may also lead to planning locks.
  Configuration Issues: Incorrect configuration in the planning area or planning book can lead to this error.
  Background Jobs: If there are background jobs that are running and holding locks on the data, this can also cause the error.
  
  Solution:
  
  Check Locks: Use transaction code SM12 to check for existing locks on the location-product combination. If you find locks that are no longer needed, you can delete them (ensure that you have the necessary authorizations).
  Wait for Completion: If another planning process is running, you may need to wait for it to complete before attempting to plan again.
  Review Data: Ensure that all necessary data for the location-product combination is complete and consistent. Check master data and transactional data for any discrepancies.
  Configuration Review: Review the configuration of the planning area and planning book to ensure that they are set up correctly.
  Background Job Monitoring: Check for any background jobs that may be running and holding locks. You can use transaction SM37 to monitor background jobs.
  Restart Planning: After resolving any locks or data issues, restart the planning process for the affected location-product combination.
  
  Related Information:
  
  Transaction Codes: 
  
  SM12 - To check and manage locks.
  SM37 - To monitor background jobs.
  SCC4 - To check client settings.
  
  
  Documentation: Refer to SAP Help documentation for more details on planning locks and troubleshooting planning issues in SAP APO.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or APO support team for further investigation.