# JD Edwards World to EnterpriseOne Data Conversion Mapping Worksheet

> Source: https://netray.co/tools/jde-world-to-e1-data-conversion-mapping-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Editable worksheet that tracks every World file you convert to EnterpriseOne: source, target, cleansing rule, record counts, owner and status.

## Category

oracle

## Erp

Oracle JD Edwards World

## Audience

- JDE consultant
- IBM i administrator
- ERP project manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Data domain

**Key:** domain

**Type:** select

**Options:**

- Address Book
- Item
- Sales
- Purchasing
- Inventory
- Finance
- Manufacturing
- Other

#### World file

**Key:** source

**Type:** text

#### E1 table

**Key:** target

**Type:** text

#### Cleansing or mapping rule

**Key:** rule

**Type:** text

#### Source rows

**Key:** src_rows

**Type:** number

#### Rows loaded

**Key:** load_rows

**Type:** number

#### Rows not loaded

**Key:** gap

**Type:** number

**Expr:** src_rows - load_rows

#### Owner

**Key:** owner

**Type:** text

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Mapped
- Test loaded
- Reconciled
- Signed off

**Rows:**

**Domain:** Address Book

**Source:** F0101

**Target:** F0101

**Rule:** Merge duplicate AN8 records, standardize search type

**Src rows:** 48200

**Load rows:** 46950

**Owner:** Data steward

**Status:** Test loaded

**Domain:** Item

**Source:** F4101

**Target:** F4101

**Rule:** Retire items with no activity in 5 years

**Src rows:** 31500

**Load rows:** 24800

**Owner:** Materials lead

**Status:** Mapped

**Domain:** Inventory

**Source:** F41021

**Target:** F41021

**Rule:** Load on-hand by location after physical count

**Src rows:** 66300

**Load rows:** 66300

**Owner:** Warehouse manager

**Status:** Not started

**Domain:** Finance

**Source:** F0911

**Target:** F0911

**Rule:** Convert open year plus two prior years, summarize older

**Src rows:** 2150000

**Load rows:** 1180000

**Owner:** Controller

**Status:** Mapped

**Domain:** Sales

**Source:** F4211

**Target:** F4211

**Rule:** Open orders only, re-point to new business units

**Src rows:** 5400

**Load rows:** 5400

**Owner:** Order desk lead

**Status:** Not started

**Totals:**

#### Total source rows

**Key:** src_rows

**Agg:** sum

**Format:** integer

#### Total rows loaded

**Key:** load_rows

**Agg:** sum

**Format:** integer

#### Total rows not loaded

**Key:** gap

**Agg:** sum

**Format:** integer

**Summary:**

#### Share of source rows loaded

**Key:** load_pct

**Expr:** if(gt(sum_src_rows,0), sum_load_rows / sum_src_rows * 100, 0)

**Format:** percent

**Primary:** true

#### Mappings tracked

**Key:** tables

**Expr:** count

**Format:** integer

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the worksheet

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Is this worksheet specific to one release of World?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

jde world to e1 data conversion, jd edwards world to enterpriseone migration excel, jde data mapping template, world to e1 conversion plan, jde world file to table mapping, jd edwards data cleansing worksheet, jde upgrade data migration tracker

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
