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

ecord for its base process. This demand record reflects the amount of the
base process required to meet the unsatisfied demand for the co-product.
As shown in Figure 5.8, MRP passes demand records directly from the
co-product to the base process without using the co-product’s order policy
or related planning parameters.
When MRP
processes a
Regular
Item
Planned
Orders
Action
Messages
Action
Messages
A co-product is like a parent of its base process. MRP plans all items in a
site by low-level code, then by item number. Low-level codes are
determined by parent/component relationships.
Planning for Base Processes
When MRP
processes a
Co-product
Base Process
Demand
Base Process
MRP plans for a base process by determining the unsatisfied co-product
demand for all co-products that reference the base process as their BOM/
Formula code. MRP then creates planned orders to fill the unsatisfied
co-product demand without regard to projected quantities on hand for the
base process.
Unlike the planning process for regular items, MRP does not consider
base process inventory. There should never be an on-hand balance for a
base process. Use item status codes to prohibit inventory movements,
sales, purchases, and repetitive orders on base process items.
CO-PRODUCTS/BY-PRODUCTS 75
Planned
Orders for for
Base Process,
Co-P, By-P
Action
Messages for for
Base Process,
Co-product
Component
Demand
Fig. 5.8
MRP Processing of
Co-products
Ï See “Setting Up
Item Status Codes
for the Base
Process” on
page 58.