Deep-dive finance migration: ACDOCA universal journal decomposition, BKPF/BSEG legacy GL, KNA1/KNB1 customer, LFA1/LFB1 vendor, ANLA/ANLC asset, CSKS cost-centre, CEPC profit-centre, BSET tax, full controlling. Triple-layer reconciliation. Penny-perfect trial balance.
Finance migration carries the highest blast radius in any S/4HANA-to-Fusion programme. Every other workstream can be partially recovered after go-live. Finance cannot.
If procurement migration has a gap, you can manually re-key the missing POs. If HCM migration has a gap, you can re-key the missing employees. If reporting migration has a gap, you can rebuild the missing reports post-cutover. None of these mistakes ends careers. SAP S/4HANA financial data migration is different — if the trial balance doesn't reconcile to the penny on day one of cutover, finance cannot close the books, the external auditors flag the period as unreliable, the SEC/regulator filings are delayed, and the CFO has a very public problem.
The discipline that protects finance migration is triple-layer reconciliation, run three times. Row-count parity, financial parity, dimensional parity — each layer catches a different class of defect. Three sequential mock migrations (at -90 days, -45 days, -7 days from go-live) prove the reconciliation is reproducible. Any variance at the third mock is a no-go signal. Syntra ETL's SAP S/4HANA financial data migration discipline is built around this — every mapping decision, every transformation rule, every load script is engineered to be auditable, repeatable, and reconcilable.
The structural challenge specific to S/4HANA is the universal journal (ACDOCA). It carries GL + CO + asset + material-ledger data in one table with hundreds of columns. Oracle Fusion uses a separated architecture (GL, SLA, Cost Management, Asset Tracking). SAP S/4HANA financial data migration decomposes each ACDOCA row into its constituent Fusion targets while preserving full traceability — every Fusion record carries the source ACDOCA document and line number so audit-trail is end-to-end.
Each domain has its own SAP source tables, Fusion target structure, mapping logic, and reconciliation rule.
ACDOCA + BKPF/BSEG → Fusion GL_JE_LINES, GL_BALANCES. Decomposition preserves every account assignment dimension. Trial balance reconciled per company code per currency.
Open AP from BKPF/BSEG + REGUP + PAYR → Fusion AP_INVOICES, AP_PAYMENT_SCHEDULES. Vendor (LIFNR) → supplier, payment terms preserved.
Open AR + AR aging → Fusion AR_PAYMENT_SCHEDULES, AR_RECEIVABLE_APPLICATIONS. Customer (KUNNR) → Fusion customer, credit limits, dunning history.
ANLA + ANLC + ANLP → Fusion FA_ADDITIONS, FA_BOOKS. Each SAP depreciation area becomes a Fusion book. Period depreciation history via period summaries.
CSKS/CSKB cost centres → department segment, CEPC profit centres → profit-centre segment, internal orders → Fusion Projects, CO-PA → profitability segments.
BSET + T007A tax codes → Fusion tax classifications. VAT, withholding, EC sales list, Intrastat preserved with full historical record.
Run three times — mock migration at -90 days, -45 days, -7 days from go-live. Any variance at the third mock is a no-go signal.
Every SAP source table produces a control total — row count, sum of amount columns, hash of key columns. Fusion target must match exactly. Catches extraction errors, transformation drop-outs, load failures.
Trial balance per company code at cutover date in SAP must equal trial balance per company code at cutover date in Fusion to the penny. Per local currency, per group currency, per ledger.
AP open balance per vendor reconciled. AR open balance per customer reconciled. Asset net book value per asset per book reconciled. Cash balance per bank account reconciled.
P&L by profit centre, by cost centre, by region, by product line for the trailing 12 months must match between SAP-source reports and Fusion-rebuilt reports. Catches dimensional-mapping defects that hide in trial-balance totals.
First full end-to-end migration on a copy of production. Reconciliation gaps identified. Mapping refinements made. Expected to find significant gaps and refine.
Final mock with frozen mapping rules. Expected to reconcile cleanly. Variance at this point triggers go/no-go discussion with CFO and audit partner.
Generic SI-led finance migration treats reconciliation as a checkpoint. Syntra ETL treats it as the operating discipline.
Auto-decomposes every ACDOCA row into Fusion GL + Cost Management + Asset Tracking targets while preserving full source-document traceability for audit trail.
Mandatory three-mock pre-production runs at -90/-45/-7 days. Each mock produces a full reconciliation pack that goes to CFO and audit partner.
Each SAP depreciation area becomes a Fusion book with per-asset net book value reconciled. Eliminates the most common asset-migration failure mode.
VAT, EC sales list (ZP), Intrastat, withholding tax all migrated with full historical record. EU/German Finanzamt audit-ready out of the box.
Trial balance reconciled in local currency, group currency, and any additional currencies (parallel currencies, group reporting currency). All three must match independently.
Every Fusion record carries source SAP document number and line number. External audit can trace any Fusion posting back to its SAP origin for post-migration audit.
SAP S/4HANA financial data migration covers the end-to-end move of every finance-relevant table from S/4HANA into Oracle Fusion's GL, subledger accounting (SLA), Cost Management, Asset Tracking, and Tax modules. The core scope: ACDOCA universal journal lines (with full account assignment — GL account, profit centre, cost centre, segment, functional area, business area, plant, intercompany partner), BKPF/BSEG legacy GL document headers and lines, FAGLFLEXA new-GL flex aggregates, KNA1/KNB1/KNVV customer master and company-specific extensions, LFA1/LFB1/LFBK vendor master, ANLA/ANLC asset master and cost segments, CSKS cost-centre master, CEPC profit-centre master, T030 account-determination tables, and all open AP/AR/asset balances. SAP S/4HANA financial data migration is the most regulated, most reconciled, most-checked workstream in any migration.
ACDOCA is S/4HANA's unified journal — every GL posting, every CO controlling document, every asset accounting movement, every material ledger transaction lands in ACDOCA with combined account assignment in one row. Oracle Fusion uses a separated architecture: GL_JE_LINES for journal lines, separate SLA tables for AP/AR/FA subledger detail, separate Cost Management tables for CO, separate Asset Tracking tables. SAP S/4HANA financial data migration decomposes each ACDOCA row into its constituent Fusion targets: the GL aspect becomes a Fusion GL journal line, the CO aspect becomes a Cost Management cost record, the asset aspect becomes an Asset Tracking record. Syntra ETL's decomposition layer maintains full traceability — every Fusion record carries the source ACDOCA document number and line number so audit-trail is preserved.
Open AP balances — unpaid vendor invoices, credit memos, downpayments — are migrated as Fusion AP Invoices with status of 'unpaid' and the full payment-schedule detail. Source records: BKPF/BSEG headers and lines filtered for AP account postings, KNB1/LFB1 control records for the business partner, PAYR for partial-payment history, REGUP for payment-run linkage. Mapping: vendor key (LIFNR) → Fusion supplier, invoice number (XBLNR) → Fusion invoice number, document date (BLDAT) → Fusion invoice date, posting date (BUDAT) → Fusion GL date, amount (DMBTR) → Fusion invoice amount with currency translation, payment terms (ZTERM) → Fusion payment terms, withholding tax (WT_QSCOD) → Fusion withholding code. Open-balance reconciliation runs three times pre-cutover at increasing data volumes.
Asset migration is the most structurally complex workstream because SAP's depreciation-area concept doesn't map cleanly to Fusion's book concept. SAP S/4HANA carries assets in ANLA (master) and ANLC (cost segment per depreciation area — typically book depreciation, tax depreciation, IFRS depreciation, group depreciation). Fusion's Fixed Assets module uses separate books per depreciation purpose. Migration approach: each SAP depreciation area becomes a Fusion book, each ANLC cost-segment row becomes a Fusion asset-in-book record, period depreciation history is migrated via the period-summary table to avoid loading thousands of monthly depreciation postings per asset. Asset-master attributes (description, asset class, capitalisation date, useful life, scrap value) migrate via the standard FBDI fixed-asset interface. Reconciliation: net book value per asset per book in SAP must equal net book value per asset per book in Fusion to the penny.
SAP S/4HANA carries cost centres in CSKS (master), CSKB (validity ranges), CSSL (statistical key figures) and profit centres in CEPC. Cost-centre and profit-centre values appear as fields on ACDOCA postings. In Fusion's chart-of-accounts model, cost centres typically map to the 'department' segment and profit centres map to a dedicated 'profit centre' segment. SAP S/4HANA financial data migration produces a crosswalk: a CSV mapping every SAP cost-centre code to a Fusion department code (often consolidated — SAP organisations frequently carry 5,000+ cost centres, Fusion deployments typically rationalise to 800–1,500), and every SAP profit-centre code to a Fusion profit-centre segment value. The crosswalk is signed off by finance before any production data is migrated because rationalisation decisions affect historical reporting.
S/4HANA's controlling module (CO) covers cost-element accounting, cost-centre accounting, internal orders, profitability analysis (CO-PA), product cost controlling, and overhead allocation. In Fusion these functions are covered by Cost Management (product cost, inventory cost), General Ledger with cost-centre segments (cost-centre accounting), Project Portfolio Management (internal orders → projects), and the SLA + GL stack for cost-element accounting. SAP S/4HANA financial data migration approach: cost-element master (CSKA, CSKB) migrates to Fusion natural-account segment values; cost-centre accounting balances migrate to GL with cost-centre segment populated; internal orders migrate to Fusion Projects with project numbers preserving the SAP order number; CO-PA characteristics migrate to Fusion's profitability segments. Cumulative period history is migrated via period-balance snapshots to keep load volume manageable.
SAP S/4HANA tax data lives in BSET (tax document lines), T007A (tax codes), T007S (tax-code descriptions), and integrates with Oracle Fusion's tax engine via tax-determination mapping. SAP S/4HANA financial data migration produces a tax-code crosswalk: every SAP MWSKZ tax code maps to a Fusion tax classification with the same rate, jurisdiction, and reporting category. Historical tax postings from BSET migrate as Fusion tax distributions linked to their AP/AR transactions. For VAT-registered EU entities, the migration also covers EC sales list (ZP) postings and Intrastat declarations to preserve the full statutory record. Withholding tax (WT_QSSHB, WT_QSCOD) maps to Fusion's withholding configuration with full historical record. Post-cutover, the first VAT return runs side-by-side in S/4HANA and Fusion for reconciliation before cutover is signed off.
Three layers of reconciliation, run three times. Layer 1: row-count parity — every SAP table that's migrated produces a control total (row count, sum of amount columns, hash of key columns) and the Fusion target must match exactly. Layer 2: financial reconciliation — trial balance per company code at the cutover date in SAP must equal trial balance per company code at the cutover date in Fusion to the penny, per local currency and per group currency. AP open balance, AR open balance, cash, inventory, fixed-asset net book value all reconciled separately. Layer 3: dimensional reconciliation — P&L by profit centre, P&L by cost centre, by region, by product line for the trailing 12 months must match between SAP-source reports and Fusion-rebuilt reports. Three sequential runs (mock migration at -90 days, mock at -45 days, mock at -7 days) prove the reconciliation is reproducible before the production migration.
Triple-layer reconciliation discipline, ACDOCA decomposition engine, triple-mock pre-prod runs, EU statutory preservation. The playbook used in 40+ S/4HANA-to-Fusion finance migrations with zero unreconciled trial-balance defects at go-live.