How To Fix CM_EHFND_API_CRR005 - &1, &2: Composition type "&3" is not valid.

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHFND_API_CRR - Messages for Compliance Requirement Result API

• Message number: 005

• Message text: &1, &2: Composition type "&3" is not valid.

What causes this issue?

You want to import data for a compliance assessment. However, the value
that you have provided as composition type (&V3&) is not valid.

You can use the composition types that are specified in the Customizing
activity
<DS:SIMG.EHFND_PMC_CCI_CMPSTY>Specify Composition Types for Composition
Based on Substances</>.

System Response

The system does not import the data.

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?

Provide a valid composition type and start the import again.

If you want to use a composition type that has not yet been specified in
Customizing activity <LS>Specify Composition Types for Composition Based
on Substances</>, add the composition type to the Customizing activity
prior to importing the affected compliance assessment.

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 CM_EHFND_API_CRR005 - &1, &2: Composition type "&3" is not valid. ?

  The SAP error message CM_EHFND_API_CRR005 typically indicates that there is an issue with the composition type specified in your API call or configuration. This error is often encountered in the context of SAP's Enterprise Services or when working with the SAP Cloud Platform.
  
  Cause:
  The error message can be triggered by several factors, including:
  
  Invalid Composition Type: The composition type specified in the API call does not exist or is not recognized by the system.
  
  Configuration Issues: There may be a misconfiguration in the backend system or in the service definition.
  Data Model Changes: If there have been changes to the data model or the service definitions, the composition type may have been deprecated or modified.
  Authorization Issues: The user or service account may not have the necessary permissions to access the specified composition type.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Verify Composition Type: Check the composition type specified in your API call. Ensure