# Oracle Fusion Manufacturing Work Definition Worksheet

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

## Short answer

Design routing operations before you key them in. Capture work centers, setup and run times, yield and the total time for an order quantity.

## Category

oracle

## Erp

Oracle Fusion Cloud Manufacturing

## Industry

Discrete Manufacturing

## Audience

- Manufacturing engineer
- Oracle Cloud consultant
- Production planner

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Op seq

**Key:** seq

**Type:** number

#### Work center

**Key:** wc

**Type:** text

#### Operation

**Key:** opname

**Type:** text

#### Type

**Key:** optype

**Type:** select

**Options:**

- In-house
- Outside processing
- Inspection

#### Setup time

**Key:** setup

**Type:** number

**Unit:** min

#### Run time per unit

**Key:** run

**Type:** number

**Unit:** min

#### Order quantity

**Key:** qty

**Type:** number

#### Operation yield

**Key:** yield

**Type:** number

**Unit:** %

#### Total minutes

**Key:** total

**Type:** number

**Expr:** setup + run * qty / (yield / 100)

**Format:** minutes

**Rows:**

**Seq:** 10

**Wc:** SAW01

**Opname:** Cut bar stock

**Optype:** In-house

**Setup:** 20

**Run:** 1.5

**Qty:** 200

**Yield:** 99

**Seq:** 20

**Wc:** CNC03

**Opname:** Turn and drill

**Optype:** In-house

**Setup:** 60

**Run:** 6

**Qty:** 200

**Yield:** 97

**Seq:** 30

**Wc:** INSP1

**Opname:** In-process inspection

**Optype:** Inspection

**Setup:** 10

**Run:** 0.8

**Qty:** 200

**Yield:** 100

**Seq:** 40

**Wc:** OSP-HT

**Opname:** Heat treat

**Optype:** Outside processing

**Setup:** 0

**Run:** 0.5

**Qty:** 200

**Yield:** 100

**Seq:** 50

**Wc:** GRD02

**Opname:** Finish grind

**Optype:** In-house

**Setup:** 45

**Run:** 3.2

**Qty:** 200

**Yield:** 98

**Totals:**

#### Total minutes

**Key:** total

**Agg:** sum

**Format:** minutes

#### Total setup

**Key:** setup

**Agg:** sum

**Format:** minutes

#### Operations

**Key:** seq

**Agg:** count

**Format:** integer

**Summary:**

#### Total hours

**Key:** hours

**Expr:** sum_total / 60

**Format:** hours

#### Setup share of total time

**Key:** setup_share

**Expr:** sum_setup / sum_total * 100

**Format:** percent

**Notes:** Yield here is a planning factor applied per operation. Compare the result with the times you plan to enter on the work definition operations and resources.

## Content

**Intro:** Before keying a work definition into Oracle Fusion Manufacturing, plan the operations on one page. This worksheet captures sequence, work center, times and yield and tells you the total time for a given order quantity.

**Sections:**

#### How to use it

**Body:** List the operations in sequence, using steps of ten so there is room to insert later. For each, enter the work center, the setup time, the run time per unit and the order quantity. The yield column inflates the time to cover scrap at that operation. The total column uses setup plus run time times quantity divided by yield. Use the output to check that the routing agrees with what the shop floor actually does.

#### Mapping to Fusion

**Body:** In Fusion, a work definition carries operations, work centers, resources and item structure components for a manufactured item. Resource usage and the scheduling basis drive time. Outside processing operations normally tie to a supplier and purchase order. Use this worksheet to agree values with engineering before they are keyed, and keep the version for the audit trail of why times changed.

**Bullets:**

- Check the work center and resource setup first
- Decide the scheduling basis per resource
- Treat outside processing separately
- Agree yield assumptions with quality

#### Reading the results

**Body:** The setup share shows how sensitive the routing is to batch size. A high share means small orders are expensive and that lot sizing deserves attention in supply planning. Compare total hours with the capacity you set in the work center to see if the routing is credible. Try one small and one large quantity and compare.

#### Common mistakes

**Body:** Copying standard times from the old ERP without checking them, mixing minutes and hours across rows, and applying yield twice, once here and again in the item or cost setup. Decide where scrap is modelled and apply it in one place only.

**Cta:** If routings live in a legacy ERP such as SyteLine or Baan, we can help extract and reshape them into work definition candidates.

**Faq:**

#### What is a work definition in Oracle Fusion?

**Answer:** It describes how a manufactured item is made: the operations, the work centers and resources used, and the components consumed at each step. Work orders are created from it and inherit operations, quantities and scheduling information.

#### Should setup time be per order or per unit?

**Answer:** Setup is normally incurred once per run, so enter it as a fixed amount per order. Run time is per unit. If your plant has changeovers that depend on the previous product, document that rule and keep it out of the base time.

#### How do I include scrap?

**Answer:** Use one place only. Either increase the operation yield here and in the item setup, or apply a shrink factor in planning. Doing both double counts the loss and overstates material and capacity needs.

#### Does this replace routing validation on the shop floor?

**Answer:** No. It is a planning aid. Validate against time studies or recent actuals before the times go live, and review them after the first production cycles.

## Search terms

oracle fusion work definition template, oracle cloud manufacturing routing worksheet, oracle fusion work definition operations, routing design template excel, oracle fusion manufacturing setup, work center operation time worksheet, oracle fusion work definition planning

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