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

SAP Error Message - Details

• 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 structure in question. Ensure that the version you are trying to access is the correct one and that it matches the expected structure.
  Update Data Model: If there have been changes to the data model, ensure that all dependent objects (like views, programs, or reports) are updated to reflect these changes.
  Rebuild or Refresh: If applicable, rebuild or refresh the data structure in the system to ensure that all versions are synchronized.
  Transport Consistency: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included and that there were no errors during the transport process.
  Consult Documentation: Review any documentation related to the changes made to the data structure to understand the implications and ensure that all necessary updates have been made.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Debugging: If you have access to debugging tools, you can trace the execution to see where the error is being triggered and gather more context about the mismatch.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis or development team for further investigation.