How To Fix CM_EHPRC_BO_WL_CMN113 - Worklist Creation: Cannot find regulatory list rev. key &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHPRC_BO_WL_CMN - Compliance Worklist - Common Messages

• Message number: 113

• Message text: Worklist Creation: Cannot find regulatory list rev. key &1

What causes this issue?

The system has detected some changes in active regulatory list revisions
or mapping of listed substances to pure substance. The changes are
stored as a compare result. Later a job processes these changes to
create a worklist to get the affected objects compliant.
The cause of this error is that the processing cannot find the
regulatory list revision for this stored compare result of a regulatory
list change.

System Response

The system stops processing for this regulatory list change and
continues with the next one.

How to fix this error?

Call your system administrator.

Procedure for System Administrators

The changes are stored in the table of <AB>BO
EHFND_REGLIST_COMPARE_RESULT</>. Check if the regulatory list revision
exists and if the batch user is authorized for it.
If the regulatory list revision has been deleted, delete also the entry
in the compare result table.
Key of regulatory list revision: &v1&
Key of compare result: &v2&

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

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_CMN113 - Worklist Creation: Cannot find regulatory list rev. key &1 ?

  The SAP error message CM_EHPRC_BO_WL_CMN113 indicates that there is an issue with the creation of a worklist due to the system being unable to find a regulatory list revision key. This error typically occurs in the context of SAP's Environment, Health, and Safety (EHS) module, particularly when dealing with regulatory compliance and worklist management.
  Cause:
  
  Missing Regulatory List: The regulatory list that the system is trying to reference may not exist or may not be properly configured in the system.
  Incorrect Configuration: The regulatory list may not be assigned correctly to the relevant business objects or may not be activated.
  Data Inconsistency: There may be inconsistencies in the data related to the regulatory lists, such as missing entries or incorrect keys.
  Authorization Issues: The user may not have the necessary authorizations to access the regulatory lists.
  
  Solution:
  
  Check Regulatory Lists: Verify that the regulatory list in question exists in the system. You can do this by navigating to the relevant transaction codes (e.g., C223 for regulatory lists) and checking if the list is active and properly configured.
  Review Configuration: Ensure that the regulatory list is correctly assigned to the relevant business objects. Check the configuration settings in the EHS module to ensure everything is set up correctly.
  Data Consistency Check: Run consistency checks on the regulatory lists and related data to identify any discrepancies. You may need to correct any inconsistencies found.
  User Authorizations: Ensure that the user attempting to create the worklist has the necessary authorizations to access the regulatory lists. You may need to consult with your SAP security team to verify and adjust user roles if necessary.
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional troubleshooting steps or patches that may address the issue.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error code or related keywords in the SAP Support Portal.
  Transaction Codes: Familiarize yourself with relevant transaction codes in the EHS module, such as:
  
  C223: Display Regulatory List
  C220: Maintain Regulatory List
  
  
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the issue persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.