How To Fix CBRC_REGCHECK321 - Regulatory list &1 is currently locked

CBRC_REGCHECK321 - Overview

• Message type: E = Error

• Message class: CBRC_REGCHECK - Messages for Substance-Related Regulation Check

• Message number: 321

• Message text: Regulatory list &1 is currently locked

What causes this issue?

Report &V2& cannot be executed for regulatory list &V1& for substance
volume tracking since one of the following reports is currently
processing regulatory list &V1&:
RREGCH_FILL: Substance Volume Tracking: Data Transfer from Property Tree
RREGCH_VT: Substance Volume Tracking: Tracking of Substance Quantities
RREGCH_RESTART_VT: Substance Volume Tracking: Correction of Tracked
Substance Quantities
RREGCH_VT_CONDENSE_SAVE: Substance Volume Tracking: Save Tracked
Quantities in Property Tree
RREGCH_CALC: Substance Volume Tracking: Average Calculation
RREGCH_DEL_DATA: Substance Volume Tracking: Delete Data (INTERNAL)

System Response

How to fix this error?

Call transaction <DS:TRAN.SM12>SM12</> (<LS>Tools -> Administration ->
Monitor -> Lock Entries</>).
Enter table name <LS> </>CCRCT_RUN.
Check the lock table to identify which user is holding the requested
lock. Contact this user if necessary.
Once the lock on the regulatory list has been removed, you can run
report &V2& again for regulatory list &V1&.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CBRC_REGCHECK321 - Details

• The SAP error message CBRC_REGCHECK321 indicates that a regulatory list (such as a list of restricted substances or compliance regulations) is currently locked, preventing any modifications or access to it. This can occur in various SAP modules, particularly those related to compliance, regulatory management, or environmental health and safety.
  
  Cause:
  
  Concurrent Access: Another user or process is currently accessing or modifying the regulatory list, which locks it for other users.
  System Lock: The system may have a lock due to a previous transaction that did not complete properly.
  
  Configuration Issues: There may be configuration settings that inadvertently cause the list to be locked.
  Database Locks: Database-level locks can occur if there are long-running transactions or if the database is under heavy load.
  
  
  Solution:
  
  Wait and Retry: If the lock is due to another user, waiting for a short period and then retrying the operation may resolve the issue.
  Check Lock Entries: Use transaction code SM12 to check for