How To Fix FICO1173 - Reference condition type &1 does not exist or not allowed

FICO1173 - Overview

• Message type: E = Error

• Message class: FICO1 -

• Message number: 173

• Message text: Reference condition type &1 does not exist or not allowed

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 FICO1173 - Reference condition type &1 does not exist or not allowed ?

  The SAP error message FICO1173, which states "Reference condition type &1 does not exist or not allowed," typically occurs in the context of pricing or condition records in the SAP FICO (Financial Accounting and Controlling) module. This error indicates that the system is unable to find a specified reference condition type, which is necessary for processing pricing or conditions in transactions.
  Causes:
  
  Non-Existent Condition Type: The specified condition type does not exist in the system. This could be due to a typo or an incorrect reference.
  
  Configuration Issues: The condition type may not be properly configured in the system. This includes missing settings in the pricing procedure or condition records.
  Authorization Issues: The user may not have the necessary authorizations to access or use the specified condition type.
  Incorrect Assignment: The condition type may not be assigned correctly in the pricing procedure or may not be allowed in the context of the transaction being processed.
  
  Solutions:
  
  Check