How To Fix EI260 - Settings for incompletion and for field control do not match

EI260 - Overview

• Message type: E = Error

• Message class: EI - Foreign Trade: Gen. Output

• Message number: 260

• Message text: Settings for incompletion and for field control do not match

What causes this issue?

The combination of data for checking incompletion and field control is
inconsistent.

System Response

The system issues a warning.

How to fix this error?

Check your entry.

How can this happen?

An example of an inconsistent entry would be setting the incompletion
check for a field in a declaration type but to set the field control to
' ' or '0' so that the field is hidden during maintenance transactions.
An example of an unsuitable combination would be to set field control
to '2' so that the field is obligatory during the maintenance
transactions but not to select this field for the declaration type so
that is not checked during document selection.
In addition, if the on-line system response field is maintained with
'E' but not selected for an incompletion check for the declaration
type, a warning is issued.
A warning is also issued if the system checks for incompletion in one
goods direction only, for example, export, but the field control has
been maintained as an obligatory field for import documents as well.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EI260 - Settings for incompletion and for field control do not match ?

  The SAP error message EI260, which states "Settings for incompletion and for field control do not match," typically arises when there is a mismatch between the settings for field control and the incompletion log in the SAP system. This can occur in various contexts, such as during the creation or modification of master data, sales orders, or other transactional data.
  
  Cause:
  
  
  Incompletion Log Settings: The incompletion log settings for a particular transaction or master data object may not align with the field control settings. For example, if a field is marked as mandatory in the field control settings but is not included in the incompletion log, this inconsistency can trigger the error.
  
  
  Field Control Configuration: The configuration for field control (which determines whether a field is optional, mandatory, or hidden) may not be properly set up in the relevant customizing settings.
  
  
  Custom Development: If there are custom developments or enhancements in the system that