Pre-built ECC data conversion for FI, CO, MM, SD, PP, HR. Cluster-table decompression, Z-* custom inventory, BKPF/BSEG → FBDI GL crosswalks, HGB and SOX retention preserved. Row-level reconciliation signed off by Wirtschaftsprüfer.
The hard part isn't running an ABAP report into a CSV. It's translating ECC's 30-year-accreted data model — cluster tables, Z-* customisation, multi-ledger accounting, parallel currencies — into Fusion without losing audit substantiation.
SAP ECC presents a data model layered across three decades of evolution. Standard tables (KNA1, LFA1, MARA, BKPF, BSEG, EKKO, VBAK) are joined by hundreds to thousands of Z-* custom tables added by every implementation since 1995. Cluster tables (BSEG, BSET, RFBLG) compress line items into binary chunks. Parallel currencies (local, group, hard) live across BSEG fields and run independent posting trails. Multi-ledger setups (leading ledger 0L plus non-leading ledgers for IFRS, HGB, US GAAP) multiply every posting. Oracle Fusion's data model — Journal Headers and Lines on a single universal journal, TCA Parties for customers and suppliers, Items in PIM, the six-segment Chart of Accounts — is structurally cleaner but fundamentally different.
Every sap ecc data migration to Oracle Fusion has to bridge those gaps without breaking the audit chain that links a GL journal line back to its original purchase order, goods receipt and invoice. Custom ABAP, custom SQL and consultant whiteboards can do it — but every domain becomes a multi-month negotiation between FI controllers, MM leads, SD ops, Basis and external audit. Syntra ETL replaces that with pre-built crosswalks refined across dozens of ECC conversions.
The same engine handles four deployment scenarios: full ECC replacement (FI/CO/MM/SD/PP/HR → Fusion), finance-only conversion (FI/CO → Fusion Financials, supply chain stays on ECC for a phased migration), HCM-only conversion (HR → Fusion HCM with finance staying on ECC temporarily), and the M&A pattern (newly-acquired ECC entity collapses into the acquirer's existing Fusion tenant).
The transformations Syntra ETL ships pre-built. No custom ABAP, no bespoke SQL, no multi-month conversion build.
BSEG, RFBLG, BSET and other cluster tables decompressed via ABAP CDS, RFC line-item reads or SLT. Output is clean tabular — one row per line item with Z-* fields preserved.
Document headers + line items translated to Fusion GL Journal Headers/Lines, preserving doc-type, posting-key, profit-centre, segment dimensions and parallel-currency context across the COA crosswalk.
Customer (KNA1/KNB1/KNVV) and vendor (LFA1/LFB1/LFM1) master converted to Fusion TCA Parties + Customer/Supplier Accounts, preserving company-code-specific data and partner functions.
Material master converted to Fusion Items in PIM, with UoM conversion, valuation class mapping, plant assignment, batch-management and serial-number context preserved.
Z-* custom tables and append fields walked, classified by reporting materiality, routed to Fusion COA segments, core attributes, DFFs or analytical archive. Audit-signed routing decisions.
Leading ledger 0L plus non-leading IFRS/HGB/US-GAAP ledgers preserved across the migration with parallel-currency translation rates and historical-cost continuity for HGB §253.
A repeatable load order that respects Fusion's data dependencies. Skip a step and your BSEG load fails on missing GL accounts or unmapped suppliers.
Fusion enterprise structures, ledgers (one per ECC non-leading ledger), business units, COA segments, fixed-asset categories, item categories, payment terms, payment methods configured. Loaded via FSM tasks — downstream dependencies.
GL accounts (SKA1/SKB1 → Account segment values), TCA Parties + Customers (KNA1/KNB1/KNVV), Suppliers (LFA1/LFB1/LFM1), Items (MARA/MARC), Cost Centres (CSKS), Profit Centres (CEPC), Employees (HRP1000/PA0000) loaded in dependency order via FBDI/HDL.
Open AR (BSID), open AP (BSIK), open POs (EKKO/EKPO with status), open Sales Orders (VBAK/VBAP), open Goods Receipts/Inventory (MSEG), fixed assets with NBV (ANLA/ANLC) loaded via FBDI. Reconciled to ECC at the cent.
Closed GL line items (BSEG) for the operational reporting window (typically current FY + prior 2–7 FYs) loaded via FBDI GL Journal Import as period balances or full line-item detail per Fusion sizing. Older periods route to the ECC long-term archive.
SLT replication captures live ECC deltas during parallel-run; deltas replayed into Fusion via FBDI delta loads or Fusion REST APIs. PI/PO integrations cut over to Oracle Integration Cloud (OIC) in the same window.
Final reconciliation pack: ECC GL trial balance vs Fusion to the cent, AP/AR aging vs aging, fixed-asset register vs register, in local currency + group currency + hard currency. External audit and Wirtschaftsprüfer sign off. Production cut to Fusion only.
The pack that satisfies internal audit, SOX external audit, German Wirtschaftsprüfer and country tax authorities on day one.
ECC GL trial balance per company code per period vs Fusion GL trial balance — to the cent in local, group and hard currencies. Variance report by GL account with exception drilldown.
Open AR (BSID) and open AP (BSIK) aging from ECC vs aging from Fusion AR/AP. Item-by-item match, exception list for any aging-bucket variance.
ECC asset register (ANLA/ANLC) — APC, accumulated depreciation, NBV — vs Fusion FA. Per-asset match with depreciation-method continuity verified.
Every extract run produces a signed JSON manifest with row counts, sum totals and SHA-256 hashes per partition. Tamper-evident audit trail.
Every Z-* table and append field with its routing decision (Fusion segment / DFF / extension / archive / retire), business justification, and approver signature.
Combined evidence pack: reconciliation reports, Z-* register, customisation inventory, OIC integration test results, delta-replay log, ledger close certification. Single PDF for board sign-off.
SAP ECC data migration is the process of moving the full transactional and master-data footprint of an SAP ERP Central Component instance — GL postings (BKPF/BSEG), customer master (KNA1/KNB1/KNVV), vendor master (LFA1/LFB1), material master (MARA/MARC), purchase documents (EKKO/EKPO), sales orders (VBAK/VBAP), billing (VBRK/VBRP), goods movements (MSEG), fixed assets (ANLA/ANLC), cost centres (CSKS), HR infotypes (HRP1000/PA-series) — into Oracle Fusion ERP, SCM and HCM. The technical heart is cluster-table decompression, Z-* custom field capture and disciplined crosswalks into Fusion's six-segment COA, TCA model and HCM data model. Syntra ETL handles all of this with pre-built extractors covering direct-DB/BAPI/IDoc/ABAP CDS/SLT modes, plus Oracle-validated FBDI and HDL output emitters.
The terms get used interchangeably, but the distinction is operational: sap ecc data migration is the end-to-end project (extract + transform + load + reconcile + cutover), while conversion is the transformation layer specifically. Syntra ETL's ECC data conversion engine ships pre-built rules for BSEG→Fusion GL Journal Lines translation, BKPF doc-type to Fusion journal-source mapping, KNA1/KNB1→TCA Party + Customer Account conversion, LFA1/LFB1→Supplier conversion, MARA→Item conversion across UoM/categorisation, EKKO/EKPO→Purchase Order conversion, and Z-* custom field collapse into DFFs or COA segments. These are rules that on an SI-led programme would otherwise eat 4–6 months of bespoke ABAP and SQL development.
SAP cluster tables compress multiple logical rows into binary cluster records on the underlying database — opaque to plain SQL and the source of every junior consultant's first ECC migration disaster. Syntra ETL's ECC extractor handles decompression natively using whichever method the Basis team approves: ABAP CDS views (the modern default in ECC EHP7+) read decompressed line items via the SAP HANA SQL layer or OData; RFC calls invoke standard SAP function modules that return decompressed BSEG line items; SLT (SAP Landscape Transformation) handles cluster decompression at the source as part of replication. Output is a clean tabular dataset — one row per BSEG line item with full doc header context, custom Z-* field values and audit metadata — ready for Fusion FBDI GL Journal load.
Yes — and it is one of the most under-estimated parts of any ECC data migration. Mature ECC tenants typically have 800–4,000 Z-* custom tables and dozens of append structures bolted onto standard SAP tables (Z fields appended to BSEG, KNA1, MARA, etc.). Syntra ETL's discovery engine crawls DD02L/DD03L (ABAP Dictionary) to catalogue every Z-* table and append, identifies which fields drive material reporting or operational behaviour, and proposes routing: required Z-* fields collapse into Fusion COA segments or core attributes, optional fields route to Fusion DFFs or extension fields, analytical-only fields land in OTBI dimensions or in the long-term ECC archive. Every routing decision is auditable so external audit signs off on the cleanup.
Syntra ETL emits Fusion-native load formats for every ECC data domain: FBDI GL Journal Import for BKPF/BSEG, FBDI AR Invoice/AP Invoice Import for BSID/BSIK opens, FBDI Receivables Customer/Payables Supplier for KNA1/LFA1 master, FBDI Item Import for MARA, FBDI Purchase Order Import for EKKO/EKPO, FBDI Sales Order Import for VBAK/VBAP, FBDI Fixed Asset Import for ANLA/ANLC, and HDL Worker.dat plus assignment files for HR infotypes. Every payload is validated against the current Oracle Fusion 26x release schema before submission so validation errors surface locally — not in a 6-hour Fusion ESS job that fails on row 92,000 of a BSEG line-item file.
Every BKPF document and every BSEG line item extracted from ECC is hashed at source (doc hash + line-item hashes). Every record loaded into Fusion is re-hashed post-load. The reconciliation engine compares counts (documents, line items, master records), sum totals (GL debits/credits per company code per period in source currency and document currency), and hash signatures per business unit per period. Any record that fails Fusion validation is captured with the exact field-level reason for bulk fix. Output is a signed timestamped reconciliation pack: ECC GL trial balance vs Fusion GL trial balance to the cent in every reporting currency, AP/AR aging vs aging, asset register vs register. Internal audit, external audit and German Wirtschaftsprüfer sign off on the pack directly.
Yes. After the bulk historical load, Syntra ETL captures ECC deltas via SLT replication or modified-since watermarks on BKPF/MSEG/VBRP and replays them into Fusion through FBDI delta loads or Fusion REST APIs. This supports the standard 1–2 fiscal-month parallel-run where ECC continues taking live postings while Fusion is validated to the cent. Once finance leadership, controllers and external audit sign off, new postings cut to Fusion-only and the ECC tenant moves to read-only archive mode. The PI/PO integration estate cuts over to Oracle Integration Cloud (OIC) in the same window — country e-invoicing flows (Italian SDI, Brazilian SPED, Polish KSeF, etc.) re-pointed to Fusion.
SOX requires 7-year retention of financial records with auditable trace from GL entry back to source document. German HGB §257 plus AO §147 require 10-year retention (Aufbewahrungspflicht) of accounting records including original-document substantiation. IFRS, MiFID II (financial services), FDA 21 CFR Part 11 (pharma) and BaFin (German banking) impose additional sector retention. Syntra ETL's sap ecc data migration preserves the full chain: GL entry in Fusion → Fusion Journal Header → original BKPF doc number → original BSEG line-item with Z-* fields → original supporting document. Whether the supporting evidence lands in Fusion or in the long-term ECC archive, the read-access log is captured for SOX, HGB and country-specific audit evidence. No reconstruction needed when auditors arrive years later.
30-minute discovery call. We'll scope your ECC modules, Z-* customisation, cluster-table volume, parallel ledgers and country-specific retention obligations — and have a working extract running on your tenant within two weeks.