How To Fix FDT_CHANGE_INFO229 - Exclusion sign was set to "Allowed"

FDT_CHANGE_INFO229 - Overview

• Message type: E = Error

• Message class: FDT_CHANGE_INFO - FDT: Changes info in object for different versions

• Message number: 229

• Message text: Exclusion sign was set to "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 FDT_CHANGE_INFO229 - Exclusion sign was set to "Allowed" ?

  The SAP error message FDT_CHANGE_INFO229 with the description "Exclusion sign was set to 'Allowed'" typically occurs in the context of the SAP Financial Data Management (FDM) or related modules where data validation rules are applied. This error indicates that there is a conflict in the configuration of exclusion signs for certain data entries.
  
  Cause:
  The error arises when a data entry or a rule is configured in such a way that it allows certain values to be included, but the system has detected that these values should actually be excluded based on the defined rules. This can happen due to:
  
  
  Configuration Issues: The settings for exclusion signs in the data validation rules may not be aligned with the intended logic.
  Data Entry Errors: Incorrect data entries that do not comply with the established rules can trigger this error.
  Rule Conflicts: Conflicting rules that allow certain entries while others exclude them can lead to this error.
  
  
  Solution:
  To