How To Fix CM_EHDGM_API_CRR_TBR042 - &1, &2: Provided value "&3" for "Classified As" is not valid.

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHDGM_API_CRR_TBR - TBR Pattern-specific Messages for CRR API

• Message number: 042

• Message text: &1, &2: Provided value "&3" for "Classified As" is not valid.

What causes this issue?

You want to import classification data for a dangerous goods assessment
of an unpackaged product. However, the value that you have provided as
<LS>Classified As</> (&V3&) is not valid.

System Response

The system does not import the data.

How to fix this error?

Provide a valid dangerous good classification and start the import
again.
The values for the <LS>Classified As</> field for the dangerous goods
assessment of an unpackaged product must have one of the following
values:
01: Not Yet Classified
02: Dangerous Good
03: No Dangerous Good

Procedure for System Administrators

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_EHDGM_API_CRR_TBR042 - &1, &2: Provided value "&3" for "Classified As" is not valid. ?

  The SAP error message CM_EHDGM_API_CRR_TBR042 indicates that there is an issue with the value provided for the "Classified As" field in a specific transaction or API call. This error typically arises in the context of data classification or management, where the system expects a valid classification value but receives an invalid one.
  
  Cause:
  
  Invalid Value: The value provided for the "Classified As" field does not match any of the predefined or acceptable values in the system.
  
  Configuration Issues: The classification settings or values may not be properly configured in the system.
  Data Entry Error: There may have been a typographical error or incorrect data entry when specifying the classification value.
  Missing Values: The classification value may not have been set up in the system at all.
  
  
  Solution:
  
  Check Valid Values: Verify the list of valid values for the "Classified As" field. This can usually be found in the configuration settings or documentation related to the specific module