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.

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

Fig. 12.1<br />

MRP Control File<br />

(23.24)<br />

Ï See <strong>User</strong> <strong>Guide</strong><br />

<strong>Volume</strong> 5:<br />

Supply Chain<br />

Management.<br />

MRP Control File<br />

Enter appropriate values in the MRP Control File (23.24).<br />

MRP Planning Horizon. Enter the period of time, in calendar days,<br />

which MRP should plan. MRP calculations ignore data outside this<br />

time period. The horizon should be at least one day longer than the<br />

longest item cumulative lead time in the database.<br />

If you change the MRP planning horizon, impacted items are not<br />

automatically replanned when you run net change MRP. Ensure that<br />

all items are replanned by running MRP in regenerative mode.<br />

MRP/DRP Combined. Enter Yes to indicate that MRP planned items<br />

can be planned using DRP functions. Enter No if they can only be<br />

planned using MRP functions.<br />

Summary Default. Specify the day of the week used by all MRP<br />

summary reports and inquiries when displaying item requirements<br />

summarized by week.<br />

Order Release Horizon. Enter the number of calendar days before a<br />

planned order’s release date that the Release Due For action<br />

message should appear on.<br />

The order release horizon should be based on your normal paperwork<br />

lead time and how often you run MRP. For example, if you run MRP<br />

weekly, you should set the order release horizon to at least seven<br />

days. If you run MRP daily, you can set it to zero.

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

Saved successfully!

Ooh no, something went wrong!