How To Fix CM_CBESCOM139 - UUID &1 is used in multiple exposure scenarios for product

CM_CBESCOM139 - Overview

• Message type: E = Error

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

• Message number: 139

• Message text: UUID &1 is used in multiple exposure scenarios for product

What causes this issue?

The system has determined that the UUID is also being used by the
(contributing) exposure scenario &V4& in the specification type <ZK>
exposure scenario header data</> (ES_HEAD) for the exposure scenario
&V2& in the value assignment instance &V3& of the product.

System Response

INCLUDE EHSPRC_ESCOM_ABBRUCH OBJECT DOKU ID TX

How to fix this error?

Check the exposure scenarios and contributing exposure scenarios
assigned to the product in value assignment type <ZH>Use and Exposure
Scenario</>
(SAP_EHS_1027_001):
If you have maintained several versions of an exposure scenario in the
product (the same UUID and different date timestamps), delete the
exposure scenario(s) with the older date timestamps.
If you have assigned the same UUID to different exposure scenarios by
mistake, you must exchange the <ZK>Exposure Scenario Header</>
(specification type ES_HEAD) assigned to the exposure scenarios on the
tab page <ZK>Specification Listing </>or you need to create and assign
new specifications with different UUIDs.

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.

CM_CBESCOM139 - Details

• The SAP error message CM_CBESCOM139 indicates that a specific UUID (Universally Unique Identifier) is being used in multiple exposure scenarios for a product. This typically occurs in the context of product compliance, where a UUID is expected to be unique to a single exposure scenario but is found to be associated with more than one.
  
  Cause:
  
  Duplicate UUID Assignment: The UUID assigned to a product's exposure scenario is not unique and has been reused in another scenario.
  Data Entry Error: There may have been a mistake during data entry or data migration, leading to the same UUID being assigned to multiple scenarios.
  System 
  Configuration Issues: There could be issues in the system configuration or data model that allow for the same UUID to be assigned to multiple scenarios.
  
  
  Solution:
  
  Identify Duplicate UUIDs: Use transaction codes like SE16 or SE11 to query the relevant database tables (e.g., tables related to exposure scenarios) to find where the duplicate