JD Edwards World to EnterpriseOne Data Conversion Mapping Worksheet
Moving from JD Edwards World on IBM i to EnterpriseOne is mostly a data project. This worksheet gives you one row per file or table so that nothing is converted by habit and nothing is lost without a recorded reason.
| Data domain | World file | E1 table | Cleansing or mapping rule | Source rows | Rows loaded | Rows not loaded | Owner | Status | |
|---|---|---|---|---|---|---|---|---|---|
1250 | |||||||||
6700 | |||||||||
0 | |||||||||
970000 | |||||||||
0 |
Example file and table names are the common core files that exist in both products. Confirm each mapping against your own modifications and your release. Rows not loaded should always have a written reason in the rule column.
Optional expert review of your conversion plan
Send your exported worksheet and we will point out missing domains and risky transforms.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Start with a list of every World file that holds live business data, not only the famous ones. Add one row per file, name the target E1 table, and write the rule in plain words: what you cleanse, what you drop, what you transform. Enter source row counts from a count against the file, and update rows loaded after each trial load. The gap column calculates automatically. Export to Excel and share with the business owners who sign off each domain.
- One row per file or per table group, not one row per project
- Name a business owner, not only an IT owner
- Record counts before and after every trial load
- Move status forward only with evidence attached
What the method is based on
Data conversion follows an extract, cleanse, transform, load and reconcile cycle repeated across several trial conversions. Address Book (F0101), Item Master (F4101), Item Location (F41021), Account Ledger (F0911) and Sales Order Detail (F4211) usually come first because everything else points at them. A reconciliation compares counts and control totals between source and target, for example ledger balances by account and period.
Reading the summary
The percent loaded figure is not a quality score. A low number can be healthy if you deliberately retire old items or history. What matters is that every gap is explained. Review any row where rows loaded exceeds source rows, which means the transform is creating records, and any row marked signed off with a gap and no rule text.
Common mistakes
Teams often map only the tables they know and discover user-defined codes, next numbers, and custom files late. Another frequent problem is cleansing in the source system during the project, which moves the target while you test. Freeze cleansing rules per trial cycle and log changes. Finally, do not treat open transactions and history the same way: open items need exact conversion, history can often be summarized.
Frequently Asked Questions
Is this worksheet specific to one release of World?
No. It is a planning tool. The sample file names are common core files, but you should verify every mapping against your own release, your modifications and the E1 release you are targeting before you build conversion programs.
Should I convert all history?
Usually not. Convert open transactions exactly, a defined number of recent financial periods in detail, and summarize or archive the rest. The decision belongs to finance, audit and legal, so record it in the rule column.
How many trial conversions are normal?
Most projects plan at least three trial loads plus a dress rehearsal of the cutover. The number depends on data volume, cleansing effort and how many modifications touch the data model.
Can I import the worksheet into Excel?
Yes. Use the export button to download Excel or CSV. The calculated gap column and totals are exported with the rows so you can keep tracking in a shared workbook.
If you want help profiling World files and drafting conversion rules from your real data, Netray can review your mapping sheet and suggest where AI-assisted matching saves effort.
Related Tools
JD Edwards World Custom Program and Modification Inventory Worksheet
Editable inventory of custom programs, modified objects and custom files with business criticality and a retire, keep or replace decision.
ERP Migration & SelectionERP Cutover and Go-Live Plan Template for IBM i Migrations
Fill-in cutover plan for migrating from an IBM i ERP: freeze window, final data load, validation, go or no-go criteria and rollback.
Costing & FinanceJD Edwards World Month-End Close Procedure Template
Fill-in month-end close procedure with subledger cutoffs, reconciliations, posting steps, period lock and sign-off lines for a World finance team.
More Oracle tools
See all- JDE World DREAM Writer Version Documentation Template
- JD Edwards World Key File Reference Table
- IBM i Power Hosting Cost Comparison Calculator
- JD Edwards World Custom Object Conversion Effort Calculator
- IBM i Batch Window Capacity Calculator
- AS/400 Disk Storage Growth Forecast Calculator
- IBM i Restore Time and RTO Calculator
- AS/400 Skills Succession Risk Assessment
- IBM i System Values Reference
New to JD Edwards World? Start with the JD Edwards World guide and toolkit.
Keep exploring
Free tools
- JD Edwards World Key File Reference TableA searchable lookup of widely used JD Edwards World files with the module, purpose and key field prefix, useful for queries, reports and migration mapping.
- JD Edwards World AI Assistant Sizing and Value CalculatorEstimate peak load, GPUs, index size, hours saved and payback for an on-prem AI assistant on JD Edwards World.
- JD Edwards World Private AI Layer Blueprint GeneratorFill in your JD Edwards World version, database, hosting and users to get a shareable architecture plan for a private, on-prem AI assistant.
ERP fixes and how-tos
- JD Edwards table conversion: how it works and how to run oneWhat a JD Edwards table conversion does to a JDE table's structure and data, when it runs in a package build, and how to run or design one manually.
- How to Add a Private AI Layer to JD Edwards World on IBM iAdd AI to JD Edwards World without moving data: DB2 for i access, journal-based replication, rebuilt row security, local GPUs and approved batch write-back.
- How to Add a Private AI Layer to JD Edwards EnterpriseOne On-PremAdd a private AI layer to JD Edwards EnterpriseOne: AIS data service, Orchestrator, Security Workbench mapping, a local model and human approval.
Runs with your ERP
- Vertex Tax Connectors with JD Edwards EnterpriseOneHow Vertex calculates sales, use and VAT tax for JD Edwards EnterpriseOne and World, plus Oracle EBS and Cloud ERP: integration model, flows, setup, pitfalls.
- RF-SMART and JD Edwards EnterpriseOne: Barcode Scanning and Mobile WMSHow RF-SMART connects barcode scanning to JD Edwards EnterpriseOne and World: integration method, data flows, setup steps, pitfalls and where private AI helps.
- RF-SMART Manufacturing Data Collection for JD Edwards WorldShop floor barcode data collection for JD Edwards World with RF-SMART: what it reports, how it connects, setup steps, pitfalls and a private AI layer on top.
AI on your ERP
- AI for JD Edwards World on IBM i, without a EnterpriseOne migrationAdd AI to JD Edwards World on IBM i without replatforming: read the physical files safely, ground an LLM on your data, and keep control on the box you already run.
- AI for JD Edwards EnterpriseOne Manufacturing, Without Leaving the F-Tables ExposedGrounded AI over JD Edwards EnterpriseOne Manufacturing: work orders, routings, and Orchestrator data, answered on-prem without sending F-table data to a public model.
Integrations
- How to add AI agents to JD Edwards World on IBM iHow to add AI agents to JD Edwards World on IBM i: a read-first tool layer over DB2 for i, human approval before any write, and a fully on-prem model option.
- How to use ChatGPT with JD Edwards WorldUsing ChatGPT with JD Edwards World on IBM i: custom GPT actions vs data exports, enterprise data controls, and when a private model is the better fit.