OracleFree worksheetPDF, Excel, Word exportOracle E-Business SuiteDiscrete ManufacturingAll Oracle E-Business Suite tools

Oracle EBS Routing and Operations Load Worksheet

Routing data is one of the heaviest conversion objects in an Oracle EBS manufacturing project. This worksheet gives engineers and consultants a clean layout for operations and resources, with hours and cost per lot calculated so errors surface before load.

Free, optional. Reopen it on any device.

Download:

Total hours per lot	Hours per unit	Resource cost per lot
6 hrs	0.055	$209
14 hrs	0.135	$1,013
20 hrs	0.2025	$648
18 hrs	0.45	$1,350
5 hrs	0.125	$225

Total hours (all lines)

62 hrs

Total resource cost

$3,445

Average cost per operation line

$689

Basis is recorded for documentation. Oracle treats Item basis as per unit and Lot basis as once per lot, so for Lot basis resources enter the full run hours per lot in the lot hours logic you adopt and adjust the formula in your own copy.

Routing migration review

Optional expert review of your routing conversion approach and data quality checks.

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

Was this tool useful?

How to use it

List one row per operation and resource per assembly. Enter the department, resource, setup hours, run hours per unit and the lot size you plan against. The sheet calculates total hours per lot, hours per unit and resource cost. Sort by assembly, then operation sequence, to review each routing in order. Export to Excel and use it as the source for your load file, or as the reviewed baseline for a manual keying session.

Use consistent operation sequence steps such as 10, 20, 30 to leave room for later inserts
Validate departments and resources against your setup before loading
Keep one lot size per assembly for like-for-like comparison

What the numbers mean

Total hours per lot is setup plus run per unit times lot size. Hours per unit spreads setup across the lot, so small lots look more expensive per unit, which is the whole point of lot sizing. Resource cost multiplies hours by the rate and is a planning indicator, not the costing result. Costing in Oracle uses the resource rates and overhead rules defined in the cost organization.

Routing fields in Oracle EBS

A routing in Oracle Bills of Material is made of operations, which belong to departments, and operations hold resources with usage rate, basis, assigned units and scheduling flags. Resources can be scheduled or not, charged or not, and may use autocharge types such as WIP move or manual. These choices drive scheduling, costing and shop floor reporting, so capture them as extra columns in your own copy if your project needs them.

Common mistakes

The most frequent issues are inconsistent units for run time, mixing minutes and hours across source systems, and reusing a resource at multiple operations without checking capacity. Also check for operations without a department, resources not assigned to the department, and routings missing a final operation for move transactions. Reconcile total hours against the legacy system to catch conversion errors early.

Frequently Asked Questions

Is this the Oracle open interface format?

No. It is a planning and review layout. Use it to prepare and check the data, then map it to the columns required by your chosen load method, such as the open interface tables or a loader tool.

Why do I need lot size on the sheet?

Lot size is needed to turn per-unit run time and one-off setup into a total for a lot, and to see how setup is spread. It is also useful when comparing lot sizes.

Can I use minutes instead of hours?

Yes, but be consistent. Convert by dividing minutes by 60 before entering, since the sheet and Oracle resource usage rates are normally expressed in hours.