Drag and Drop Question You are the production supervisor at a manufacturing company. You are in the process of configuring the production control module and its parameters. A company plans to use…

Question

Exhibit

Answer Area

Explanation

Explanation: Automatic BOM Consumption for Operation-Level Backflushing

Context

In Microsoft Dynamics 365 Supply Chain Management, the Manufacturing Execution (MES) production order defaults form has an Automatic BOM consumption setting that controls when BOM materials are consumed during production. The options are:

The Two Targets and Why Both = never

The drag-and-drop targets represent the two automatic consumption trigger points on the form - typically job start and report as finished (or equivalent operation-level events). Both are set to never for the following reasons:

Target 1 → never BOM consumption should not fire automatically when a production job starts. Setting this to always or flushing principle would consume materials the moment a worker clocks onto a job - before the operation is actually complete. This contradicts the backflushing-on-operation requirement.

Target 2 → never BOM consumption should also not fire automatically via the system's default finish/report event. Instead, consumption must be triggered explicitly when the operator reports progress at the operation level through the job card terminal. Setting this to anything other than never would cause double-consumption or premature consumption.

Key principle: Setting both to never hands control of BOM consumption over entirely to the operation reporting step, which is exactly what backflushing at the operation level means - materials are consumed backward from the completion event reported by the operator.

Common Mistakes / Misconceptions

• Using flushing principle seems logical (let the item decide), but the flushing principle on BOM lines is evaluated at job start/finish events - it does not guarantee operation-level consumption. It could fire at the wrong time.
• Using always would cause BOM items to be consumed at every automatic event, not just at operation reporting - leading to over-consumption or timing mismatches.
• Students often confuse where backflushing is triggered (operation report) with what controls it (the MES defaults form). The never setting doesn't mean "never consume" - it means "don't consume automatically here; let the operation report handle it."

No community discussion yet for this question.