Pre-built infor ln to oracle fusion data mapping for every Baan package. Multi-company structural crosswalks, field-level rules, item-class and project-WBS conversions, version-controlled, signed by controllers. No bespoke Baan-table SQL.
LN's Baan-derived multi-company N:M architecture, company-suffixed tables, package-prefixed naming and 4GL-extensible DD don't translate 1:1 to Fusion's Ledger/BU/Inv Org structure. Every field needs a deterministic target.
Infor LN, descended from Baan IV/V, organizes data by package prefix (tc, tf, td, ti, tp, ts, qm, fm), segregates company-specific transactional data via 3-digit company suffix on table names (tfgld010, tdsls010, tisfc010), and exposes a DD (Data Dictionary) extensibility layer where customers add custom fields directly to standard tables. Oracle Fusion uses a completely different shape — Ledgers, Business Units, Inventory Orgs, with FBDI templates that expect specific column orders, specific data types, and specific lookup-code references from Oracle-maintained code tables.
Every infor ln to oracle fusion data mapping has to bridge that structural divide while preserving the intercompany audit chain, the multi-company segregation, the item-master attribute richness, the project-WBS hierarchy and the EVM measures. Custom Baan-table SQL plus one-off FBDI scripts can do it — but every domain becomes a multi-month conversation between finance, manufacturing, projects, supply chain and IT.
Syntra ETL replaces that with pre-built crosswalks refined across dozens of LN-to-Fusion conversions, plus a configuration-driven customization layer where you tune the mapping for your specific COA design and company structure. Mapping rules are version-controlled, signed by the business owner, and produce auditable run-logs when applied — so auditors get a deterministic answer to 'how did this Fusion record get this value from LN?'
Each layer ships pre-built. Each layer is customizable with version-controlled, signed rules.
Logistical/Financial Company N:M architecture mapped to Fusion Ledger per Financial Company, BU per Logistical Company, Inv Org per warehouse — material companies kept, obsolete ones retired.
LN account-cost-center segments mapped to Fusion 6-segment COA with customer-customized rules per Financial Company, per account, per cost center — signed by controller.
LN item-master attributes (UOM conversions, lot/serial control, ABC class, ITAR/DFARS flags, item-class hierarchy) mapped to Fusion Item Master core + Item Class flex fields.
LN work centers, routings, BOMs mapped to Fusion work centers, resources, BOMs with capacity, labor rates and overhead carried forward.
LN project WBS (Project+Element+Activity) mapped to Fusion PPM hierarchy with budget, contract, T&M lines, progress billing and EVM measures preserved.
LN Baan-precision unit costs (5–6 decimal places) reconciled to Fusion's 2–10 decimal precision with documented rounding rules per currency and per cost component.
From discovery to signed, audit-ready mapping pack — typically 4–6 weeks for full-scope coverage.
Syntra extractor crawls every active package, every company-suffixed table, every DD extension. Output: complete field-level inventory ready for mapping decisions.
Standard LN-to-Fusion crosswalks applied across the inventory — every field that has a deterministic Fusion target gets one. Output: 70–80% of mapping decisions auto-resolved.
Customer-specific COA mapping rules captured per Financial Company per account, custom-field mapping rules for DD extensions, item-class hierarchy customization, project-WBS-to-PPM mapping — signed by business-domain owners.
Mapping rules applied to a sample LN extract, dry-run FBDI/HDL payloads generated, validated against current Fusion 26x schema. Errors surface locally with row-level diagnostics before production load.
Mapping pack signed by controller, finance lead, manufacturing lead, projects lead. Version-locked in Git with audit trail. Ready for production migration.
Quarterly mapping refresh tracking Oracle Fusion 26x release schema changes and customer-side accounting policy updates. Re-running a load with updated mapping is one-click.
Every mapping decision documented, versioned, signed and traceable end-to-end.
Every LN source field documented with package, table, DD definition, data type, sample values and customization indicator (standard vs DD extension).
Every Fusion target field documented with current Oracle release schema reference, FBDI template column, data-type expectation and lookup-code requirement.
Each mapping documented with rule type (pass-through, lookup, computation, conditional), business logic, default-value handling and exception behavior.
Each mapping signed by the business-domain owner (controller for COA, manufacturing lead for items, projects lead for WBS) with timestamp and rationale.
Every mapping rule version-controlled in Git with full history — who changed what when, why, and what loads ran against which version. Auditors get a deterministic timeline.
Every Fusion record drillable back to originating LN record with the mapping rule version that applied at load time — eliminates 'how did we get this value?' audit questions.
Infor ln to oracle fusion data mapping is the field-level translation layer between Infor LN's Baan-derived data model and Oracle Fusion's ERP/SCM/PPM/EPM data model. Every LN field — from the obvious (item master attributes in tcibd, GL journal lines in tfgld) to the obscure (project EVM measures in tppss, ITAR classification flags on item-master extensions) — needs a deterministic Fusion target with a documented transformation rule. The Syntra ETL data-mapping engine ships pre-built crosswalks for the standard LN-to-Fusion correspondence across all 8 production packages, plus a governed customization layer where you tune the mapping for your specific configuration: COA segment design, item-class hierarchy, work-center-to-resource mapping, project-WBS-to-PPM-structure conversion.
The terms get used interchangeably, but operationally: a crosswalk is the table-level correspondence between an LN entity and a Fusion entity (LN tfgld → Fusion GL_JE_LINES_INTERFACE), while a data mapping is the field-level translation rule that says how a specific source value becomes a specific target value (LN Financial Company 010 + LN COA account 4000-100-200 → Fusion Ledger LEDG-US-PRIMARY + Fusion COA 1100-100-2000-100-000000-0000). Syntra ETL's infor ln to oracle fusion data mapping engine ships pre-built crosswalks for every standard LN-to-Fusion correspondence, and a configuration-driven field-level mapping layer that customers tune for their specific COA design and company structure.
LN segregates company-specific transactional data by appending the 3-digit company code as a table suffix — tfgld010 holds GL journals for Financial Company 010, tfgld020 for company 020, and so on across hundreds of company suffixes. A naïve mapping that targets 'tfgld' misses everything. Syntra ETL's mapping engine auto-discovers every active company-suffixed table variant during extraction, preserves the company code as a partition key throughout the pipeline, and applies the correct Fusion Ledger/BU/Inv Org mapping per company suffix at load time. Multi-company configurations route automatically to the correct Fusion enterprise structure with intercompany flows reconstructed as Fusion intercompany journals.
Yes — and you typically will. Every customer's Fusion COA design reflects their accounting policy, statutory requirements and management reporting structure, so the LN-to-Fusion account mapping is necessarily customer-specific. Syntra ETL's mapping engine ships with default LN-COA-segment-to-Fusion-COA-segment scaffolding, plus a governed customization layer where you define your specific mapping rules: per Financial Company, per LN account, per cost center, per project. Mappings are version-controlled, auditable and signed by the controller. Re-running a load with an updated mapping is a one-click operation — no Baan-table SQL editing, no FBDI template re-engineering.
Item master in LN (tcibd in the Common package plus item-class-specific extension tables) carries far more attribute richness than Fusion's default Item Class structure: unit-of-measure conversions per item per business partner, ABC class per Logistical Company, lot/serial control per item per warehouse, ITAR/DFARS classification flags, configure-to-order routing rules. Syntra ETL's mapping engine preserves the full attribute set — mapping standard attributes to Fusion Item Master core fields and routing LN-specific attributes to Fusion Item Class flex fields with the correct hierarchy. Item categories from LN map to Fusion Product Categories with multi-level hierarchy preserved.
Yes. LN project structures (tppdm — Project + Element + Activity hierarchy) map to Fusion PPM (Project + Task + Sub-task hierarchy) with budget, contract and progress carried forward. EVM measures from LN (BCWS, BCWP, ACWP, plus customer-specific EVM extensions) map to Fusion PPM EVM measurements with the calculation rules preserved. Project commitments, time-and-material lines, progress billing milestones, and earned-value reporting carry over with full traceability — so PPM reports in Fusion immediately reconcile to the equivalent LN project reports during parallel run.
Every mapping rule in Syntra ETL's engine is version-controlled in Git, signed by the customer's controller or business-domain owner, and produces an auditable run-log when applied to a load. The mapping documentation pack includes: source LN field with package and DD definition, target Fusion field with current Oracle release schema reference, transformation rule (pass-through, lookup, computation, conditional), rule owner, sign-off date and version history. Auditors get a deterministic answer to 'how did this Fusion GL line get this account code from LN?' — drilling all the way back to the originating LN journal line in tfgld with the mapping version that applied.
Yes — and customers running multi-tenant LN deployments do exactly this. Customers with multiple LN tenants (one per business unit, one per acquired company, one per geography) typically share the foundational mapping (item-class crosswalk, work-center-to-resource translation, project-WBS-to-PPM conversion) and customize only the tenant-specific overlays (per-tenant COA mapping, per-tenant Logistical/Financial Company mapping). The shared mappings cut per-tenant migration time by 40–60%. Syntra ETL's mapping engine supports inheritance and override semantics so tenant-specific changes don't bleed into the shared layer.
30-minute call. Walk through your LN package footprint, company structure and Fusion target design — leave with a concrete data-mapping plan and timeline.