Oracle Fusion · Financials · Balances
Migrate opening general ledger balances into Oracle Fusion, covering code combinations, ledger and currency handling, period alignment and the trial balance that has to agree.
GL balance migration has one success criterion that everybody understands: the trial balance in the new system equals the trial balance in the old one. That clarity is deceptive. The difficulty is not the arithmetic, it is that the chart of accounts is usually being redesigned at the same time, so the two trial balances are expressed in different languages.
Balances also arrive as journals. Fusion does not accept a balance directly — an opening position is posted as a journal against the correct period, which means period status, ledger setup and code combination validity all gate the load.
Scope is agreed in discovery; this is the shape of the object.
| Data area | Typical information |
|---|---|
| Opening balances | Account, cost centre and the rest of the segment values, with amounts |
| Code combinations | The full accounting flexfield combination per balance |
| Ledger and currency | Primary ledger, entered and accounted currency, rate where relevant |
| Period | The opening period the balance is posted into |
| Balancing | Debits equal credits per balancing segment |
Dependency drives load sequence: a child cannot exist before its parent.
Confirm each of these before the first migration cycle.
Production-proven means we have delivered this object from that source. Supported and custom-mapping describe capability, not delivery history.
Object-level equivalence. Field-level mapping is produced per engagement.
| Source system | Source entity | Target object |
|---|---|---|
| Oracle EBS | GL Balances by code combination | Fusion opening balance journal |
| SAP ECC | G/L account balances by company code | Fusion opening balance journal |
| JD Edwards | Account Balances (F0902) | Fusion opening balance journal |
Journal Import FBDI, posting the opening position as a balanced journal
Import and post per ledger and per balancing segment
Fusion will not post an unbalanced journal.
Every combination exists, is enabled and is allowed for posting in that ledger.
The opening period is open and no later period has been closed against it.
Total by account and by balancing segment compared to source before the load, not after.
What has to exist before this object can load.
What actually fails on this object, and why.
Counts alone rarely prove this object migrated correctly.
Trial balance by account: source vs loaded, to the cent
By balancing segment and by ledger, not just in total
Subledger control accounts reconciled against the subledger objects loaded separately
Suspense account must be zero after load
Sign check on a sample of asset, liability, revenue and expense accounts
Detailed GL journal history is a strong archive candidate. Statutory retention usually runs to seven or ten years, but only the opening balance is operationally needed in the new ledger. Migrating balances and archiving detailed history keeps the new ERP fast and keeps the detail queryable for audit.
Extraction, mapping, transformation, validation preparation and target load generation.
Explore DataMove →Preserves source, prepared and target states for reconciliation, lineage and audit evidence.
Explore DataVault →Migration progress, data quality, exceptions and readiness across cycles.
Explore DataLens →Source-specific guidance for moving this object.
Published case studies whose scope included gl balances.
Tell us your source application, target system, object scope, volume and migration timeline. We can discuss the recommended migration approach and relevant Syntra ETL project experience.