Execution & Control Flushing Methods (2026)
Flushing methods in Business Central production orders: forward, backward and manual flushing, the pick plus warehouse step, component-level flushing policies and routing link codes. Includes a demo of posting manual components and finishing an order.
- Introduction to flushing methods
- What is flushing - definition and scope
- Three flushing methods and pick plus
- Routing link codes and component timing
- Reading the production order page
- Practical benefits of flexible flushing
- Demo - posting manual components and finishing the order
Overview
The video defines a flushing method as the rule for when the system posts production consumption automatically. It covers three methods (forward, backward, manual) and pick plus, which adds a warehouse picking step before the chosen rule applies.
It then shows that each component line on a production order can carry its own posting rule, and how routing link codes tie component consumption to a specific routing operation. It closes with a demo of posting manual components and finishing the order, using the production order page and the production journal.
Key points
- Forward flushing consumes components automatically once the production order is released. It suits predictable components that need no manual journal entry.
- Backward flushing posts consumption later, when output is recorded or the order is finished, so it waits for proof that work happened.
- Manual flushing has the operator review the component line and post actual consumption in the journal. It fits variable quantities or tighter control.
- Pick plus adds a warehouse picking step before the selected flushing rule applies. It does not replace forward, manual or backward flushing.
- Each component line on a production order can have its own flushing method, so forward, backward, manual and pick plus can be mixed on one order.
- A routing link code on a component ties its consumption to a specific routing operation when the codes match. A blank code applies timing to the order more generally.
- In the demo, releasing the order consumed the forward-flushed components and the control panel display, which is linked by routing link code 100 to body assembly. Backward and manual components still had quantity remaining. After a manual quantity change, the actual cost came out slightly above the expected cost.
Features
| Feature | Status | At |
|---|---|---|
| Forward flushing | status not stated, demoed | 0:55 |
| Backward flushing | status not stated, demoed | 1:13 |
| Manual flushing | status not stated, demoed | 1:26 |
| Pick plus | status not stated | 1:26 |
| Routing link codes on components | status not stated, demoed | 1:54 |
| Component-level flushing policies | status not stated, demoed | 0:44 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- other “production journal” at 0:10
- other “production order” at 0:21
- other “production order routing” at 2:05
Quotes
- 0:21 “A flushing method defines when the system posts production activity automatically.”
- 0:44 “On a production order, each component line can carry its own posting rule.”
- 1:42 “It only adds picking before that selected rule applies. That is the main point.”
- 2:05 “That matching code is what ties component consumption to a specific operation instead of treating the whole order as one timing event.”
- 2:45 “If a routing link code is filled in, the component is tied to that matching routing operation.”
- 2:58 “Components with forward flushing already consumed the expected quantity. Backwards and manual flushing methods still have the required amount as remaining quantity.”
- 3:25 “Predictable components can be automated. Components that need warehouse handling can stay pick controlled.”
