How To Fix UGMD086 - Attribute &3 is contained in both DataStore objects

UGMD086 - Overview

• Message type: E = Error

• Message class: UGMD - FIN Master Data: Messages

• Message number: 086

• Message text: Attribute &3 is contained in both DataStore objects

What causes this issue?

The two ODS objects &V1& and &V2& are assigned to combination
characteristic &V4& for time-dependent and time-independent attributes.
Attribute &V3& is contained in <ZH>both</> ODS objects. As a result, the
attribute's dependency on time is <ZH>undetermined</>.

System Response

If you create or change a <DS:GLOS.3C14A7065A82D511B1250008C784EFB1>data
basis</>: the data basis is not saved.
If you subsequently change the ODS object: errors while reading data
from, and writing data to, the combination characteristic &V4& are
possible. Runtime errors are also possible.

How to fix this error?

You have two options:
Delete the attribute &V3& from one of the two mapped ODS objects.
Assign different ODS objects to combination characteristic &V4& in which
the attributes do not overlap.

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 UGMD086 - Attribute &3 is contained in both DataStore objects ?

  The SAP error message UGMD086 indicates that there is a conflict due to the same attribute being present in two different DataStore Objects (DSOs) within the same InfoProvider. This can occur during data modeling or when trying to load data into a DSO where the system detects that the same attribute is defined in multiple places, leading to ambiguity.
  
  Cause:
  The error arises when:
  
  Two DataStore Objects (DSOs) have the same attribute name (e.g., Attribute &3).
  The system is unable to determine which DSO's attribute should be used for processing or reporting.
  This can happen during data extraction, transformation, or loading processes where the attributes are expected to be unique.
  
  
  Solution:
  To resolve the UGMD086 error, you can take the following steps:
  
  
  Identify the DSOs: Determine which two DataStore Objects are causing the conflict. You can do this by checking the data model or the InfoProvider configuration.
  
  
  Rename Attributes: If possible, rename one of the conflicting attributes in one