Oracle Fusion · SCM · Master data

Oracle Fusion Item Data Migration

Migrate item master data into Oracle Fusion Product Management, covering the master item, organisation assignments, categories, units of measure, item attributes and costing.

Discuss Your Migration All Migration Objects

Object overview

Fusion separates the item definition from where it is used. An item is created once in the master organisation and then assigned to each inventory organisation that transacts it, with attributes that can differ per organisation. One legacy item row therefore becomes one master item plus N organisation assignments.

Attribute volume is what makes this object heavy. Items carry hundreds of controlled attributes — planning, purchasing, costing, inventory, invoicing — and most legacy sources populate only some of them, so defaulting rules matter as much as mapping.

What data is typically migrated

Scope is agreed in discovery; this is the shape of the object.

Data area	Typical information
Master item	Item number, description, item class, status, primary UOM, lifecycle phase
Organisation assignment	Which inventory organisations carry the item
Categories	Catalog and category assignments driving accounting and reporting
Units of measure	Primary UOM, conversions, secondary UOM where dual UOM applies
Attributes	Planning, purchasing, costing, inventory and invoicing attribute groups
Cost	Standard or average cost per organisation and cost book
Cross-references	Supplier part numbers, customer item numbers, legacy identifiers

Object relationships

Dependency drives load sequence: a child cannot exist before its parent.

Master organisation

└─ Master item

└─ Organisation assignment

└─ Org-specific attributes

└─ Item cost

└─ Catalog / category assignment

└─ UOM conversions

└─ Cross-references

Object migration flow

Source Items→DataMove→Map & transform→Validate→Oracle Fusion Items→DataVault reconciliation→Sign-off

Before you migrate this object

Confirm each of these before the first migration cycle.

□Inventory organisations and the master organisation are configured

□Units of measure and conversions are loaded

□Item classes and attribute groups are defined

□Catalogs and categories exist

□The item numbering strategy is agreed

□Attribute defaulting rules are documented and approved

□Obsolete-item policy is agreed

Common source systems

Production-proven means we have delivered this object from that source. Supported and custom-mapping describe capability, not delivery history.

Oracle EBS Production-provenSAP ECC Production-provenSAP S/4HANA SupportedMicrosoft Dynamics 365 SupportedOracle JD Edwards Supported

Source-to-target mapping examples

Object-level equivalence. Field-level mapping is produced per engagement.

Source system	Source entity	Target object
Oracle EBS	MTL System Items (master + org rows)	Fusion Master Item + Org assignments
SAP ECC	Material master (MARA + MARC + MBEW)	Fusion Item + Org assignments + Cost
Dynamics 365	Released product + product master	Fusion Item + Org assignments

Migration methods for this object

Product Hub / Item Import FBDI (item, org assignment, category, cross-reference files)

Item REST services for incremental maintenance

Separate cost load per cost book and organisation

Extraction considerations

Plant and organisation rows are the expansionSAP MARC and EBS org rows are what become Fusion organisation assignments. Extracting only the general view produces items nobody can transact.

Obsolete and blocked itemsItems with stock, open orders or historical transactions must migrate even when obsolete, or the dependent objects fail.

Dual unit of measureIndustries using catch weight carry two UOMs per item. If the source uses dual UOM the target must be configured for it before extraction design is finalised.

Attribute sparsityLegacy items often populate a small fraction of available attributes. Profiling which attributes are actually used prevents mapping work on fields that are always null.

Transformation rules

Item number strategyRetain the legacy number or generate new with the legacy value as a cross-reference. This decision propagates into every transactional object.

Item class and attribute groupsLegacy material types map onto Fusion item classes, which control which attribute groups apply.

UOM crosswalk and conversionsSource UOM codes map to Fusion UOMs, and conversion factors are carried so quantities remain correct.

Category assignmentLegacy material groups become catalog category assignments, which drive default accounting.

Attribute defaultingWhere the source has no value and Fusion requires one, the default is a documented business rule rather than a load-time guess.

Data quality and validation

Primary UOM exists

And any conversions referenced are defined.

Organisation exists

Every assignment references a configured inventory organisation.

Item class and category exist

With their attribute groups configured.

Mandatory attributes populated

Per item class, which differs by class.

Duplicate item number

Within the master organisation.

Cost is present where required

For standard-costed organisations.

Load sequence and dependencies

What has to exist before this object can load.

1Inventory organisations and cost books
2Units of measure and conversions
3Catalogs and categories
4Item classes and attribute groups
5Master items
6Organisation assignments
7Category assignments
8Item costs
9Cross-references

Common migration errors

What actually fails on this object, and why.

Organisation not foundThe assignment references an inventory organisation that does not exist.

UOM not definedThe primary UOM or a conversion is missing.

Mandatory attribute missing for item classThe class requires an attribute the source does not populate and no default was defined.

Duplicate item numberTwo source records collapsed onto one target number, common in a multi-source consolidation.

Invalid category assignmentThe category does not exist in the assigned catalog.

Cost missing in a standard cost organisationTransactions cannot be valued.

Reconciliation

Counts alone rarely prove this object migrated correctly.

Master item count: source distinct items vs loaded

Organisation assignment count against the expected item-to-organisation matrix

Item count by category and by item class

Items with on-hand stock reconciled at 100% — these gate the inventory load

Cost coverage: every item in a standard cost organisation has a cost

Cross-reference completeness for supplier and customer part numbers

How Syntra ETL supports this object

DataMove

Extraction, mapping, transformation, validation preparation and target load generation.

Explore DataMove →

DataVault

Preserves source, prepared and target states for reconciliation, lineage and audit evidence.

Explore DataVault →

DataLens

Migration progress, data quality, exceptions and readiness across cycles.

Explore DataLens →

Relevant migration routes

Source-specific guidance for moving this object.

SAP ECC→Oracle Fusion

Successfully delivered projects involving this object

Published case studies whose scope included items.

Oracle EBS→Oracle FusionMajor Saudi Government OrganizationGovernment · Middle East

18 Business units
1M+ Inventory items
5× Faster than manual loading

Loaded roughly five times faster than manual loading, with every object reconciled.DELIVERED WITH GLOBAL SIView Project →

Frequently asked questions

Why does one legacy item become several Fusion records?

Because Fusion defines an item once in the master organisation and then assigns it to each inventory organisation that transacts it. An item used in five plants becomes one master item and five organisation assignments.

Should obsolete items be migrated?

Any item with on-hand stock, open orders or in-scope transaction history must migrate, regardless of status. Genuinely dead items with no dependencies can be excluded and archived.

How are item attributes handled when the source does not populate them?

Through documented defaulting rules agreed with the business. Fusion enforces mandatory attributes per item class, so a null in the source has to become something deliberate rather than a load-time guess.

Do item costs migrate with the item?

As a separate load, per organisation and per cost book. Standard-costed organisations require a cost before transactions can be valued, so cost coverage is a validation in its own right.

Planning a similar data migration?

Tell us your source application, target system, object scope, volume and migration timeline. We can discuss the recommended migration approach and relevant Syntra ETL project experience.

Discuss Your Migration Explore Migration Routes