Home / Case Studies / Oracle EBS → Oracle Fusion (KSA Government)
    CASE STUDY · PwC PROGRAM · RIYADH, KSA

    Oracle EBS to Oracle Fusion Data Migration for a Major Saudi Government Organization

    A PwC-led Oracle Fusion implementation for a major government organization headquartered in Riyadh, Saudi Arabia. Syntra ETL delivered the transform-and-load of procurement, supplier, item and finance data — across 18 business units and more than a million inventory items — into Oracle Fusion, roughly five times faster than manual loading and with complete row- and column-level reconciliation of every data element.

    18
    Business units
    1M+
    Inventory items
    Faster than manual
    Row + column
    Reconciliation

    The engagement

    The client — a major government organization headquartered in Riyadh, Saudi Arabia — was moving its procurement operation off Oracle E-Business Suite onto Oracle Fusion Cloud. The overall Oracle Fusion implementation was owned by PwC as prime. Syntra ETL (Firstcron) was brought in to own the part that decides whether a go-live succeeds or slips: the transform-and-load of the data into Oracle Fusion.

    The responsibilities were split cleanly, which kept the programme fast and auditable:

    🧩

    Syntra ETL owned

    Configuration of the Syntra platform; transformation of PwC-supplied data to the Fusion target schema, value sets and 18-BU logic; load into Fusion via FBDI/REST; load-readiness checks; and technical reconciliation (source → staged → Fusion).

    🏛️

    PwC owned

    Extraction of data from the legacy EBS systems, business validation and cleansing of source data, all customer-facing communication, and milestone acceptance.

    🔒

    Scope discipline

    Inputs were frozen at the start of every milestone; anything changed afterward was a change request, not a defect — protecting both timeline and data integrity.

    Why the Syntra ETL platform

    ~5× faster than manual

    On comparable objects, loading through Syntra was around five times faster than hand-building and importing FBDI files — the difference between a cutover weekend and a cutover week.

    🎯

    Load-readiness validation

    Before anything touches Fusion, Syntra checks mandatory fields, datatypes, lookups and referential integrity against the Fusion targets — so failures surface in staging, not mid-import.

    🏢

    18-BU transformation logic

    Item-to-BU and supplier-site-to-BU assignment across 18 business units was encoded once in the tool and applied consistently, instead of being re-derived by hand each run.

    🔁

    Idempotent re-runs

    Repeated mock and production loads are safe: batch keys and de-duplication prevent “already exists” collisions when the same records are reloaded.

    🔗

    FBDI + REST + UCM

    Native Oracle Fusion load paths — FBDI templates, REST, and UCM for attachments — driven and logged from one place.

    Reconciliation built in

    Every object produces a source → staged → Fusion count, plus row- and column-level checks, as a by-product of the load — not a separate manual exercise.

    How it was delivered

    A staged, mock-run-based approach de-risked the production cutover:

    1

    Tool configuration

    Syntra configured for the Fusion procurement scope — templates, mappings, target-schema validations and non-prod connectivity — proven end-to-end on a small sample.

    2

    Three main load runs

    Three main transform-and-load runs into Fusion non-prod — the first on a representative dataset, the next two at full production volume — each with a load-readiness exception report handed back for correction.

    3

    Many delta runs

    Between the main runs, many smaller delta runs loaded only the corrected and changed records — converging to a clean, reconciled load and finalising the cutover runbook.

    4

    Production cutover + hypercare

    Production load in the sequence Item → Supplier → Procurement → Finance, per-wave reconciliation, and a fixed hypercare window.

    5

    Historical data load

    Post go-live load of historical procurement transactions and attachments into Fusion/UCM.

    Read the full delivery approach →

    Reconciliation you can put in front of an auditor

    Syntra’s responsibility ended not at “the load ran” but at a technical reconciliation pack for every object: source row counts versus staged rows versus Fusion rows, plus row- and column-level validation of every data element. Load logs recorded success and failure counts per object, and a shared error tracker carried each exception through to a resolution.

    Source → staged → Fusion
    Every object reconciled at all three stages, so any drop is caught and explained.
    Row + column level
    Not just totals — individual data elements validated against source.
    Evidence, not assertion
    Load logs, exception reports and an error tracker form an auditable trail.

    How reconciliation & validation worked →

    The outcome: stalled for close to a year, delivered in under 12 weeks

    Before Syntra ETL came on board, the Oracle EBS → Oracle Fusion data migration had been in progress for almost a year — worked by the system integrator and client through conventional, largely manual loading — without reaching a clean, reconciled load. Once Syntra owned the transform-and-load, the full scope went live in just under twelve weeks.

    Before Syntra
    ~1 year
    in progress, not landed

    The migration had run for close to a year through conventional, largely manual loading — without a clean, reconciled result across the 18-business-unit estate.

    With Syntra
    Under 12 weeks
    configured → mocked → loaded → reconciled

    Syntra configured the platform, proved it across three main runs and many smaller delta runs, and loaded procurement, supplier, item and finance data into Oracle Fusion — reconciled and ready for go-live.

    18 business units loaded1M+ inventory itemsRow + column reconciled~5× faster than manualRepeatable, idempotent re-runs

    Frequently asked questions

    Who was the end customer?

    Under our agreement with PwC we don’t publish the end-customer name. It is a major government organization headquartered in Riyadh, Saudi Arabia, migrating from Oracle E-Business Suite to Oracle Fusion Cloud. PwC owned the overall implementation; Syntra ETL delivered the data transform-and-load.

    What was Syntra ETL responsible for?

    Configuring the Syntra platform, transforming PwC-supplied data to the Fusion target schema and 18-BU logic, loading it into Oracle Fusion via FBDI/REST, running load-readiness checks, and producing technical reconciliation. PwC owned data extraction and business validation.

    How much faster was the tool than manual loading?

    On comparable objects, loading through Syntra was roughly five times faster than manually building and importing FBDI files, with fewer human errors and repeatable re-runs.

    How large was the migration?

    18 business units and more than a million inventory items in the item master, alongside the full supplier master, procurement transactions and AP finance objects.

    Which Oracle Fusion load methods were used?

    Native Fusion paths — FBDI templates and REST for structured data, and UCM for attachments — all orchestrated and logged from the Syntra platform.

    Planning an Oracle EBS to Oracle Fusion migration?

    Tell us your source EBS footprint, modules and business units — we'll scope a mock-run-based transform-and-load plan on the Syntra ETL platform.