How To Fix COM_PRCAT067 - Relationship type &2 is already being used in category hierarchy &1

SAP Error Message - Details

• Message type: E = Error

• Message class: COM_PRCAT - Product Category

• Message number: 067

• Message text: Relationship type &2 is already being used in category hierarchy &1

What causes this issue?

Each relationship type can only be assigned to one hierarchy per
product type. This means the following:
You can assign a relationship type to several categories within one
hierarchy.
You can assign a relationship type to two categories in different
hierarchies if these categories have different product types.
You cannot assign a relationship type to two categories in different
hierarchies if these have the same product type.

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message COM_PRCAT067 - Relationship type &2 is already being used in category hierarchy &1 ?

  The SAP error message COM_PRCAT067 indicates that there is an issue with the relationship type being used in a category hierarchy. Specifically, it means that the relationship type you are trying to assign or modify is already in use within the specified category hierarchy. This can occur when you attempt to create or change a relationship between categories in the SAP system, but the relationship type is already associated with another category or is being used in a way that conflicts with your current action.
  
  Cause:
  
  Duplicate Relationship: The relationship type you are trying to use is already assigned to another category in the hierarchy.
  Incorrect Hierarchy Structure: The structure of the category hierarchy may not allow for the relationship type to be reused in the way you are attempting.
  Data Integrity Constraints: SAP enforces certain constraints to maintain data integrity, and this error is a result of those constraints being violated.
  
  
  Solution:
  
  
  Check Existing Relationships: