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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

You can transfer inventory even if a picklist has not been created or<br />

printed. Use the Alloc and Picked fields to set the default for your<br />

transfers. You can also directly specify inventory to issue.<br />

After issuing inventory, the system records an ISS-TR transaction and a<br />

RCT-TR transaction in the transaction history file.<br />

Managing Cumulative Orders<br />

The system keeps a running total for each <strong>com</strong>bination of items, sites,<br />

production lines, product structures, and routings using a cumulative<br />

order. The cumulative order tracks costs and quantities for work-inprocess<br />

(WIP) for repetitive production. A cumulative order is created for<br />

a profile that defines the site, item number, production line, routing code,<br />

BOM/formula code for the order, and start and end effective dates.<br />

Cumulative orders can be created three ways.<br />

• Automatically by the system when you execute a repetitive<br />

transaction (18.22.13 –18.22.21)<br />

• One at a time with Cumulative Order Maintenance (18.22.6)<br />

• In a batch with Cumulative Order Create (18.22.11)<br />

When a cumulative order is created, a cost rollup establishes the<br />

cumulative order cost. Cumulative orders have an assigned ID number,<br />

but no order number.<br />

Repetitive transactions create a cumulative order when they cannot find<br />

one with the same profile (site, item, production line, routing, BOM/<br />

formula code) where the transaction effective date does not fall within the<br />

effective date range of an existing cumulative order. The start and end<br />

effective dates are determined using the parameters in the Repetitive<br />

Control File.<br />

During transaction processing, the system captures rate variances and<br />

creates GL entries. Usage/method variances are accumulated and posted<br />

when you run one of the following.<br />

• Post Accumulated Usage Variances (18.22.9) creates GL entries for<br />

usage and method variances accumulated since the previous Post<br />

Accumulated Usage Variances report. The report gives you the option<br />

to update.

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

Saved successfully!

Ooh no, something went wrong!