A jd edwards migration assessment that replaces slide-deck estimates with F9860 row counts, F0911 ledger profiles, OMW customization inventories and signed integration maps. Sized budget and timeline before week three.
Every consultant-led JDE migration overrun we have inherited started with an assessment that skipped OMW customization inventory or guessed at F0911 row counts. Evidence first, estimate second.
Oracle JD Edwards estates accumulate complexity in three places that a desk-research assessment cannot see: OMW custom objects (decades of R55xxxxx UBEs, P55xxxxx apps, NER business functions, BSFN C code, custom F9210 data items), category-code conventions on F0006 Business Units (each plant or business unit often built its own 30-category-code language over the years), and integration glue (Orchestrator flows, AIS Server REST consumers, EDI brokers, bank file plumbing). None of this shows up in a vendor questionnaire — and all of it determines the timeline.
Syntra ETL's jd edwards migration assessment is a fixed-fee 2–4 week engagement that crawls the actual source: F9860 Object Librarian Master, F9861 Object Librarian Status Detail and F98711 Audit Trail produce the OMW inventory; F0006 + F0901 produce the COA structure; F0911 + F0902 produce the ledger volume; F4111 + F4801 + F3112 + F31122 produce the manufacturing depth; F0101 produces the Address Book split profile. The output is a sized budget and timeline backed by row counts, not estimates.
For mixed E1 + World estates the assessment doubles as a sequencing recommendation: cut World first to retire AS/400 hardware (often a board-level objective once iSeries RPG/COBOL talent retires), then cut E1; or unify into a single wave to one Fusion target. The complexity scoring framework gives the steering committee a defensible answer. The same applies to M&A-driven multi-instance consolidation — 3, 5, 8 JDE instances inherited across acquired business units, each with its own COA dialect.
Each dimension scores 1–5 against an evidence base from the JDE source itself. The composite score drives the timeline band, budget range and recommended phasing.
F0911 row count, years of history, F4111 item-ledger depth, F4801 work-order chain length. Drives extract throughput planning and Parquet archive sizing.
OMW object count weighted by classification — a custom NER GL-posting hook scores 5; a custom R55xxxxx supplier-aging report scores 1 because it retires to OTBI.
Orchestrator flows, AIS Server REST consumers, EDI brokers (TrueCommerce, SPS, Cleo on F47xxx), bank file plumbing, tax engines, freight. Each catalogued with target-state disposition.
Company × BU × Object × Subsidiary cardinality, number of distinct category-code conventions across BUs, multi-currency exposure. Drives the crosswalk effort.
Fusion Manufacturing in-scope vs Financials-only, routing complexity, work-order genealogy preservation requirements. Often the biggest single timeline driver.
SOX 7yr, HGB 10yr, FDA 21 CFR Part 11, FAA 14 CFR, DCAA/DFARS. Each regime adds evidence-preservation work to the load route and sign-off pack.
Read-only access on day one. Customization inventory by end of week one. COA crosswalk draft by end of week two. Sized plan and steering-committee read-out by end of week three.
Stakeholder map confirmed, read-only credentials provisioned against the JDE backend (Oracle DB / SQL Server / DB2 LUW for E1; DB2/400 ODBC or JTOpen JDBC for World), AIS Server endpoint validated where in scope, OMW environment confirmed.
F9860, F9861, F98711 walked. Every custom object inventoried, classified by business purpose, and assigned a draft disposition (retire / rebuild in OTBI / Fusion Integration Cloud extension / carry forward). Interview cycle with JDE functional leads to validate.
F0010, F0006, F0901, F4101, F0101 row counts, cardinality and category-code convention profile captured. Draft Fusion 6-segment COA crosswalk produced and walked with controllership.
F0911, F0902, F0411, F03B11, F4111, F4801 row counts captured. Every upstream/downstream integration (bank, tax, freight, EDI, BI, EPM) catalogued with target-state disposition.
Six-dimension complexity score computed against evidence. Sized timeline band (12–18 weeks for low/mid, 18–28 for high) and budget range produced with sensitivity analysis. Phasing recommendation (Financials first vs full-scope, single wave vs multi-wave) drafted.
Steering-committee read-out delivered. Five-deliverable pack issued: instance inventory, OMW catalog, COA crosswalk draft, integration map, sized migration plan with risk register. Becomes the input to the SOW for the migration itself.
The findings that consistently change the sizing conversation when the evidence lands on the table.
Most R55xxxxx UBE reports retire to Fusion OTBI. Most custom Form Design Aid extensions retire to Redwood UX. The OMW count that looked terrifying in the questionnaire compresses dramatically.
Each BU often built its own 30-category-code language. The crosswalk has to harmonise them into a single Fusion DFF/segment language — usually the biggest single sign-off conversation.
iSeries hardware end-of-support or RPG/COBOL skills retirement often drives the cutover window. The assessment surfaces this early so the timeline aligns to the hardware reality, not the other way round.
F47xxx EDI tables often carry 50–200 partners with custom map variants. Re-pointing them to Fusion Integration Cloud or a hybrid EDI broker becomes a sub-track in its own right.
F4801, F3112 and F31122 carry years of work-order genealogy that finance assumes is in F0911. The assessment forces an explicit decision: load to Fusion Manufacturing, archive to Parquet, or both.
Most JDE migrations we see are 3–8 instance consolidations from past acquisitions, not single-instance replacements. The assessment scopes the harmonisation work that single-instance frameworks miss.
A jd edwards migration assessment is the structured discovery phase that produces three deliverables before a single line of FBDI is generated: an inventory of every JDE EnterpriseOne (E1) and JDE World instance in scope (with backend platform, Tools release, install path-code list and unattended backup posture), a complete OMW customization catalog (every R55xxxxx UBE, P55xxxxx app, custom NER and BSFN business function, custom Form Design Aid form, custom Data Dictionary item from F9210), and a complexity score that translates those findings into a sized timeline and budget. Without it, you're estimating from a slide deck. With it, you're estimating from F9860/F9861/F98711 row counts, F0911 ledger volumes, F0006 business-unit hierarchies and F0901 account-master depth — the only numbers that actually matter. The assessment is a fixed-fee 2–4 week engagement that pays for itself the first time the consultant-led estimate gets cut in half because the OMW inventory shows 60% of the 'custom' code is reporting that retires to Fusion OTBI.
A standard jd edwards migration assessment runs 2–3 weeks for a single E1 instance, 3–4 weeks for a mixed E1 + World estate, and 4–6 weeks for an M&A-driven multi-instance consolidation with 3–8 source JDE environments. The bulk of the elapsed time is data-gathering: read-only credentials provisioned (Oracle DB / SQL Server / DB2 LUW for E1; DB2/400 ODBC or JTOpen JDBC for World), AIS Server endpoint validated where applicable, OMW catalog crawled, F-series row counts captured, integration map drawn. The output is delivered as a written assessment report plus a working session with finance leadership, IT, SCM operations and (where applicable) plant finance. The assessment is not the migration — it's the evidence base that makes the migration estimate defensible to the CFO and the steering committee.
Every OMW custom object that lives outside Oracle's shipped baseline: custom UBE batch reports (R55xxxxx prefix), custom interactive applications (P55xxxxx), custom Named Event Rules (NER) business functions, custom C business functions (BSFN) written and compiled into the BSFN DLL/SRVPGM, custom Form Design Aid forms attached to standard or custom apps, custom Report Design Aid layouts, custom data items added to F9210 (Data Dictionary), custom Vocabulary Overrides, custom processing options and custom workflow definitions. The assessment walks F9860 (Object Librarian Master), F9861 (Object Librarian Status Detail) and F98711 (Object Librarian Audit Trail) to inventory everything, then classifies each object by business purpose — GL posting logic, AP voucher creation, MRP allocation, shop-floor reporting, integration glue — and recommends a disposition: retire (Fusion does it natively), rebuild in OTBI / BI Publisher, replace with Fusion Integration Cloud extension, or carry forward as a Fusion configuration. 40–60% of objects typically retire, and that single finding compresses 3 months of scope debate.
The complexity scoring framework combines six dimensions: data volume (F0911 row count, years of history, item-ledger F4111 depth, work-order F4801 chain length), customization footprint (OMW object count weighted by classification — a custom NER GL-posting hook scores higher than a custom UBE report), integration breadth (Orchestrator integrations, AIS Server-mediated REST consumers, EDI flows via F47xxx, legacy file-drops to bank, tax, freight), COA complexity (Company × BU × Object × Subsidiary cardinality, number of distinct category-code conventions across BUs, multi-currency exposure), manufacturing depth (Fusion Manufacturing scope vs JDE-stay-Financials-only scope, routing complexity, work-order genealogy depth), and retention overlay (SOX 7yr, HGB 10yr, FDA 21 CFR Part 11, FAA, DCAA/DFARS regimes in play). Each dimension scores 1–5; the composite drives the sized timeline (12–18 weeks for low/mid complexity, 18–28 for high) and the budget range.
Every system that touches JDE today gets catalogued: inbound payment files from banks (BAI2, MT940, CAMT.053 — keyed to F0411 voucher payment matching), outbound payment files (PPD/CCD ACH, ISO 20022 pain.001), tax-engine integrations (Vertex O Series, Sovos, Avalara feeding F0411 and F03B11 tax lines), freight integrations (Descartes, project44, SMC3 feeding F4211 sales-order shipment), EDI brokers (TrueCommerce, SPS Commerce, Cleo on F47xxx transaction tables), Oracle Hyperion / EPM Cloud consolidation feeds from F0902, BI extracts to Snowflake/Databricks, custom Orchestrator flows, custom AIS Server REST consumers, and manual file-drops. Each is classified by criticality, latency requirement, and target-state pattern (replace, re-point at Fusion, retain via hybrid bridge). The integration map becomes the input to the cutover sequencing — you cannot cut Financials to Fusion before re-pointing the tax-engine feed.
Yes — World on IBM i (AS/400, iSeries) is a first-class assessment scope. The assessment captures the iSeries hardware profile (model, partition, IBM i OS release), the JDE World release (A7.3, A8.1, A9.1, A9.2, A9.4 are still in production), the data library layout (F-series tables as physical files), DB2/400 row counts via the IBM i Access ODBC or JTOpen JDBC driver, and the green-screen application footprint (custom RPG/COBOL programs in QGPL or per-instance libraries). The customization assessment for World walks the equivalent JDE World object catalog and surfaces RPG/COBOL programs that need rebuild assessment. Mixed E1 + World estates often surface a sequencing decision: cut World first to retire iSeries hardware, then cut E1; or cut both in a single wave to a unified Fusion target. The assessment gives the steering committee the data to choose.
A typical jd edwards migration assessment requires 4–8 hours per week from the following: JDE technical lead or CNC administrator (provides OMW catalog access, F9210 Data Dictionary access, environment topology), JDE functional lead per module in scope (Financials, Distribution, Manufacturing — confirms business processes), database administrator (provides read-only credentials, walks F-series row counts), integration architect (catalogs upstream/downstream system map), finance controller (validates COA scope and reconciliation expectations), and IT executive sponsor (signs off scope, budget envelope). For World assessments add an iSeries operator. Syntra ETL brings the assessment lead, JDE solution architect and (for manufacturing in scope) a manufacturing data architect. Most of the work is done by Syntra ETL against the data you provide; your team's time is interview-and-review, not data preparation.
Five deliverables make up the assessment pack. First, the JDE source inventory: every E1 and World instance in scope with platform, version, environment topology, integration footprint and F-series row-count profile. Second, the OMW customization catalog: every custom object classified by business purpose with retire/rebuild/extend/carry-forward disposition and effort estimate per object. Third, the COA crosswalk draft: F0006 + F0901 + category-code structure mapped to the proposed Fusion 6-segment COA with surfaced gaps. Fourth, the integration map: every upstream/downstream system with target-state disposition. Fifth, the sized migration plan: phased timeline (Financials first vs full-scope, single-instance vs multi-instance consolidation), budget range with sensitivity analysis, risk register, governance model, recommended cutover window aligned to fiscal calendar and (where relevant) regulatory close dates (Q4 SOX 404 attestation, German HGB year-end, FDA inspection cycles).
Two to four weeks, fixed fee, evidence-based. Walk away with an OMW catalog, COA crosswalk draft, integration map and sized timeline backed by F-series row counts — the only assessment your steering committee can defend.