How To Fix /PLMPCV/QRM673 - Query &1: Unknown relation type &3 in attribute &2

/PLMPCV/QRM673 - Overview

• Message type: E = Error

• Message class: /PLMPCV/QRM -

• Message number: 673

• Message text: Query &1: Unknown relation type &3 in attribute &2

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 /PLMPCV/QRM673 - Query &1: Unknown relation type &3 in attribute &2 ?

  The SAP error message /PLMPCV/QRM673 indicates that there is an issue with a query related to a specific attribute in the SAP system. The message breaks down as follows:
  
  Query &1: This refers to the specific query that is being executed.
  Attribute &2: This indicates the attribute that is causing the issue.
  Relation type &3: This specifies the unknown relation type that is not recognized by the system.
  
  Cause
  The error typically arises due to one of the following reasons:
  
  Incorrect Configuration: The relation type defined for the attribute in the query may not be correctly configured or may not exist in the system.
  Data Model Issues: There may be inconsistencies or missing entries in the data model that the query is trying to access.
  Custom Development: If there are custom developments or enhancements in the system, they may not be properly aligned with the standard configurations, leading to this error.
  Version Compatibility: The query might be using features