Deep-dive sap ecc financial data migration: BKPF/BSEG, multi-ledger preservation, parallel currencies, IFRS adjustment traceability, fixed-asset NBV reconstitution, HGB §253 historical-cost continuity. Reconciled to the cent in every reporting currency, signed off by Wirtschaftsprüfer.
Sap ecc financial data migration is not BSEG → FBDI. It's preserving multi-ledger fidelity, parallel-currency historical-cost continuity, IFRS adjustment traceability, fixed-asset NBV reconstitution and Wirtschaftsprüfer-grade audit evidence — domain by domain, currency by currency, ledger by ledger.
Sap ecc financial data migration is the deepest, most audit-sensitive domain of any SAP ECC to Oracle Fusion conversion. The technical surface area is large — BKPF / BSEG / BSID / BSAK / KNA1 / LFA1 / ANLA / ANLC / CSKS / CEPC plus parallel-currency fields plus multi-ledger replication plus CO-PA plus tax — but the real complexity is in the non-obvious requirements: preserving historical translation rates so HGB §253 lower-of-cost-or-market valuation survives the migration intact; preserving IFRS-only journal postings as a separately addressable source so external audit can reconstruct IFRS-vs-local-GAAP adjustments years later; preserving fixed-asset NBV per depreciation area per parallel currency per fiscal year so balance-sheet continuity is auditable; preserving aging-bucket reconciliation on open AR and AP to the cent at cutover.
Get any of these wrong and the consequences are material: HGB §253 audit findings if historical-cost basis is lost; IFRS restatement risk if adjustment trace is broken; balance-sheet discontinuity if fixed-asset NBV diverges; cutover delays if AR/AP aging won't reconcile. Syntra ETL ships pre-built sap ecc financial data migration crosswalks that handle every domain: multi-ledger preservation with one Fusion ledger per ECC ledger; parallel-currency historical-cost continuity per BSEG line item; IFRS adjustment routing as a discrete journal source; fixed-asset NBV reconstitution per area per currency per year; AR/AP aging-bucket reconciliation in source / document / group currencies.
The reconciliation rigour is the final test. Every BKPF document and every BSEG line item is hashed at source. Every record loaded into Fusion is re-hashed post-load. Reconciliation compares counts, sum totals per company code per period per ledger per currency, and hash signatures. Output is a Wirtschaftsprüfer-grade signed evidence pack: ECC GL trial balance vs Fusion GL trial balance to the cent in every reporting currency in every ledger; AP/AR aging vs aging in every currency; fixed-asset register vs register per depreciation area; IFRS adjustment summary with traceability. Internal audit, external audit and (in Germany) the Wirtschaftsprüfer sign off on the pack directly before cutover.
Each has a documented Syntra ETL crosswalk. Each is where naive SI-led migrations fail audit.
Leading ledger 0L + non-leading IFRS / HGB / US-GAAP each become a discrete Fusion ledger. Postings replicated 1:1. Reporting continuity per ledger preserved. External audit reviews per-ledger trial balance.
Every BSEG line item migrated with original local + group + hard + additional currency amounts at transaction date — not re-translated at cutover rate. HGB §253 historical-cost basis preserved per material per period.
IFRS-only journal postings, FI-SL Special Ledger entries, Z-* IFRS-classified docs all routed to a discrete Fusion journal source. Adjustment trace auditable years post-cutover for restatement defence.
ANLA + ANLB + ANLC + ANEK + ANEP combined to reconstitute every asset's NBV per depreciation area per parallel currency per fiscal year. Balance-sheet continuity audit-defensible.
Open AR (BSID) and open AP (BSIK) loaded as Fusion open invoices. Aging buckets (1-30, 31-60, 61-90, 91-120, 121+) reconciled to the cent in source + document + group currency at cutover.
Tax codes, jurisdictions, EU VAT one-stop-shop, Brazilian SPED, Italian SDI, Polish KSeF, Saudi ZATCA — country-statutory finance preserved with regulator transition pre-cutover.
The order Fusion expects. Skip a dependency and the load fails on missing master data.
Fusion enterprise structures: ledgers configured one-per-ECC-ledger, primary + reporting currencies per ledger, business units, COA segments, fixed-asset categories, item categories, payment terms (T052 → Fusion equivalent), tax regimes. Loaded via FSM tasks — every downstream wave depends on this.
GL accounts (SKA1/SKB1 → Account segment values), TCA Parties + Customers (KNA1/KNB1/KNVV → FBDI Receivables Customer), Suppliers (LFA1/LFB1/LFM1 → FBDI Payables Supplier), cost centres (CSKS), profit centres (CEPC). Master-data reconciliation in count + key-attribute level.
Open AR (BSID → FBDI AR Invoice Import), open AP (BSIK → FBDI AP Invoice Import), open fixed-assets with NBV (ANLA + ANLC → FBDI Fixed Asset Import). Aging-bucket reconciliation per company code per ledger per currency.
Closed BSEG line items (current FY + prior 2-7 FYs depending on operational reporting window) loaded via FBDI GL Journal Import as full line-item detail or period balances per Fusion sizing. Multi-ledger replication preserved. Parallel-currency continuity preserved.
SLT replication captures live ECC deltas during 1-2 fiscal-month parallel cycle. Deltas replayed into Fusion via FBDI delta loads. Both systems reconciled at fiscal month-end. Finance + audit observe.
Final Wirtschaftsprüfer-grade reconciliation pack issued. ECC GL trial balance = Fusion GL trial balance to the cent in every ledger every currency. AR/AP aging matches. Asset register matches. IFRS adjustments traceable. ECC moves to read-only archive; new postings to Fusion only.
The pack external audit signs off on before cutover. Every output is auditable, signed, timestamped.
Per ledger per company code per period in source + group + hard currency. ECC vs Fusion to the cent. Variance threshold 0.00 — not 'within materiality'. Signed by external audit.
Per company code per ledger per currency, in aging buckets 1-30 / 31-60 / 61-90 / 91-120 / 121+. ECC BSID vs Fusion open AR. Aging discrepancies investigated to root cause.
Per company code per ledger per currency, same aging buckets. ECC BSIK vs Fusion open AP. Payment-terms preservation verified. Partial-payment history preserved.
Per asset per depreciation area (book / tax / IFRS / HGB) per parallel currency. ECC ANLA+ANLC vs Fusion asset register. Historical cumulative depreciation preserved. HGB §253 basis intact.
Per fiscal period: IFRS-only postings catalogued, traced back to originating economic event (revenue-recognition IFRS 15, lease IFRS 16, financial-instruments IFRS 9). External auditor reproducibility verified.
Migration methodology document, reconciliation approach, hash-verification protocol, Z-* triage decisions. Internal audit + external audit + Wirtschaftsprüfer signatures captured and timestamped.
Sap ecc financial data migration covers the full finance footprint of SAP ECC FI/CO into Oracle Fusion Financials: BKPF/BSEG general ledger headers and line items, BSID/BSAD open and closed AR items, BSIK/BSAK open and closed AP items, KNA1/KNB1/KNVV customer master across global and company-code data, LFA1/LFB1/LFM1 vendor master, ANLA/ANLC/ANEK/ANEP fixed-asset register and value transactions, BKPF doc-type to Fusion journal-source mapping, CSKS cost centres, CEPC profit centres, CO-PA tables, parallel-currency configuration (local, group, hard, additional), multi-ledger structures (leading ledger 0L plus non-leading IFRS / HGB / US-GAAP ledgers), bank statement and electronic-bank-statement (FEBKO/FEBEP) reconciliation history, dunning levels, payment terms (T052), tax codes and jurisdictions. Syntra ETL ships pre-built crosswalks for every domain — no bespoke ABAP, no consultant whiteboard sessions, no 4-6 month transformation build.
This is the part that breaks naive ECC migrations. Mature ECC tenants typically run leading ledger 0L for local GAAP plus 1-3 non-leading ledgers (IFRS for group reporting, US-GAAP for SEC-listed subsidiaries, HGB for German entities) and 2-4 parallel currencies per ledger (local, group, hard, additional currency for hyperinflation jurisdictions). Every BSEG line item carries amounts in all parallel currencies, and every accounting event posts to every active ledger. Sap ecc financial data migration must preserve every ledger as a separate Fusion ledger configured with the right primary and reporting currencies, must preserve historical translation rates (so historical-cost continuity for HGB §253 lower-of-cost-or-market is auditable), and must preserve the linkage between leading and non-leading ledger postings so IFRS adjustments are traceable. Syntra ETL's pre-built ledger crosswalk handles all of this; loss of multi-ledger fidelity is a common SI-led failure mode.
IFRS adjustments in SAP ECC live across multiple mechanisms: ledger-specific postings to the non-leading IFRS ledger (typically ledger 1L or L1), Special Ledger (FI-SL) postings, classified Z-* document types that mark IFRS-only entries, and adjustment journals routed via specific posting keys. Sap ecc financial data migration must inventory every mechanism, preserve the IFRS-only postings as a separately addressable journal source in Fusion (typically a dedicated Fusion ledger with IFRS-only category), preserve the trace back to the originating economic event (e.g., revenue-recognition adjustment under IFRS 15 vs local-GAAP), and preserve the comparative period for IFRS reporting (typically 3+ years of comparatives for first-time adopters). Syntra ETL's IFRS preservation crosswalk handles all four mechanisms and produces a Wirtschaftsprüfer-audit-ready evidence pack of IFRS adjustments traceable end-to-end.
Fixed-assets (FI-AA) are the most operationally sensitive domain in sap ecc financial data migration because they directly drive depreciation expense, net book value (NBV) on the balance sheet, and tax depreciation reporting. The migration must preserve: ANLA (asset master) class assignments, capitalisation dates, useful-life parameters; ANLB (depreciation areas — typically book, tax, IFRS, HGB, supplementary) per asset; ANLC (asset values) cumulative depreciation and NBV per area per fiscal year; ANEK (asset transactions) every acquisition, retirement, transfer, depreciation event historical trail; ANEP (asset line items) supporting trail per transaction; insurance values, investment-support keys, parallel-currency asset values. Syntra ETL's fixed-asset crosswalk produces Fusion FBDI Asset Import payloads that preserve every depreciation area, every historical transaction and the full NBV reconstitution back to original capitalisation. Asset register reconciles to the cent in every reporting currency and every depreciation area.
Open AR (BSID — open customer items) and open AP (BSIK — open vendor items) are loaded into Fusion via FBDI AR Invoice Import and FBDI AP Invoice Import as 'open balance' invoices with original document date, due date, payment terms, partial-payment history if applicable, customer/supplier reference, and full audit trace back to the original ECC document number. Open positions must reconcile aging-bucket-by-aging-bucket between ECC and Fusion at cutover (1-30 days, 31-60, 61-90, 91-120, 121+ in source-currency, document-currency and group-currency). Closed items (BSAD/BSAK) from the operational reporting window (current FY + prior 2-7 FYs) are loaded as historical line items either as FBDI GL Journal posts or as period-balances per Fusion sizing guidance, with full traceability to ECC source documents. The sap ecc financial data migration cutover only proceeds when AR and AP aging reconciles to the cent.
HGB §253 (lower-of-cost-or-market valuation) requires that asset valuations and inventory valuations preserve historical-cost basis with continuity across fiscal years and across system migrations. A sap ecc financial data migration that loses historical-cost basis triggers HGB §253 audit findings and potentially restatements. Syntra ETL preserves continuity through three mechanisms: (1) every BSEG line item migrated with full parallel-currency amounts at original transaction date (not re-translated at cutover rate), (2) ANLC (asset values) historical cumulative depreciation preserved per depreciation area in every parallel currency, (3) Material Ledger (CKMI1 / CKM_CR) historical valuations preserved for HGB-relevant materials. Wirtschaftsprüfer evidence pack documents the historical-cost continuity explicitly with reconciliation per asset, per material, per parallel currency, per fiscal year. HGB §253 compliance survives the migration intact.
The sequence respects Fusion's data dependencies. Foundation (week 1) — Fusion enterprise structures, ledgers (one per ECC ledger), business units, COA segments configured via FSM. Master data (weeks 2-4) — GL accounts (SKA1/SKB1) loaded as Account segment values, TCA Parties + Customers (KNA1/KNB1/KNVV) via FBDI Receivables Customer, Suppliers (LFA1/LFB1/LFM1) via FBDI Payables Supplier, cost centres (CSKS) and profit centres (CEPC) loaded. Open transactions (weeks 4-6) — open AR (BSID), open AP (BSIK), open fixed-assets with NBV (ANLA/ANLC) loaded via FBDI. Historical GL (weeks 5-10) — closed BSEG line items for the operational reporting window loaded via FBDI GL Journal Import as period balances or full line-item detail. Delta wave (weeks 10-14) — SLT-replicated deltas during parallel-run replayed via FBDI delta loads. Cutover (weeks 14-16) — final reconciliation pack signed off, ECC switched to read-only, new postings flow to Fusion only.
Bank statement reconciliation history (FEBKO bank statement headers + FEBEP line items + EBKN bank account assignments) is migrated as historical context to support post-cutover bank reconciliation continuity. Active bank-account connections are re-established in Fusion Cash Management with the same bank account numbers, IBAN, SWIFT/BIC codes, and house-bank assignments. Open payment proposals (REGUH/REGUP) in flight at cutover are either cleared in ECC pre-cutover (preferred) or re-created in Fusion Payments. Treasury (FI-TR) positions — money-market deals, FX forwards, interest-rate swaps — are migrated if Fusion Treasury Cash Management is in scope, otherwise route to a treasury-system replacement. Sap ecc financial data migration thus covers not just GL and AR/AP but the full operational treasury context — bank statements reconcile post-cutover without lost history, treasury positions transition without value-date breaks.
30-minute discovery call. We'll examine your ledger setup, parallel-currency configuration, IFRS adjustment patterns, fixed-asset register and country-statutory footprint — and produce a sap ecc financial data migration plan that reconciles to the cent and that Wirtschaftsprüfer signs off on directly.