How To Fix /SAPAPO/TDL_DAO072 - Data for location &1 and product &2 are locked

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/TDL_DAO -

• Message number: 072

• Message text: Data for location &1 and product &2 are locked

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/TDL_DAO072 - Data for location &1 and product &2 are locked ?

  The SAP error message /SAPAPO/TDL_DAO072 indicates that the data for a specific location and product is locked, which prevents certain operations from being performed on that data. This is commonly encountered in SAP Advanced Planning and Optimization (APO) environments, particularly when dealing with planning data.
  Cause:
  
  Data Locking: The most common cause of this error is that the data for the specified location and product is currently being accessed or modified by another user or process. This can happen during planning runs, data uploads, or when another user is editing the same data.
  Background Jobs: If there are background jobs running that are processing the same data, they may lock the data temporarily.
  Transaction Locks: Certain transactions may lock data for the duration of their execution, leading to this error if another transaction tries to access the same data.
  
  Solution:
  
  Wait and Retry: If the lock is temporary, waiting for a few moments and then retrying the operation may resolve the issue.
  Identify the Lock: Use transaction SM12 to check for existing locks. You can look for locks on the specific location and product combination. If you find a lock that is no longer needed, you can delete it (if you have the necessary authorizations).
  Check Background Jobs: Use transaction SM37 to check for any background jobs that might be running and locking the data. If you find a job that is taking too long, you may need to investigate further or contact the job owner.
  User Coordination: If multiple users are working on the same data, coordinate with your team to avoid simultaneous access to the locked data.
  System Configuration: In some cases, it may be necessary to review system settings or configurations that could be causing excessive locking. This may involve consulting with your SAP Basis team.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM37: To monitor background jobs.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to data locking in your version of SAP APO.
  Documentation: Review SAP documentation on data locking mechanisms in APO to understand how locks are managed and how to avoid them in the future.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP support team or consult with SAP directly for further assistance.