OracleFree worksheetPDF, Excel, Word exportOracle Fusion Cloud ManufacturingDiscrete Manufacturing

Oracle Fusion Manufacturing Work Definition Worksheet

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.

Download:
Op seqWork centerOperationTypeSetup time (min)Run time per unit (min)Order quantityOperation yield (%)Total minutes
323 min
1,297.1 min
170 min
100 min
698.1 min
Total minutes
2,588.2 min
Total setup
135 min
Operations
5
Total hours
43 hrs
Setup share of total time
5.2%

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.

Want routings converted from your legacy ERP?

Optional expert review of legacy routings before they become work definitions.

Optional. The tool and every export work without this. No spam.

How to use it

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

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.

  • 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

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

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.

Frequently Asked Questions

What is a work definition in Oracle Fusion?

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?

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?

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?

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.

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