20.06.2013 Views

MFG/PRO 9.0 User Guide Volume 3: Manufacturing - QAD.com

MFG/PRO 9.0 User Guide Volume 3: Manufacturing - QAD.com

MFG/PRO 9.0 User Guide Volume 3: Manufacturing - QAD.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

98 <strong>MFG</strong>/<strong>PRO</strong> USER GUIDE — MANUFACTURING<br />

Table 6.4<br />

Work Order<br />

Life Cycle<br />

Work Order Status<br />

Work order status codes correspond to stages in a work order’s life cycle.<br />

• Planned<br />

• Firm planned<br />

• Batch<br />

• Exploded<br />

• Allocated<br />

• Released<br />

• Closed<br />

The status of a work order determines how much control you have over its<br />

bill, routing, inventory allocations, inventory transactions, and labor<br />

feedback.<br />

• You cannot make any changes to orders with status Planned. These<br />

are managed by MRP.<br />

• For orders with status Firm Planned, you can change the dates and<br />

quantities as needed, and specify an approved alternate bill or routing.<br />

• For orders with status Exploded, Allocated, or Released, bills and<br />

routings can be modified or alternate ones specified.<br />

A work order progresses from one status code to the next and, unless<br />

prematurely released, does not return to an earlier status.<br />

Type Code Description Life Cycle<br />

[Blank] Standard Planned—Firm Planned—Exploded—Allocated—<br />

Released—Closed<br />

F Final Assembly Exploded—Allocated—Released—Closed<br />

R Rework Allocated—Released—Closed<br />

E Expense Released—Closed<br />

S Scheduled Exploded—Closed<br />

C Cumulative Released—Closed<br />

After entering an order, change its status to Firm Planned, Exploded, or<br />

Allocated using Multiple Work Order Status Change (16.8). Table 6.5<br />

shows how the status changes affect a work order’s BOM and routing.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!