Pre-built microsoft dynamics nav to oracle fusion data mapping. Customer 18 → TCA party. Vendor 23 → supplier site. Item 27 → Inventory master. G/L Entry 17 → Fusion GL + SLA. Item Ledger 32 → Cost Accounting. Dimensions → COA + DFFs. Posting Groups → SLAM rules. Signed, version-controlled, audit-ready.
Two data models that look superficially similar — ERP customers, vendors, items, GL entries — but differ in every detail that matters for audit, statutory reporting and operational continuity.
NAV's classic table set evolved across three decades, from the Navision Attain database through Microsoft Navision into Dynamics NAV 2009 RTC, 2013, 2015, 2016, 2017 and 2018. Customer lives on table 18 with a Customer Posting Group driving AR account derivation. Vendor lives on table 23 with a Vendor Posting Group driving AP. Item lives on table 27 with an Inventory Posting Group plus General Product/Business Posting Groups driving cost of goods and VAT. G/L Entry on table 17 holds every posted line with Global Dimensions 1 and 2 on the row, Shortcut Dimensions 3–8 in a related Dimension Set Entry table, and source code plus document chain back to the originating Sales Invoice or Purchase Invoice or Journal.
Fusion uses a fundamentally different shape. TCA holds parties as a master abstraction, with customer accounts and supplier sites layered on top. Inventory Items live in a separate master with category hierarchies. The Chart of Accounts is a 6-segment fixed structure — typically Company, Cost Center, Natural Account, Product, Project, Intercompany — with all other analytics riding on DFFs. Subledger Accounting (SLA) replaces NAV's Posting Group derivation with a journal entry rule engine. Every microsoft dynamics nav to oracle fusion data mapping has to bridge these structures without losing the audit chain that links a Fusion GL line back to the original NAV Sales Invoice.
Syntra ETL ships the bridge pre-built. Crosswalks for the classic table set are refined across dozens of NAV conversions; custom-table routing, dimension materiality scoring and posting-group translation run as automated passes; the evidence pack is generated by the engine, not assembled by hand. The first round of mapping output is on the table in week two — not month five.
The decisions that on a consultant-led microsoft dynamics nav to oracle fusion data mapping project become multi-week negotiations — and how the engine resolves them in hours.
NAV G/L Account chart (table 15) walked, dormant accounts flagged, control accounts identified, mapped to Fusion natural-account segment with parent-rollup preserved and historical-balance continuity confirmed.
Global Dim 1/2 + Shortcut Dim 3-8 + customer dimensions evaluated for materiality. High-cardinality statutory dimensions collapse to COA segments; analytical dimensions route to DFFs; obsolete dimensions retire.
Customer/Vendor/Inventory/General Product/General Business/VAT Posting Groups translated to Fusion Subledger Accounting Method journal entry rules, validated by sample-period replay.
Custom fields on standard tables (18, 23, 27) inventoried, classified by business purpose, routed to Fusion DFFs on the parent object. Custom tables in 50000-99999 range routed individually.
Per-company NAV databases (Company1, Company2, Company3) consolidated into Fusion BUs and ledgers with NAV-source-company preserved as DFF and intercompany pairs reconciled.
Country-specific NAV localisation fields (DE GoBD, UK MTD, NO/PL/PT/FR SAF-T, IT SdI, MX CFDI, BR SPED) preserved on the relevant Fusion DFFs for ongoing statutory submission continuity.
A repeatable, signed sequence. Each stage produces an artefact that gets reviewed and signed before the next stage starts.
Object Designer crawler walks every NAV table, field, key, page and codeunit. SQL Server profiler estimates row volumes. Output: complete source-side inventory across every company in scope.
Fusion COA segment shape locked. TCA party model, Inventory item model, Subledger Accounting Method scope confirmed. DFF inventory on parent objects defined. Output: signed target design document.
Per-domain crosswalk generated by the mapping engine — Customer, Vendor, Item, G/L Account, dimension, posting group, custom field, custom table. Output: draft microsoft dynamics nav to oracle fusion data mapping evidence pack v0.1.
Sample period (typically last full quarter) extracted from NAV, run through the mapping engine, reconciled to the cent against the source G/L Entry totals, AR aging, AP aging and inventory valuation. Errors surfaced with row-level diagnostics.
Tax, audit, finance and operations leads review the evidence pack, sign each per-domain crosswalk. Mapping v1.0 locked under version control. Any subsequent change requires a documented amendment and re-replay.
Locked mapping drives every subsequent extraction-transform-load cycle through to cutover. Mapping evidence pack is the single source of truth for any post-go-live audit or operational question.
One pack, eight artefacts, signed once and referenced for the life of the migration and the audit window afterwards.
Customer, Vendor, Item, G/L Account, dimension, posting-group, custom-field and custom-table crosswalks — each one a versioned spreadsheet with source-field, target-field, transformation rule and example values.
Sample-period replay logs showing input NAV rows, applied transformation rules, expected Fusion output rows and reconciliation deltas (must be zero).
Per-period reconciliation between NAV trial balance and Fusion trial balance, AR aging vs aging, AP aging vs aging, inventory valuation vs valuation — to the cent.
Tax, audit, finance and operations sign each per-domain crosswalk plus the overall mapping v1.0 lock. PDF-signed pages bundled with the pack.
Fusion COA segment shape, TCA party model, Inventory item model, SLAM scope, DFF inventory — the target side of the mapping fixed in writing.
Dimension materiality scoring methodology and outputs, custom-table materiality scoring, partner add-on routing decisions — the methodology behind every routing call.
Microsoft dynamics nav to oracle fusion data mapping is the field-level translation layer between NAV's classic data model — Customer table 18, Vendor table 23, Item table 27, G/L Entry table 17, Item Ledger Entry table 32, Sales Header 36 / Line 37, Purchase Header 38 / Line 39 — and Fusion's TCA party, Inventory item, Subledger Accounting and 6-segment Chart of Accounts structures. Done by hand it is dozens of weeks of consultant SQL plus C/AL inspection plus spreadsheet crosswalks. Syntra ETL ships the mapping pre-built and version-controlled, so what traditionally consumes the first quarter of a NAV → Fusion programme is a documented artefact in week two.
The core operational tables are non-negotiable: table 18 (Customer) → Fusion TCA party + customer account; table 23 (Vendor) → TCA party + supplier site; table 27 (Item) → Fusion Inventory item master; table 17 (G/L Entry) → Fusion GL journal lines with subledger context; table 32 (Item Ledger Entry) → Fusion Cost Accounting layers; table 36/37 (Sales Header/Line) → Fusion AR transactions or open Sales Orders; table 38/39 (Purchase Header/Line) → Fusion AP invoices or open Purchase Orders; table 5050 (Contact) → TCA contact; table 270 (Bank Account) → Fusion Cash Management bank account; G/L Account table 15 → COA natural account segment; Dimension framework (Global Dim 1/2 + Shortcut Dim 3–8) → Fusion COA segments + DFFs. Custom tables in the 50000-99999 range get individual mapping decisions captured in the evidence pack.
Table 17 (G/L Entry) is the heart of NAV finance — every posted entry across every subledger lands here with G/L Account, posting date, amount in LCY, amount in additional reporting currency, source code, document number and the full dimension stack. The microsoft dynamics nav to oracle fusion data mapping engine routes each G/L Entry row through a deterministic pipeline: G/L Account → Fusion natural-account segment (via the COA crosswalk), Global Dimension 1 and 2 → typically Cost Center and Product segments, Shortcut Dimensions 3-8 and customer dimensions → remaining COA segments or DFFs by materiality, Source Code → Fusion journal source, document chain (Sales Invoice, Purchase Invoice, Journal) → Fusion subledger linkage. The FBDI Journal Import payload validates against current Fusion 26x schemas before any submission.
NAV's Dimension framework is its flexible analytics axis — Global Dimensions 1 and 2 sit on most operational tables for fast filtering, Shortcut Dimensions 3 through 8 appear on G/L Entry and subledger entries, and customer-defined dimensions extend the model further. Fusion's equivalent is the 6-segment Chart of Accounts. The microsoft dynamics nav to oracle fusion data mapping engine walks every active dimension value in the source database, samples usage across G/L Entry 17 and subledger entries, scores materiality, then routes: high-cardinality statutory dimensions collapse to Fusion COA segments (a typical 6-segment shape is Company, Cost Center, Account, Product, Project, Intercompany), low-cardinality analytical dimensions route to Fusion DFFs, obsolete dimensions (no posting in 36 months) retire with sign-off.
Customer Posting Group (table 92), Vendor Posting Group (93), Inventory Posting Group (94), General Product Posting Group (250), General Business Posting Group (251), VAT Posting Groups (324/325) — these drive NAV's automatic G/L account derivation across the subledger applications. The microsoft dynamics nav to oracle fusion data mapping engine reverse-engineers each Posting Group's effective behaviour, samples actual G/L Entry postings to confirm rule fidelity, and translates the resulting logic into Fusion Subledger Accounting Method (SLAM) journal entry rules. The mapping is verified by replaying a sample period of NAV postings through the resulting SLAM rules and reconciling to the cent against the original G/L Entries before sign-off.
Yes. NAV deployments accumulate custom fields on standard tables (Customer 18, Vendor 23, Item 27) and entirely new custom tables in the 50000-99999 partner range over years of in-house development. The microsoft dynamics nav to oracle fusion data mapping engine walks every modified standard table and every custom table, classifies each by business purpose and update frequency, and routes: required custom fields collapse onto Fusion descriptive flexfields (DFFs) on the parent object with full historical-value retention, high-volume analytical custom tables route to a Fusion-adjacent warehouse with OTBI lookback, partner add-on tables (Anveo, ChargeLogic, Continia, Insight Works) follow per-vendor playbooks, and obsolete custom tables retire. Every routing decision is logged in the migration evidence pack.
NAV's per-company database segmentation makes a multi-tenant estate (Company1, Company2, Company3 in the same SQL Server database) look like a set of parallel structures with shared object definitions but independent transactional data. The mapping engine handles this natively: each company gets its own extraction pipeline keyed on company-id, masters consolidate into a single Fusion TCA / Inventory model with NAV-source-company preserved as a DFF, dimensions and posting groups consolidate via per-company sub-mappings, and intercompany G/L Entry pairs are reconciled and replayed against Fusion's intercompany accounting framework. Whether the target Fusion shape is one ledger with multiple BUs or multiple ledgers consolidating via FCCS, the mapping engine emits the right shape.
Yes. Every mapping decision lands in a signed, version-controlled evidence pack: a per-domain crosswalk spreadsheet (Customer mapping, Vendor mapping, Item mapping, G/L Entry mapping, dimension mapping, posting-group mapping, custom-table mapping, partner add-on mapping), a per-rule replay log showing sample input rows and expected Fusion output rows, a reconciliation log showing NAV totals vs Fusion totals at row, sum and hash level. Internal audit, external audit, tax and finance leads sign the pack before cutover. The pack also serves as the post-go-live reference: when a question arrives 18 months later about why a particular NAV dimension landed on a particular Fusion COA segment, the answer is in the pack.
Book a 30-minute discovery call. We'll walk through your NAV table inventory, dimension framework, posting groups, custom-table tail and partner add-ons — and give you a concrete crosswalk timeline before the call ends.