How To Fix COM_PRODUCT602 - Category &1 is locked; set type &2 cannot be saved

SAP Error Message - Details

• Message type: E = Error

• Message class: COM_PRODUCT - General Messages on Products

• Message number: 602

• Message text: Category &1 is locked; set type &2 cannot be saved

What causes this issue?

You want to maintain the attributes of set type &V2& for the product.
This set type is assigned to category &V1&. Another user is currently
maintaining this category.
The set type contains multiple-value attributes that are stored in the
PME (Product Modeling Environment). To prevent inconsistencies arising
in the PME, the category must not be locked when the values of
multiple-value attributes are saved in the PME.

System Response

You cannot save the product. You cannot do this until the category &V1&
is no longer locked.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message COM_PRODUCT602 - Category &1 is locked; set type &2 cannot be saved ?

  The SAP error message COM_PRODUCT602 indicates that a specific category (denoted by &1) is locked, preventing the saving of a set type (denoted by &2). This error typically occurs in the context of SAP's Product Lifecycle Management (PLM) or similar modules where product data management is involved.
  Cause:
  
  
  Locked Category: The category you are trying to work with is currently locked. This could be due to:
  
  Another user is editing the same category.
  The category is in a status that does not allow changes (e.g., it might be in a "locked" state due to a workflow or approval process).
  System or application-level locks that prevent modifications.
  
  
  
  Authorization Issues: The user may not have the necessary permissions to modify the category or set type.
  
  
  Technical Issues: There could be underlying technical issues, such as database locks or inconsistencies in the application.
  
  
  Solution:
  
  
  Check Locks: 
  
  Use transaction code SM12 to check for any locks on the category. If another user is holding a lock, you may need to wait until they release it or contact them to coordinate.
  
  
  
  Review Category Status: 
  
  Ensure that the category is not in a status that prevents changes. You may need to change the status or unlock it if you have the necessary permissions.
  
  
  
  User Authorization: 
  
  Verify that you have the appropriate authorizations to modify the category and set type. If not, contact your SAP security administrator to request the necessary permissions.
  
  
  
  Technical Support: 
  
  If the issue persists, consider reaching out to your SAP Basis or technical support team to investigate any underlying technical issues that may be causing the lock.
  
  
  
  Retry Saving: 
  
  After addressing the above points, try saving the set type again.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM12: To view and manage locks.
  SE11: To check the data dictionary for the category and set type.
  SE80: For development-related checks if you suspect a custom development issue.
  
  
  
  Documentation: Review SAP documentation related to Product Management and the specific module you are working with for more context on category management.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.