How To Fix FICO1355 - Reference condition type does NOT agree with Customizing (&1).

FICO1355 - Overview

• Message type: E = Error

• Message class: FICO1 -

• Message number: 355

• Message text: Reference condition type does NOT agree with Customizing (&1).

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 FICO1355 - Reference condition type does NOT agree with Customizing (&1). ?

  The SAP error message FICO1355, which states "Reference condition type does NOT agree with Customizing (&1)," typically occurs in the context of pricing or condition records in the SAP system, particularly within the Financial Accounting (FI) and Controlling (CO) modules. This error indicates that there is a mismatch between the condition type being referenced and the configuration settings in the system.
  
  Cause:
  
  Configuration Mismatch: The condition type being used in a transaction does not match the settings defined in the Customizing (SPRO) for that condition type. This could be due to changes made in the configuration that have not been reflected in the transaction data.
  Missing or Incorrect Condition Type: The condition type may not be properly defined in the system, or it may have been deleted or modified incorrectly.
  Inconsistent Data: There may be inconsistencies in the master data or transaction data that reference the condition type.
  
  
  Solution:
  
  
  Check Customizing Settings:
  
  Go to the SAP Customizing