Resources S/4HANA 2027

S/4HANA 2027: get value from your SAP data before the migration, and keep it after.

SAP ECC's mainstream maintenance ends on December 31, 2027, and about half of ECC-era customers had not moved by mid-2026 [1]. The usual decision is to wait: start the analytics, planning and archiving work after the migration. That costs two years and often means building things twice. This guide shows how to decouple three kinds of work from the migration so they deliver now and survive the cutover: reading ECC data in place, delivering planning datasets from ECC and later from S/4HANA, and moving history into an archive that stays readable. It ends with a 12-point readiness check.

THE 15 MONTHS IN WHICH PLANNING AND DATA WORK USUALLY WAITS2024Dec 20272024–2025S/4HANA programs planned or startedJun 9, 2026ODP RFC enforcement: extraction paths changeDec 2026ODP opt-out expiresDec 31, 2027ECC mainstream maintenance endsTODAY · SEP 2026
The clock. Two dates fall before the migration for most estates: the ODP restriction (June and December 2026) and the maintenance end (December 2027). The shaded band is the period in which planning and data work usually waits.
Dec 31, 2027
ECC mainstream maintenance ends
dated source [1]
~half
of ECC-era customers still on ECC, 18 months from the date
dated source [1]
95%
of SAP customers in one survey found the S/4HANA business case hard to make
dated source [2] · Nov 2025
56%
of supply-chain leaders name legacy integration the top blocker to scaling AI
dated source [3] · Apr 2026
22 days
from contract to production
showcase estate
Step 1: the trap

Waiting costs two years; migrating first means building twice.

If you wait. Analytics, planning integration and archiving start after go-live. Go-live slips; the work starts later still. Two years pass in which the business runs on spreadsheets and the planners work around the data.

If you build on ECC only. Reports, loads and archives are written against ECC tables. At cutover, MATDOC replaces the material document tables, ACDOCA replaces the ledger tables, PRCD_ELEMENTS replaces KONV, and everything built on the old names is rebuilt.

The way out. Build once on a layer that reads both. Lima's catalog maps ECC and S/4HANA objects to the same business terms; pipelines and questions are written against the terms. When the cutover comes, the connector changes and the mapping updates; the pipelines, the reports and the archive stay.

The three kinds of work below each deliver value now and keep it afterwards.

Step 2: read ECC in place, now

Questions, dashboards and a control tower without a copy.

The Data Fabric reads ECC through released interfaces alongside Oracle, the warehouse, the WMS and 3PL feeds, and answers questions in seconds with the access policy applied. A control tower with exceptions, KPIs and two governed agents reached production in 22 days on the showcase estate.

At cutover, the SAP connector points at S/4HANA and the catalog's mapping updates. The questions and the dashboards do not change.

The 22-day control tower pilot →

Step 3: deliver planning datasets from ECC, then from S/4HANA

The planning program stops waiting.

Kinaxis, o9, Blue Yonder, SAP IBP and OMP need a delivered dataset on the planning calendar. Lima Backbone builds it from ECC today through table reads via a released function module, BAPIs and change pointers, and returns the plan to ECC. After cutover, the same pipelines read S/4HANA through released CDS views and table reads, with the mapping updated in the catalog.

The first planning dataset is live in four weeks at a fixed price. Because the ODP RFC path is closed from December 2026, an extraction built on released interfaces now also avoids a second conversion later.

Planning integration → · The ODP RFC exit kit →

Step 4: move the history once, and keep it readable

Archive and retire on your schedule.

Years of ECC history do not all need to move into S/4HANA. Lima extracts the tables in scope in partitions with a count and control total per table, lands them in a lakehouse or object storage in Iceberg or Delta tables, and keeps them readable through the Fabric for auditors and analysts. When the ECC system is retired, its history is still a question away, and any table can be restored into a target on demand.

Legacy decommissioning → · Archiving and offload →

Step 5: the readiness check

Twelve questions.

A check that works on its own, whether or not Lima is involved.

What is the migration date, and how many times has it moved?The answer sizes the cost of waiting.
Which reports, loads and archives are written against ECC table names?Each is rebuilt at cutover unless it reads through a mapped layer.
Which extraction jobs use ODP over RFC?They stop in December 2026 regardless of the migration.
Which planning application is waiting for data?And how many planners are working around it meanwhile.
Do results return to the ERP today?Planned orders, requisitions, corrections; by hand or by interface.
Which ECC history must be kept, and for how long?Retention by table and by jurisdiction.
Who owns planning master data outside the ERP?Parameters, hierarchies and rules in spreadsheets need an owner and a version.
What is the run window for the planning load?The deadline on the planning calendar the load must meet.
How is a bad record handled today?Dropped, emailed, or routed to an owner with a deadline.
What does reconciliation look like today?Rows and totals per table, or a feeling.
What would the control tower show on day 22?The exceptions and the two agents that matter most.
What is measured before go-live?The baseline that makes the result provable.
Terms on this page

Plain meanings.

ECCSAP's previous ERP release; mainstream maintenance ends December 31, 2027.
S/4HANASAP's current ERP; some tables change (MATDOC, ACDOCA, PRCD_ELEMENTS).
CutoverThe moment the business moves from the old system to the new.
Mapped layerA catalog that maps each system's objects to business terms, so pipelines and questions are written once.
Released interfaceAn SAP interface SAP documents and supports for external use.
Questions

Asked about this guide.

Does building on ECC now waste money?

Only if what is built reads ECC table names directly. Built against the catalog's business terms, the reports, loads and archives survive the cutover with a mapping update.

Should the planning integration wait for S/4HANA?

The planners are working around the data now, and the ODP path closes in December 2026 either way. A first dataset from ECC in four weeks, on released interfaces, carries over.

What about SAP's own tools?

SAP's data services are sanctioned roads with their own licences; they land data in SAP's cloud first. The guide's point is to decouple the work from the migration; the tool choice follows from the estate.

Start before the migration, keep it after.

A control tower in 22 days, or a first planning dataset from ECC in four weeks. Either way, built once.