How To Fix PIC01058 - Product group &1 is locked by the combination plant &2 / user &3

SAP Error Message - Details

• Message type: E = Error

• Message class: PIC01 - Parts Interchangeability Message Class

• Message number: 058

• Message text: Product group &1 is locked by the combination plant &2 / user &3

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 PIC01058 - Product group &1 is locked by the combination plant &2 / user &3 ?

  The SAP error message PIC01058 indicates that a product group is locked in a specific plant by a particular user. This typically occurs in the context of product group management, where certain operations cannot be performed because the product group is currently being edited or processed by another user.
  Cause:
  
  User Lock: The product group is being edited by another user, which prevents other users from making changes to it.
  Transaction in Progress: A transaction that involves the product group is currently in progress, leading to a lock.
  System Lock: The system may have a lock due to a previous operation that did not complete successfully.
  
  Solution:
  
  Identify the Locking User: Check who is currently locking the product group. You can use transaction codes like SM12 (to view locks) to identify the user and the session that is holding the lock.
  Wait for Release: If the lock is due to another user, you may need to wait until they finish their transaction and release the lock.
  Contact the User: If possible, contact the user who is locking the product group to understand their activity and see if they can release the lock.
  Terminate the Session: If the locking session is no longer active or the user is unavailable, a system administrator can terminate the session using transaction SM12 to release the lock.
  Check for Background Jobs: Sometimes, background jobs may also hold locks. Check if there are any jobs running that might be causing the lock.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view and manage locks), SM21 (to check system logs), and SM37 (to monitor background jobs).
  User Management: Ensure that users are aware of the locking mechanism and follow best practices to avoid unnecessary locks.
  Documentation: Refer to SAP documentation for more details on product group management and locking mechanisms.
  
  If the issue persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.