How To Fix CM_EHPRC_BO_WL_CMN120 - Lock failed while processing changes of regulatory list

CM_EHPRC_BO_WL_CMN120 - Overview

• Message type: E = Error

• Message class: CM_EHPRC_BO_WL_CMN - Compliance Worklist - Common Messages

• Message number: 120

• Message text: Lock failed while processing changes of regulatory list

What causes this issue?

After saving a regulatory list the following steps are necessary:
1. The system detects the changes and stores them in temporary tables.
2. A job processes these changes and creates a worklist that contains
all compliance objects affected by the regulatory list change.
3. The affected compliance objects must be processed manually.
The issue is that the content in the temporary tables could not be
locked. The system has to lock the changes in the temporary tables to
mark them as <LS>in process</> or <LS>completed</>.

System Response

The changes cannot be locked and therefore the job cannot create a
regulatory list worklist. The next execution of the job tries to process
these changes again.

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

Wait for the next execution of the job. If the problem persists, check
the BOPF tables for BO EHFND_REGLIST_COMPARE_RESULT with key &v1&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_EHPRC_BO_WL_CMN120 - Lock failed while processing changes of regulatory list ?

  The SAP error message CM_EHPRC_BO_WL_CMN120 indicates that there was a failure in acquiring a lock while processing changes to a regulatory list. This error typically occurs in the context of SAP's Environment, Health, and Safety (EHS) module, particularly when dealing with regulatory compliance data.
  Causes:
  
  Concurrent Access: The most common cause of this error is that another user or process is currently accessing or modifying the same regulatory list, leading to a lock conflict.
  Long-running Transactions: If a transaction takes too long to complete, it may hold a lock on the regulatory list, preventing other processes from accessing it.
  System Performance Issues: High system load or performance issues can lead to delays in lock acquisition.
  
  Configuration Issues: Incorrect configuration of the EHS module or related components may also lead to locking issues.
  
  Solutions:
  
  Check for Concurrent Users: Verify if another user is currently editing the regulatory list. If so, wait for them to complete their changes.
  Transaction Monitoring: