How To Fix CM_CBESCOM070 - Specification &3: Identifier with category &1 (type &2) does not exist

CM_CBESCOM070 - Overview

• Message type: E = Error

• Message class: CM_CBESCOM - Message Class for ESComXML Outbound Processing

• Message number: 070

• Message text: Specification &3: Identifier with category &1 (type &2) does not exist

Schirmnachricht Nummer 081
Diese Nachricht folgt auf Nachricht Nummer075

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

What causes this issue?

The system tried to generate an ESComXML file. This was not possible
because the identifier with category &V1& and type &V2& for substance
&V3& does not exist although this is a mandatory field.

System Response

How to fix this error?

Create the identifier with category &V1& and type &V2& for substance
&V3&.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CM_CBESCOM070 - Details

• The SAP error message CM_CBESCOM070 indicates that there is an issue with a specification identifier in the system. This error typically arises in the context of SAP's Environment, Health, and Safety (EHS) module or when dealing with product specifications in the SAP system.
  
  Cause:
  The error message "Specification &3: Identifier with category &1 (type &2) does not exist" suggests that the system is unable to find a specification that is expected to exist based on the provided parameters. The placeholders (&1, &2, &3) represent:
  
  &1: The category of the identifier (e.g., material, substance).
  &2: The type of the identifier (e.g., specification type).
  &3: The actual specification identifier that is being referenced.
  
  Common causes for this error include:
  
  The specification identifier does not exist in the database.
  The specification has been deleted or is inactive.
  There is a typo or incorrect entry in the specification identifier.
  The specification is not assigned to the correct category or type.
  
  
  Solution:
  To resolve this error, you