Work Orders > Creating Work Orders > Work Order Type
  
Work Order Type
Most work orders are entered with a blank type. These represent normal manufacturing orders with a standard product structure and routing. The other types indicate special kinds of work orders.
Work Order Types lists work order type codes.

Work Order Types
 
Type Code
Description
 
Type Code
Description
Blank
Standard
 
S
Scheduled
F
Final Assembly
 
C
Cumulative
R
Rework
 
W
Flow
E
Expense
 
 
 
All work order types are similar in terms of planning, inventory, and accounting. They differ in their default bills, routings, and status codes. These defaults are shown in Work Order Type Defaults for each order type.
See Work Order Status for more details.
Note: Scheduled and cumulative orders are managed using repetitive functions and are not included in this table.

Work Order Type Defaults
 
Work Order
Type
Type
Code
Default
Bill
Default
Routing
Default
Status
Standard
blank
Standard
Standard
Firm Planned
Rework
R
Parent Item
None
Allocated
Final Assembly
F
Sales Order
Standard
Exploded
Expense
E
None
None
Released
Flow
W
Standard
Standard
Exploded
Rework Work Orders
Use rework orders to manage repair, reprocessing, or completion of non-conforming items. A rework order has the parent item as its only component, and no routing.
You can create an R type work order when the following conditions exist:
You define a site and set Use Plan/Sched Workbenches to Yes in Site Maintenance.
You define the item and set Pur/Mfg to L in Item Planning Maintenence.
After creating a rework order, you can modify its bill and routing by adding components and operations before it is released. If additional items are needed, use Work Order Component Issue (16.10) or directly modify the bill using Work Order Bill Maintenance (16.13.1).
If rework activity is a common procedure, consider establishing a rework routing in Routing Maintenance (14.13.1) and attaching it in Work Order Maintenance (16.1), or create one in Work Order Bill Maintenance (16.13.1).
If you are using the Service/Support Management module to receive items from customers and rework them, you can establish default service routings in Service Item Maintenance (11.3.7).
In Work Order Maintenance (16.1), set the WIP account, sub-account, cost center, and project to an appropriate expense account for posting rework costs.
Final Assembly Work Orders
Final assembly (FAS) orders are used to manufacture configured products of type assemble to order (ATO). Kit-configured items do not require a work order. These are indicated by a Pur/Mfg code of Configured in Item Master Maintenance (1.4.1). FAS orders are generated when a sales order for a configured product is released to manufacturing using Sales Order Release to Work Order (8.13).
An FAS order uses the standard item routing, but its BOM contain only the items specified in the sales order configuration. Release and process FAS orders the same as regular work orders.
See User Guide: QAD Sales for more information about configured items.
Expense Work Orders
Use expense work orders for non-inventory jobs, such as engineering prototypes or design projects. Expense work orders have no bill or routing, but you can attach these manually as needed.
You can create an E type work order when the following conditions exist:
You define a site and set Use Plan/Sched Workbenches to Yes in Site Maintenance.
You define the item and set Pur/Mfg to L in Item Planning Maintenance.
Note: You should define a separate site, item code, and product line for expense orders to keep their planning and manufacturing separate from regular manufacturing.
To separate cost accounting, specify an expense account rather than the default WIP account. Or use the Project field to track expenses in the GL.
If you process expense work orders frequently, streamline the process by:
1 Creating a product line with account numbers for this type of work.
2 Creating an item of type E to use for expense orders. Define a blank order quantity to prevent planning functions from treating it like a normal item.
3 Creating a status code that restricts all inventory transactions and assign it to the item.
Scheduled Work Orders
Scheduled work orders are generated by the system when repetitive schedules are entered. Like standard work orders, they have a standard work order bill and routing.
A scheduled work order cannot be processed as a standard work order unless you change its status to Allocated or Released. Changing a scheduled order to a regular order automatically updates the repetitive schedule to exclude it; however, the work order type remains Scheduled.
See Advanced Repetitive and Repetitive for more information on scheduled orders.
Cumulative Work Orders
Cumulative orders are generated by the system to track repetitive production costs. They cannot be processed using work order functions.
See Managing Cumulative Orders.
Routable Work Orders
The system manages one other kind of work order that is not represented by a separate type code. Subassemblies can be set up so that work orders are automatically created for them when a parent item is allocated or released using:
Work Order Release/Print (16.6; 16.30 for enhanced .NET UI version)
Multiple Work Order Release/Print (16.7)
To do this, set the Pur/Mfg code for the item to Routable in Item Master Maintenance (1.4.1) or Item Planning Maintenance (1.4.7). A work order for a routable item has the same number as the parent work order, but a unique work order ID.
These work orders can be allocated, released, and used for processing component issues, inventory receipts, and shop floor control transactions. When the subassembly is finished:
Process a work order receipt from the routable work order.
Then issue the subassembly as a component to the parent work order.
Flow Work Order
Flow work orders are generated by the system when flow scheduled orders are entered and do not include a reference to an existing standard work order. Like standard work orders, they have a standard work order bill and routing.
A flow work order cannot be processed as a standard work order. It is automatically updated when you process the associated flow scheduled order.