# Oracle Fusion Data Migration Mapping Worksheet

> Source: https://netray.co/tools/oracle-fusion-data-migration-mapping-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Map legacy fields to Oracle Fusion objects and attributes, record the transform rule, and see how many records survive cleansing.

## Category

oracle

## Erp

Oracle Fusion Cloud SCM

## Audience

- Data migration lead
- Oracle Cloud consultant
- ERP analyst

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Source table

**Key:** src_table

**Type:** text

#### Source field

**Key:** src_field

**Type:** text

#### Fusion object

**Key:** target_object

**Type:** text

#### Fusion attribute

**Key:** target_attr

**Type:** text

#### Transform

**Key:** rule

**Type:** select

**Options:**

- Direct move
- Lookup / cross reference
- Concatenate
- Default value
- Derive
- Drop

#### Source records

**Key:** records

**Type:** number

#### Known bad data

**Key:** err_pct

**Type:** number

**Unit:** %

#### Records after cleansing

**Key:** clean

**Type:** number

**Expr:** records * (100 - err_pct) / 100

**Format:** integer

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Mapped
- Loaded in test
- Signed off

**Rows:**

**Src table:** ITEM_MASTER

**Src field:** ITEM_NO

**Target object:** Item

**Target attr:** Item Number

**Rule:** Direct move

**Records:** 48200

**Err pct:** 3

**Status:** Mapped

**Src table:** ITEM_MASTER

**Src field:** UOM

**Target object:** Item

**Target attr:** Primary UOM

**Rule:** Lookup / cross reference

**Records:** 48200

**Err pct:** 1.5

**Status:** Mapped

**Src table:** VENDOR

**Src field:** VENDOR_NAME

**Target object:** Supplier

**Target attr:** Supplier Name

**Rule:** Direct move

**Records:** 2150

**Err pct:** 8

**Status:** Not started

**Src table:** ONHAND

**Src field:** QTY_ON_HAND

**Target object:** On-hand Quantity

**Target attr:** Quantity

**Rule:** Derive

**Records:** 61000

**Err pct:** 2

**Status:** Not started

**Src table:** BOM_HDR

**Src field:** PARENT_ITEM

**Target object:** Item Structure

**Target attr:** Parent Item

**Rule:** Direct move

**Records:** 9400

**Err pct:** 5

**Status:** Loaded in test

**Totals:**

#### Total source records

**Key:** records

**Agg:** sum

**Format:** integer

#### Total after cleansing

**Key:** clean

**Agg:** sum

**Format:** integer

#### Fields mapped

**Key:** src_field

**Agg:** count

**Format:** integer

**Summary:**

#### Share of records surviving cleansing

**Key:** survive_pct

**Expr:** sum_clean / sum_records * 100

**Format:** percent

**Notes:** Use the Fusion object and attribute names from the FBDI templates or the REST resource you intend to load through. Check names against your release.

## Content

**Intro:** Data migration is where Oracle Fusion SCM projects slip. This worksheet keeps the field level mapping, transform rule and cleansing status in one table that you can export and hand to the loading team.

**Sections:**

#### How to fill it in

**Body:** Start from the source side. List each legacy table and field that matters, then name the Fusion object and attribute that receives it. Choose a transform rule so developers know whether a field moves as is, needs a cross reference table, or is derived. Enter source record counts and the percentage of known bad data from profiling. The sheet then shows the records expected to pass cleansing.

#### Using the transform column

**Body:** Lookup rows deserve extra attention because each needs a published cross reference, such as legacy unit of measure to Fusion unit of measure or legacy category to catalog category. Derived rows need written logic. Drop rows should be agreed with the business, since a dropped field is often someone's report column. Keep a count of each type and review them in the mapping sign off.

**Bullets:**

- One row per source field
- Cross reference tables are deliverables
- Derived logic is written, not verbal
- Drops need business sign off

#### Reading the survival rate

**Body:** The summary divides cleansed records by source records. It is only as good as your profiling. If a high volume object such as on-hand balances or item attributes shows a poor survival rate, plan extra cleansing cycles before the mock loads. Compare it with load results from each mock cycle, because the real error rate often differs from the profiled rate.

#### Common mistakes

**Body:** Mapping to display names rather than the load column, ignoring required attributes that have no legacy source, and forgetting dependency order. Items must exist before structures, and organizations and locations before on-hand quantities. Add a sequence note in the transform column when order matters.

**Cta:** If the source is Infor SyteLine, Baan or another legacy ERP, we can profile the tables and draft the first mapping from the schema.

**Faq:**

#### Which load method should I map to?

**Answer:** Most bulk SCM loads use File Based Data Import templates, while smaller or ongoing updates often use REST services. Map to whichever you will run in production. Attribute names can differ between methods, so state the method in the Fusion object column.

#### How many mock loads do projects usually run?

**Answer:** Typically two to four full mock loads before cutover, with each cycle shrinking the error count. The right number depends on volume and cleansing quality, and the plan should hold time for a final dress rehearsal.

#### What error percentage is acceptable?

**Answer:** There is no universal threshold. Master data such as items and suppliers should be near clean, while historical transactions may be partly archived instead of migrated. Set targets per object and record them in the sign off.

#### Should inactive records be migrated?

**Answer:** Usually only if they are referenced by open transactions or needed for history. Migrating dead items inflates load times and clutters search. Agree an activity cut off date with the business.

## Search terms

oracle fusion data migration template, oracle cloud data mapping excel, legacy to oracle fusion field mapping, oracle fusion item migration mapping, erp data migration mapping sheet, oracle fusion supplier load mapping, data cleansing tracker erp

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