A purpose-built ETL platform for SAP S/4HANA to Oracle Fusion migration — Finance, SCM, PPM, and EAM. HANA-aware extractors, CDS view and OData consumption, BAPI bridges, FBDI/HDL emitters. 40–60% faster than SI-led, and the HANA licence cost stops at cutover.
Most SAP S/4HANA to Oracle Fusion migrations fail in the COA translation, ABAP/CDS inventory, and integration re-engineering — not in extract or load.
SAP S/4HANA customers carry a deceptive accumulation of complexity: ABAP Z-reports built across decades of ECC heritage, CDS view extensions layered on top of standard Core Data Services, BAdI implementations on hundreds of enhancement spots, IDoc partner profiles for B2B EDI, and ABAP CAP services running on BTP. SI-led migrations spend the first four to six months just cataloguing what exists. By the time real ETL work starts, half the budget is already gone.
Syntra ETL inverts the sequence. Pre-built HANA extractors for every delivered table mean week-one extraction. A discovery engine that crawls the ABAP repository (TRDIR, TADIR), the CDS catalog, the BAdI registry, and the IDoc partner directory produces a complete customisation inventory in days, not months. The conversation that consumed the first six months of every traditional project now happens in week three, with hard evidence on the table.
Whether you're migrating Finance only, both Finance and SCM, or running the full enterprise stack across FI/CO/MM/SD/PP/PS/EAM, the same engine handles the workflow — with the same reconciliation rigor, the same audit trail, and the same emission to FBDI/HDL/REST formats that Oracle Fusion 26x natively consumes.
And how the Syntra ETL platform addresses each one — before they consume your timeline.
BKPF/BSEG carries GL account + cost centre + profit centre + WBS + internal order + functional area. Syntra ETL's analyser surfaces which dimensions drive material splits and collapses to Fusion's fixed 6-segment design, with the rest routed to DFFs or PPM dimensions.
Discovery crawls TRDIR, TADIR, CDS catalog, BAdI registry, ABAP CAP services. Every customisation gets a Fusion-equivalence recommendation: native, Page Composer, VBCS, OIC, or retire. Typical outcome: 35–55% retired outright.
Customers carry £500K–£3M/year in HANA database licence and RISE infrastructure cost. Syntra ETL targets day-one offload — the HANA licence stops at Fusion cutover, not 18 months later as in typical SI engagements.
Legacy artifact inventory, business-value classification, and Fusion-equivalent rebuild plan (OTBI, BI Publisher, FRS, Smart View). 50–70% of legacy reports are retired during cleanup; only the critical ones get rebuilt.
Every IDoc partner profile, BAPI consumer, and OData service consumed by S/4HANA gets re-pointed to Oracle Integration Cloud (OIC) connections, REST endpoints, or ESS-scheduled file feeds — with cut-over orchestration so upstream/downstream systems never lose a beat.
Decades of BKPF/BSEG don't all need to land in Fusion. The archival path puts cold periods in queryable cloud storage with auditor-grade access — satisfying German HGB/AO 10-year retention without paying HANA in-memory rates for cold data.
A repeatable, governed workflow built for S/4HANA's particular complexity. Typical multi-pillar timeline: 14–22 weeks.
Discovery engine crawls TRDIR/TADIR (ABAP repository), the CDS view catalog, the BAdI registry, IDoc partner profiles, the SAP Cloud Integration tenant, and Fiori app catalog. Output: a complete customisation inventory, account-assignment usage analysis, integration-surface map, and sized migration assessment with risk register.
SAP account assignment → Fusion 6-segment COA design, vendor/customer/material de-duplication rules, DFF routing decisions, cost centre and profit centre hierarchy mappings. Reviewed and signed off by finance, CO, and SCM functional leads. ABAP retire/replace decisions logged.
Pre-built HANA extractors pull BKPF/BSEG, KNA1/LFA1, MARA/MARC, EKKO/EKPO, VBAK/VBAP and all dependent tables in parallel. CDS views consumed for cloud-restricted instances. Output staged as Parquet with row hashes and partition manifests.
Crosswalks applied, SAP account assignments collapsed to Fusion COA, DFFs populated, FBDI/HDL/REST payloads generated, validated against Fusion 26x release templates. Errors surfaced locally with row-level diagnostics.
FBDI ZIPs and HDL bundles submitted to Fusion ESS, monitored to completion, reconciled at row, sum, and hash level. In parallel, critical OTBI and BI Publisher reports rebuilt and validated against SAP equivalents.
1–2 close cycles in parallel (S/4HANA + Fusion), deltas captured and replayed, reconciled to the cent, sign-off pack issued. S/4HANA moves to archive-only and HANA licence is released; production traffic now flows to Fusion.
No more bespoke ABAP downloads or HANA SQL scripts. Just configure scope, run, reconcile.
BKPF, BSEG, ACDOCA (universal journal), ACDOCP (plan data), SKA1/SKAT (GL master), T001 (company codes), T009 (fiscal year variants). Full account assignment context preserved, period-by-period reconciliation built in.
LFA1, LFB1, LFM1, LFBK (vendor master + bank), PAYR (payment), open AP from BSIK/BSAK. Open-invoice migration with full payment-status, withholding-tax, and approval-state context.
KNA1, KNB1, KNVV, KNBK, open AR from BSID/BSAD, dunning history. Open-invoice aging preserved, dunning level translation applied during extract.
MARA, MARC, MARD, MBEW (valuation), MCHB (batches), MSEG (movement), EKKO, EKPO (PO header/item). Multi-plant, multi-storage-location context preserved end-to-end.
VBAK, VBAP, VBRK, VBRP (billing), LIKP, LIPS (delivery), KONV (conditions). Open orders, open deliveries, billing-due-list state migrated to Fusion Order Management context.
ANLA, ANLB, ANLC (asset master/values/cumulative), AFKO, AFPO (production orders), EQUI, IFLOT (equipment/functional location). Asset book translation and depreciation key remapping built in.
A typical SAP S/4HANA to Oracle Fusion migration covering Finance (FI/CO) plus SCM (MM/SD), 8–12 years of history, and 2–4 TB of HANA source data runs 14–22 weeks with Syntra ETL versus 14–24 months with traditional SI-led delivery. Finance-only cutovers complete in 12–18 weeks; single-pillar SCM in 10–14 weeks. The acceleration comes from pre-built HANA extractors targeting BKPF/BSEG, KNA1/LFA1, MARA/MARC, EKKO/EKPO and VBAK/VBAP, plus CDS view consumption, OData service connectors, and BAPI/RFC bridges. Crosswalks for SAP COA (chart of accounts + cost centre + profit centre) to Oracle Fusion's 6-segment COA are pre-built. FBDI for Financials and HDL for HCM are emitted natively against the current Fusion 26x release.
Customers move from SAP S/4HANA to Oracle Fusion for four reasons we hear repeatedly. First, HANA licence costs: in-memory HANA database licensing alone can exceed £1M/year for mid-to-large customers, and RISE with SAP bundles that cost into a subscription that escalates 8–12% annually. Second, post-M&A standardisation: an Oracle-aligned parent inheriting a SAP S/4HANA subsidiary consolidates onto Fusion to avoid running two ERP stacks. Third, S/4HANA Cloud Public Edition limitations: customers find the multi-tenant variant too restrictive for their COA design or close process. Fourth, ABAP/CDS customisation burden: the cost of maintaining ABAP extensions, CDS view extensions, and BAdI implementations across S/4HANA upgrade cycles outweighs the cost of moving to Fusion's lower-customisation model.
Syntra ETL supports SAP S/4HANA to Oracle Fusion migration across all enterprise modules. Finance: FI (General Ledger, AP, AR), CO (Cost Centre Accounting, Profit Centre Accounting, Internal Orders, COPA), FSCM (Credit/Collections/Dispute), Treasury, Asset Accounting (FI-AA). SCM: MM (Materials Management, Purchasing, Inventory), SD (Sales & Distribution, Pricing, Billing), PP (Production Planning), QM (Quality), WM/EWM (Warehouse). Project Systems (PS) → Fusion PPM. Plant Maintenance / Enterprise Asset Management (PM/EAM). HCM (rarely on S/4HANA — most customers use SuccessFactors) is supported when present. Both S/4HANA on-prem and S/4HANA Cloud Private Edition (RISE with SAP) are supported via the same extraction layer.
SAP uses a flexible account-assignment model: GL account + cost centre + profit centre + WBS element + internal order + functional area + segment + business area. Oracle Fusion uses a fixed 6-segment COA. Syntra ETL's mapping engine analyses BKPF/BSEG journal-line postings to identify which SAP assignment fields actually drive material reporting, proposes a Fusion 6-segment design that fits the analytic intent, and routes residual SAP fields to Fusion DFFs or PPM dimensions. Profit-centre hierarchies (KE5Z) and cost-centre hierarchies (KS13) are flattened into Fusion segment-value hierarchies. Every mapping is reviewed and signed off by finance and CO leads before any FBDI load runs.
ABAP code itself doesn't migrate — Fusion has no ABAP runtime. What Syntra ETL does is inventory every ABAP report (Z*/Y* programs), CDS view extension, BAdI implementation, user exit, and SAP Cloud Application Programming model service in the source S/4HANA instance, classify each by business purpose, and produce a Fusion-equivalent recommendation: native Fusion functionality, Fusion Page Composer, Visual Builder Cloud Service (VBCS), Oracle Integration Cloud (OIC) flow, or BI Publisher report. Customers typically find 35–55% of ABAP customisations are redundant under Fusion's native capabilities and can be retired. The remaining 45% get re-implemented in Fusion-native tooling — not translated line-by-line, which would be both impossible and undesirable.
Fiori UI, classic SAP GUI transactions, ABAP report output, and SAC dashboards don't carry over to Fusion. The Syntra ETL assessment phase inventories every report and analytical artifact in production use, classifies by business value, and proposes Fusion replacements: OTBI dashboards for ad-hoc analytics, BI Publisher for pixel-perfect operational reports, Fusion Financial Reporting Studio for management reporting, and Smart View for Excel-tethered analysis. About 50–70% of legacy Fiori apps and ABAP reports turn out to be duplicates or low-value and get retired. The remaining critical reports are rebuilt in Fusion-native tooling during the migration window, not after — go-live includes the reporting layer.
Syntra ETL's HANA extractors parallelise across company code (BUKRS), plant (WERKS), fiscal year and document number ranges, restart cleanly on failure, and stage Parquet to cloud object storage. The largest BSEG extract our customers run is 4.2 billion rows; the largest BKPF is 1.6 billion. Extracts use HANA SQL where direct DB access is available, CDS views where customers prefer the application-layer interface, OData services for cloud-hosted RISE environments, and BAPIs/RFC for legacy access. A typical billion-row extract completes in 5–8 hours. Outputs include hash signatures, manifest files with row counts and sum totals per partition, and an audit log of every read operation — ready for SOX, IFRS, German HGB/AO and BaFin control evidence.
No. Syntra ETL's HANA extractors run as a read-only HANA database user (or via CDS views with appropriate authorisations for RISE-hosted instances where direct DB access is restricted). Extracts are throttled to avoid contention with online users and the nightly batch window. For the largest tables, extracts can be scheduled during the SAP batch window, or pulled from a HANA system replication secondary to eliminate any production impact. No ABAP code changes, no S/4HANA upgrade prerequisite, no BAdI development, no Basis-team intervention beyond initial user provisioning.
Book a 30-minute discovery call. We'll walk through your S/4HANA modules, HANA footprint, ABAP/CDS customisation profile, and target Fusion pillars — and give you a concrete timeline and budget before the call ends.