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.

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

Ï See “Simulating<br />

Schedules in the<br />

Workbench” on<br />

page 149.<br />

Ï See “Creating<br />

Repetitive<br />

Schedules” on<br />

page 153.<br />

Ï See “Using<br />

Repetitive<br />

Picklists” on<br />

page 155.<br />

Ï See “Managing<br />

Cumulative<br />

Orders” on<br />

page 160.<br />

Ï See Chapter 7,<br />

“Shop Floor<br />

Control,” on<br />

page 125.<br />

Simulating Schedules in the Workbench<br />

Line Schedule Workbench (18.1.10) is exactly the same as the workbench<br />

(18.22.1.10) in Advanced Repetitive.<br />

Creating and Exploding Repetitive<br />

Schedules<br />

These functions are almost identical in the two modules. Internally, the<br />

system processes additional information for Advanced Repetitive<br />

schedules, but the interface and input values are the same.<br />

Using Repetitive Picklists<br />

The functions on Repetitive Picklist Menu (18.8) are identical to the<br />

functions on Picklist Menu (18.23.3).<br />

Managing Cumulative Orders<br />

Cumulative orders track repetitive activities in much the same way as in<br />

Advanced Repetitive. Cumulative orders can be added manually using<br />

Cumulative Order Maintenance (18.9). However, its primary purpose is to<br />

change the status of an existing cumulative order to Closed so that<br />

Cumulative Order Accounting Close (18.12) can be used. Cumulative<br />

orders should remain open for the periods used by accounting to monitor<br />

WIP costs. Procedures should be in place to ensure they are closed at the<br />

end of each fiscal month or period.<br />

Executing Repetitive Transactions<br />

Repetitive transactions provide feedback for repetitive operations. Like<br />

those in the Shop Floor Control module, they require use of an employee<br />

code. Repetitive Labor Transaction is an exception, because it triggers<br />

inventory transactions to backflush <strong>com</strong>ponents and receive <strong>com</strong>pleted<br />

units.

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

Saved successfully!

Ooh no, something went wrong!