How To Fix OH072 - Group & is not unique

OH072 - Overview

• Message type: E = Error

• Message class: OH - Messages Group Maintenance

• Message number: 072

• Message text: Group & is not unique

What causes this issue?

You wish to process group &V1&, which is not unique.
A group is unique if it only contains each subgroup and each value
once. Value intervals may not overlap each other.

System Response

The system only allows the display of ambiguous groups (not
maintenance).

How to fix this error?

Re-create group &V1& as unique, or restrict processing to unique
subgroups within group &V1&.
To remove ambiguity, proceed as follows:
Choose Extras -> Ambiguity check. The system displays all of the groups
and values which occur more than once, and all overlapping values.
Remove these groups, values, and overlapping values by processing the
affected groups directly.
If the standard hierarchy is affected, the compare function enables you
to compare the master data (Extras menu).
Once all the ambiguities are removed, it is possible to process group
&V1& again.

Error message extract from SAP system. Copyright SAP SE.

OH072 - Details

• The SAP error message OH072 "Group & is not unique" typically occurs in the context of SAP when there is an attempt to create or modify a master data record (such as a cost center, profit center, or other organizational units) that involves a group or category that is not uniquely identifiable. This can happen in various modules, including Controlling (CO) or Financial Accounting (FI).
  
  Cause:
  
  Duplicate Entries: The most common cause of this error is that there are multiple entries in the database for the same group or category. This could be due to incorrect data entry or a lack of proper data governance.
  
  Configuration Issues: There may be issues in the configuration settings that allow for non-unique identifiers to be created or recognized.
  Data Migration Issues: If data has been migrated from another system, it is possible that duplicates were introduced during the migration process.
  
  
  Solution:
  
  
  Check for Duplicates: 
  
  Use transaction codes like SE16