Embedded Foreign Trade Retired in Favour of GTS

Classic ECC behaviour

S/4HANA behaviour

Project impact

• Custom ABAP reports that read old Foreign Trade tables or the legal control status field on the sales document return empty results after conversion, and this is frequently misread as a data issue rather than a functional gap.
• Order-to-cash cycle time increases because every order or delivery now makes a round trip to an external GTS system for screening, which introduces network and batch latency that was not present when the check ran inline.
• Authorisation roles built around the old Foreign Trade transactions become dead weight; compliance staff instead need GTS access, which is a different authorisation model entirely.
• Export compliance and trade finance teams lose letter of credit tracking inside SD with no automatic substitute, forcing a manual or third-party workaround if GTS scope does not cover it.
• Month-end statistical reporting for intrastat and extrastat can break silently if commodity code maintenance was assumed to be handled by the old Foreign Trade config rather than material master classification data feeding GTS.
• Warehouse and shipping teams see orders sitting in a blocked state for longer, or blocked with less visible reason codes, if the GTS integration is not fully mapped to the old legal control messages users were used to seeing.

Migration actions

• Treat the assessment of current embedded Foreign Trade usage as a pre-conversion gate: identify every process using legal control, license determination, preference processing or letter of credit functionality before any technical conversion work starts.
• Confirm whether GTS is already present anywhere in the landscape; if not, initiate GTS procurement and implementation as a parallel project, since its lead time frequently exceeds the S/4 technical conversion timeline and can become the critical path.
• Migrate and cleanse legal control master data, denied party lists and classification data into GTS rather than assuming it carries over automatically from ECC.
• Rebuild custom reports and interfaces to source document block status and classification data from the GTS integration layer instead of the retired Foreign Trade tables.
• Test the full blocked-document workflow end to end under realistic order volume, including the round trip to GTS and back, before cutover, not just with a handful of test orders.
• Redesign authorisation roles for compliance staff around GTS rather than trying to preserve the old Foreign Trade transaction-based roles.
• Formally decommission the old Foreign Trade IMG configuration once GTS is confirmed live, so no one assumes it is still doing anything.

Whose problem this is

Common pitfalls

• Assuming embedded Foreign Trade is optional legacy functionality that can simply be dropped, then discovering during audit or an actual export event that no substitute compliance check exists in the new system.
• Underestimating the GTS implementation timeline against the S/4 conversion date, leading to a go-live where compliance checks are either missing or run on a rushed, under-tested configuration.
• Screening latency that looks acceptable in test with a handful of orders but creates a visible backlog of blocked documents at month-end order volume, when GTS is under load and staff try to manually release orders to hit shipping deadlines.
• Custom reports that go quietly empty rather than throwing an error, which gets reported as a data quality issue and burns investigation time before someone recognises the underlying table is retired.
• Loss of inline landed cost, duty or preference calculation that was previously visible on the order, with no one noticing until a customer disputes a duty amount weeks after shipment.