Executing Repetitive Transactions
As work is performed, labor and movement of WIP units are reported. You can report these activities using various types of transactions, including downtime, scrap, rework, move, and rejects. There are nine transaction types and several purchase order functions for subcontract activities.
Repetitive transactions affect other areas of the system. As quantities are moved through repetitive operations, inventory transactions are recorded and posted as backflushing occurs. Labor and burden costs are recorded by manual entry or as a result of backflushing.
Transactions generate cost variances and create GL entries. Most transactions generate quantity and cost posting to the cumulative order and associated operation and bill of material (BOM) records.
Transactions affect any one of the three quantity queues associated with routing operations:
• The input queue, which holds quantities from the previous operation
• The output queue, which holds quantities from the current operation that have not been moved to the next operation
• The reject queue, which holds quantities rejected by the current or a subsequent operation