How To Fix CM_CBESCOM_INB179 - Exposure scenario header data &1 has incorrect specification type &2

CM_CBESCOM_INB179 - Overview

• Message type: E = Error

• Message class: CM_CBESCOM_INB - Message Class for ESComXML Inbound Processing

• Message number: 179

• Message text: Exposure scenario header data &1 has incorrect specification type &2

What causes this issue?

The system has determined specification &V1& with the specification type
&V2& from the ESComXML file for the exposure scenario.
Exposure scenario header data must be assigned only specifications with
the specification type &V3&.

System Response

INCLUDE EHSPRC_ESCOM_INB_STOP OBJECT DOKU ID TX

How to fix this error?

Change specification &V1& in <DS:TRAN.CG02>specification management</>:
Change the following identifiers:
UUID (NUM ES_UUID)
Version date (NUM ES_DT_STMP)
If you no longer use specification &V1&, you can delete it.
INCLUDE EHSPRC_ESCOM_CONTACT OBJECT DOKU ID TX

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_CBESCOM_INB179 - Exposure scenario header data &1 has incorrect specification type &2 ?

  The SAP error message CM_CBESCOM_INB179 indicates that there is an issue with the specification type in the exposure scenario header data. This error typically arises in the context of SAP's Environment, Health, and Safety (EHS) module, particularly when dealing with chemical substances and their exposure scenarios.
  
  Cause:
  The error message CM_CBESCOM_INB179 is triggered when the specification type defined in the exposure scenario header does not match the expected or valid specification types for the given context. This could be due to:
  
  Incorrect Configuration: The specification type may not be correctly configured in the system.
  Data Entry Error: There may be a typo or incorrect value entered in the specification type field.
  Missing Master Data: The specification type may not exist in the master data or may not be properly linked to the exposure scenario.
  Versioning Issues: If there are multiple versions of the exposure scenario, the wrong version may be referenced.
  
  
  Solution:
  To resolve this error, you can