How To Fix /SAPAPO/PPO_OPT120 - &1 products were locked in another session hence they were skipped.

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/PPO_OPT -

• Message number: 120

• Message text: &1 products were locked in another session hence they were skipped.

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/PPO_OPT120 - &1 products were locked in another session hence they were skipped. ?

  The SAP error message /SAPAPO/PPO_OPT120 indicates that certain products were locked in another session during a planning operation in SAP Advanced Planning and Optimization (APO). This typically occurs when multiple users or processes are trying to access or modify the same product data simultaneously, leading to a lock situation to maintain data integrity.
  Cause:
  
  Concurrent Access: Another user or process is currently accessing or modifying the same product data, causing a lock.
  Long-Running Transactions: A transaction that takes a long time to complete may hold locks longer than expected, preventing other sessions from accessing the same data.
  System Configuration: The system may be configured to lock certain objects during specific operations, which can lead to this error if not managed properly.
  
  Solution:
  
  Identify the Lock: Use transaction code SM12 to check for existing locks. You can filter by user or object to find out which session is holding the lock.
  Wait and Retry: If the lock is temporary, you may simply wait for the other session to complete its operation and then retry your action.
  Terminate the Lock: If you have the necessary authorizations and it is safe to do so, you can delete the lock entry in SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other session is still active.
  Optimize Processes: Review and optimize the processes that are causing locks. This may involve scheduling jobs during off-peak hours or improving the performance of long-running transactions.
  Increase Lock Timeout: If applicable, consider adjusting the lock timeout settings in the system configuration to allow for longer wait times before a lock is considered an error.
  
  Related Information:
  
  Transaction Codes: 
  
  SM12: Display and manage lock entries.
  SM21: Check system logs for any related issues.
  ST22: Analyze dumps that may provide insights into the problem.
  
  
  Documentation: Refer to SAP Help documentation for more details on locking mechanisms in APO and best practices for managing concurrent access.
  User Training: Ensure that users are trained on how to manage their sessions and avoid long-running transactions that can lead to locks.
  
  By following these steps, you should be able to resolve the issue related to the /SAPAPO/PPO_OPT120 error message effectively.