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.

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

Fig. 8.9<br />

Schedule<br />

Maintenance<br />

(18.22.2.1)<br />

If you need to replace an existing schedule, delete it manually in Schedule<br />

Maintenance, then run Repetitive Schedule Update to create a new<br />

schedule.<br />

After updating repetitive schedules, run MRP to synchronize planned<br />

orders with the schedule changes.<br />

Schedule Maintenance<br />

Use Schedule Maintenance (18.22.2.1) to enter or maintain daily<br />

schedules for each production line at a site. If the production line has<br />

multiple shifts, the schedule represents the total for all shifts. If there are<br />

no production lines at the site, you can enter a schedule for the whole site.<br />

The bill of material and routing for an item on a repetitive schedule<br />

default from Item Master Maintenance (1.4.1) or Item-Site Planning<br />

Maintenance (1.4.17). You can specify valid alternates, but you cannot<br />

<strong>com</strong>bine different BOMs and routings on one order.<br />

Exploding Repetitive Schedules<br />

Once you establish a schedule, you must explode it using Schedule<br />

Explosion (18.22.2.4). The explosion creates the material and work center<br />

operation requirements necessary to support the schedule.<br />

Until exploded, changes to the schedule are not reflected in <strong>com</strong>ponent<br />

demand or work center load. MRP reports for the <strong>com</strong>ponents or CRP<br />

reports for the affected work centers do not reflect the current repetitive<br />

schedule until it is exploded.

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

Saved successfully!

Ooh no, something went wrong!