JD Edwards Migration Cutover — Period-Aligned, Reversible, Rehearsed

A jd edwards migration cutover is the orchestrated transition from a live JDE EnterpriseOne or World production environment to a live Oracle Fusion environment — the moment new transactions cut to Fusion, JDE moves to read-only, and the business continues operating. JDE cutovers carry three particular complications. First, manufacturing depth: in-flight work orders (F4801), partially-consumed parts lists (F3111) and in-progress routing operations (F31122) cannot freeze cleanly the way GL transactions can — they have a physical real-world state on the shop floor. Second, period-end alignment: cutting mid-period creates a partial F0902 balance that is messy to reconcile, so cutovers align to month-end or quarter-end. Third, World-side coordination: if World runs on AS/400 hardware that is also being decommissioned, the cutover sequencing has to account for hardware retirement timing alongside data cutover. Each is solvable, but each requires explicit planning.

Cutover aligns to a fiscal period boundary — typically month-end, often quarter-end, sometimes fiscal year-end for the cleanest reconciliation pack. The period close in JDE has to complete in JDE (final F0902 balances posted, AP/AR aging settled, item-ledger close run), the F0902 trial balance has to reconcile to Fusion GL to the cent (the final reconciliation pack from jd edwards data validation), then the period opens in Fusion and new transactions cut to Fusion. The cutover window is typically a 36–72 hour change window over a weekend, with the JDE period close on Friday night, reconciliation and FBDI delta-replay through Saturday, Fusion period-open Sunday morning, and business resumption Monday. For fiscal-year-end cutovers the window is longer (typically 5 days) to accommodate the closing-entry preparation and the auditor's preliminary review.

In-flight work orders are the hardest part of a manufacturing cutover because they straddle the cutover boundary — opened in JDE, will complete in Fusion. Three strategies cover most cases. First, drain: stop releasing new work orders 2–4 weeks before cutover, let in-flight work orders complete in JDE before the freeze, cut over with zero open work orders. Lowest risk, highest disruption to operations. Second, freeze-and-replicate: at cutover, freeze in-flight work orders in JDE (status held), replicate to Fusion with current state (parts consumed so far, operations completed so far), continue the work order in Fusion. Highest complexity, lowest disruption. Third, parallel run for manufacturing: keep manufacturing in JDE for one or two months after Financials cuts to Fusion, then cut manufacturing in a second wave when in-flight work orders have drained naturally. The right choice depends on shop-floor cycle time, work-order volume, and operations tolerance for disruption.

The freeze window is the period during which JDE accepts no new transactions and Fusion is not yet live — the data is in motion (final delta replay, reconciliation, period-open). For Financials-only cutovers the freeze is typically 24–36 hours over a weekend. For full-scope cutovers (Financials + SCM + Manufacturing) the freeze stretches to 48–72 hours and often spans a long weekend. For year-end cutovers the freeze extends to 5 days to accommodate the closing process and the auditor's preliminary review. During freeze, ops continues physical activity (manufacturing, shipping, receiving) with paper-based records or stand-in process where required, and transactions are entered into Fusion post-cutover with the appropriate effective dates. The cutover plan documents the freeze window minute-by-minute with named owners, dependencies and decision points.

Delta replay is the mechanism that keeps Fusion current with the last hours of JDE activity before freeze. After the initial bulk load (weeks before cutover) Syntra ETL runs incremental delta extracts keyed off per-table modified-date watermarks: F0911.GLUPMJ for ledger, F0411.RPUPMJ for AP voucher, F03B11.RPUPMJ for AR invoice, F4111.ILUPMJ for item ledger, F4211.SDUPMJ for sales order, F4311.PDUPMJ for purchase order. During parallel run these run daily or hourly. During the cutover window the final delta runs against the period-close watermark, generating final FBDI batches that catch every JDE transaction up to the freeze instant. The final reconciliation pack (F0902 vs Fusion GL to the cent) runs against the post-delta state. Only when reconciliation signs off does the period open in Fusion.

Rollback is procedural, not theoretical — every cutover plan documents a no-go decision point and the rollback procedure to execute if conditions are not met. The primary go/no-go criteria are: F0902 trial balance reconciles to Fusion GL to the cent (zero-variance threshold for material accounts, defined-variance threshold for immaterial), all sub-ledger agings reconcile within tolerance, all FBDI loads complete without unresolved errors, all critical OTBI reports run and tie to JDE equivalents, all critical integrations cut to Fusion and validated end-to-end. If any criterion fails at the no-go point (typically 24 hours before period-open), rollback executes: JDE freeze lifts, JDE returns to live for the next period, Fusion period-open delays, the failure root-cause is investigated, the cutover reschedules to the next fiscal period boundary. No fudging, no incomplete cutover that leaves the business running half on each side.

World customers on AS/400 (IBM i) hardware often have a board-level objective to retire the iSeries — RPG/COBOL talent retirement, hardware end-of-support, datacenter consolidation, OPEX reduction. The cutover sequencing has to coordinate data cutover with hardware decommission. Typical sequence: full read-only extract of World data captured to Parquet archive (the data lives forever in the archive, not on the AS/400); production cutover to Fusion executed per the standard cutover plan; 30-day post-cutover validation period during which World hardware stays available read-only for any unforeseen reconciliation need; AS/400 decommission executed (hardware powered off, final backup taken, decommissioned per IBM procedure). For mixed E1 + World estates, the World cutover often runs first to retire the hardware, with E1 staying live to support phased cutover of remaining business areas.

A typical cutover call has 8–15 named participants on a 36–72 hour rolling rota: cutover lead (Syntra ETL or client PM), JDE technical lead (CNC administrator, ready to execute period close and freeze), JDE functional lead per module (Finance, SCM, Manufacturing if in scope), Oracle Fusion functional lead per module (mirror of JDE side), database administrator (read-only credentials, query support), integration lead (cuts each integration flow in sequence), data validation lead (runs reconciliation pack, owns sign-off threshold), controllership representative (signs F0902 reconciliation), SCM operations representative (signs item-ledger reconciliation), executive sponsor (owns go/no-go decision), on-call infrastructure (Fusion ESS support, network, identity). For World customers add an iSeries operator. The cutover plan documents the call schedule, the named owner per checkpoint, the escalation path, and the decision criteria — minute by minute through the freeze.