How To Fix STEP972 - Create COND: Relationship &1 found

SAP Error Message - Details

• Message type: E = Error

• Message class: STEP - ISO 10303 STEP Mapping Messages

• Message number: 972

• Message text: Create COND: Relationship &1 found

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message STEP972 - Create COND: Relationship &1 found ?

  The SAP error message "STEP972 Create COND: Relationship &1 found" typically occurs in the context of condition records or pricing procedures in SAP. This error indicates that there is an issue with the creation of a condition record due to an existing relationship that conflicts with the new entry you are trying to create.
  
  Cause:
  
  Existing Condition Record: The error suggests that there is already a condition record with the same key or relationship that you are trying to create. This could be due to duplicate entries or an attempt to create a condition that is not allowed based on the existing data.
  Incorrect Configuration: The pricing procedure or condition type may not be configured correctly, leading to conflicts when trying to create new conditions.
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that are causing the system to reject the new condition.
  
  
  Solution:
  
  Check Existing Condition Records: Use transaction codes