Your client has decided that Discrete Manufacturing will be implemented at a future stage, so any new supply from current manufacturing will be added to current inventory by the Open Transactions…

Question

Options

• AAll Transaction Types Related to Work in Process
• BAverage Cost Update
• CBackflush Subinventory Transfer
• DMiscellaneous Issues and Receipts
• EAll Internal Transactions

Explanation

A (All Transaction Types Related to Work in Process) and C (Backflush Subinventory Transfer) are the two transaction types that can be omitted.

Since Discrete Manufacturing and the Work in Process (WIP) module are deferred, any transaction type that exists solely to support shop floor and production activity is irrelevant at this stage. WIP transaction types (completions, component issues, scrap, etc.) only fire when the WIP module is active, and backflush subinventory transfer is a WIP-specific mechanism that automatically pulls components from a designated subinventory during production - both are dead code until manufacturing goes live.

Why the distractors are wrong:

• B (Average Cost Update) - Inventory costing is active from day one; average cost updates are needed to maintain accurate item costs as receipts and issues occur.
• D (Miscellaneous Issues and Receipts) - The Open Transactions Interface will use miscellaneous receipt transactions to bring manufacturing output into inventory, so these are required immediately.
• E (All Internal Transactions) - Subinventory transfers, inter-org transfers, and similar internal moves are core to Inventory and Order Management operations and cannot be omitted.

Memory tip: Think "WIP = Workshop In Progress." If the workshop (Discrete Manufacturing) is closed, anything labeled WIP or backflush belongs to that closed workshop and can be skipped - everything else keeps the warehouse and orders running.

No community discussion yet for this question.