Skip to main content

Solutions

Law firms

Tax, audit & accounting firms

Corporations

Governments

Products

Legal

Trade & supply

Tax, audit & accounting

Corporate tax

Risk & fraud

Books

Recommended products

Questions? We are here to help.
Contact us

Purchase

Buy solutions

Buy books

Contact sales

Questions? We are here to help.

Resources

Insights

Events

Product training

Product communities

Developers

Topics

6.9.1.0 SAP S/4HANA 2025 Compatibility for Global Next Integration

Product:
 ONESOURCE Indirect Tax Integration for SAP – Global Next
Version:
 6.9.1.0
Published date
: December-2025.

Symptom

Upon upgrading an SAP system to S/4HANA 2025, customers may encounter syntax errors in ABAP objects within the
/IDT/
 namespace. These errors typically manifest as "Duplicate field UNPL_REFWR" and can cause activation failures or runtime short dumps (
SYNTAX_ERROR
), impacting processes that use the affected objects, particularly in Materials Management (MM).

Root Cause

The root cause is a field name collision between the SAP standard and the ONESOURCE integration.
  • In the S/4HANA 2025 release, SAP introduced a new field named
    UNPL_REFWR
     into a standard core data structure.
  • The ONESOURCE integration structure
    /IDT/MMCR_DRSEG_CO
     also contained a field with the same name.
When the system attempts to use a program that references both structures, the ABAP runtime detects a duplicate field declaration, which results in a syntax error.

Resolution

To resolve this conflict, Thomson Reuters has released a corrective transport that modifies the ONESOURCE structure
/IDT/MMCR_DRSEG_CO
 to eliminate the duplicate field. This modification ensures the ONESOURCE data dictionary objects are fully compatible with the SAP S/4HANA 2025 standard. We have tested this fix on S/4HANA 2025 Initial Shipment Stack.

Required Action

To prevent or resolve the syntax errors, customers must import the following corrective transport request:
Implementation Timing:
 This transport is flexible and can be imported according to one of the following scenarios:
  • Proactive (Recommended):
     Import the transport
    before
     executing the S/4HANA 2025 system upgrade. This will prevent the syntax errors from ever occurring.
  • Reactive:
     Import the transport
    after
     the S/4HANA 2025 upgrade is complete to correct any syntax errors that have appeared.
After importing the transport, ensure all relevant objects in the
/IDT/
 namespace are activated successfully.

This article applies to:

  • Product: ONESOURCE Indirect Tax
  • Sub-Product: SAP