Migrate your Oracle Manufacturing Cloud data

Work Orders are the primary production execution record in Oracle Manufacturing Cloud. We export the full work order hierarchy including status, quantities, scheduled dates, and operations routing. The work order must reference an active Item and Work Definition before import; we sequence these so dependencies are satisfied in order.

Work Definitions define the routing steps for manufacturing an item. We export the operation sequence, work center assignments, and step-level details. A migration-critical gotcha: the work definition start date must match or precede the cost scenario effective date or costs will not roll up—we flag this during scoping.

Items are the master product records that drive BOMs and work definitions. We export item attributes including item class, uom, and the make-or-buy flag. Oracle's item numbering convention must match destination requirements, and we flag any custom attributes for explicit mapping.

Manufacturing Plants define the organizational unit where production occurs. We export the plant hierarchy and calendar associations. The plant must exist in the destination before work orders can be assigned to it.

Work Centers represent production resources (machines, labor pools, departments). We export capacity, availability rules, and the UOM overrides at the work center level. These must land before work definitions can reference them.

Manufacturing Calendars define plant working times and shift patterns. We export the calendar definition and its shift assignments. The calendar must be imported before the plant that references it becomes active.

Cost Scenarios define material, resource, and overhead costs. We export cost element mappings but the effective date must be explicitly handled—it must equal or follow the work definition start date, or cost rollup silently fails in Oracle. We flag this as a required mapping decision during scoping.

Smart Operations Configurations include UOM defaults at plant level, work center UOM overrides, reason codes, operator assignment rules, and target metrics (plan adherence, OEE). These export and import via CSV through the Functional Setup Manager. Custom or manually entered configurations may fail import due to row-key mismatches—We flag all non-Gold-environment configurations for explicit review.

BOMs define the component structure for each item. We export the multi-level BOM hierarchy including co-products and by-products. The destination must have the same item structure for BOM lines to resolve correctly.

Custom Objects are created via Oracle Application Composer and are environment-specific. We export the object definition and data, but a key limitation: manually creating a custom object in the target environment and then running an import of the same object can cause metadata inconsistency beyond repair. We require customers to use Gold-environment exports only for custom object data.

Attachments associated with work orders, items, and work definitions are exported via Oracle's document management. File type, size limits, and the attachment association metadata require explicit mapping during the export scoping phase.

Production Sequences govern the order of operations execution. We export sequence definitions and their step associations. Mixed-mode production environments require explicit mapping of co-product and by-product sequence rules.

Departments represent organizational cost and responsibility centers. We export department definitions and their association to work centers. Departments must exist in the destination before cost accounting assignments can complete.

Reason Codes are used at workstations to explain production variances and exceptions. We export the reason code set and its usage context. Reason codes are environment-specific and must be imported via the Functional Setup Manager CSV process.