How To Fix EHSB_RC100 - Value assignment type/class &1 does not exist

EHSB_RC100 - Overview

• Message type: E = Error

• Message class: EHSB_RC - Compliance Check

• Message number: 100

• Message text: Value assignment type/class &1 does not exist

What causes this issue?

The value assignment type or class specified does not exist in the
classification system.

System Response

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

How to fix this error?

Check the settings in Customizing for Product Safety and Stewardship
under <LS>Basic Data and Tools</> -> <LS>Compliance Check</> ->
<DS:SIMG.EHSBC_RC_CONSTR>Set Up Constraints</>and
<DS:SIMG.EHSBC_RC_PARA>Set Up Technical Parameters</>, or create the
required class in the classification system.

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 EHSB_RC100 - Value assignment type/class &1 does not exist ?

  The SAP error message EHSB_RC100 indicates that a value assignment type or class specified in the system does not exist. This error is typically encountered in the context of SAP Environment, Health, and Safety (EHS) module, particularly when dealing with substance data, safety data sheets, or other related functionalities.
  
  Cause:
  
  Incorrect Configuration: The value assignment type or class may not have been configured correctly in the system.
  Missing Entries: The specific value assignment type/class may not exist in the database, possibly due to incomplete implementation or data migration issues.
  Typographical Errors: There may be a typo in the value assignment type/class name when it is being referenced in a transaction or program.
  Authorization Issues: The user may not have the necessary authorizations to access the value assignment type/class.
  
  
  Solution:
  
  
  Check Configuration:
  
  Navigate to the configuration settings for the EHS module and verify that the value assignment types/classes are correctly defined.
  Use transaction codes like SPRO to access the configuration