How To Fix FDT_SERVICE072 - No matching column in new version for column &1 in old version.

FDT_SERVICE072 - Overview

• Message type: E = Error

• Message class: FDT_SERVICE - Formula & Derivation Tool: Services

• Message number: 072

• Message text: No matching column in new version for column &1 in old version.

What causes this issue?

A new version of a decision table collides with the current version,
that has been changed by customer on the runtime system. The current
version of the decision table contains a column that has no compatible
match in the new version.

System Response

The new version of the decision table contains incompatible changes and
can therefore not be deployed automatically.

How to fix this error?

Contact the owner of the decision table.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FDT_SERVICE072 - No matching column in new version for column &1 in old version. ?

  The SAP error message FDT_SERVICE072 indicates that there is a mismatch between the columns defined in the old version of a data structure and the new version. This typically occurs when there have been changes made to the data structure (like a table or a data model) that are not reflected in the corresponding version that is being accessed or used.
  
  Cause:
  
  Version Mismatch: The error usually arises when there is an attempt to access a data structure that has been modified (e.g., columns added, removed, or renamed) without updating the corresponding version in the system.
  Data Model Changes: Changes in the underlying data model or structure that are not properly synchronized with the application logic or data access layer.
  Transport Issues: If changes were transported from one system to another (e.g., from development to production) and the transport did not include all necessary updates.
  
  
  Solution:
  
  Check Data Structure Versions: Verify the versions of the data