Skip to content

Commit 5ec42ea

Browse files
authored
Update production-how-to-flush-components-according-to-operation-outp… (#1451)
* Update production-how-to-flush-components-according-to-operation-output.md 1. polishing scenario as Forward option doesn't respect actual output. 2. slightly polished table from https://docs.microsoft.com/en-us/previous-versions/dynamicsnav-2016/hh168039(v=nav.90), as it provides better explanation of options than example above.
1 parent d795623 commit 5ec42ea

File tree

1 file changed

+25
-12
lines changed

1 file changed

+25
-12
lines changed
Lines changed: 25 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: How to Flush Components According to Operation Output | Microsoft Docs
3-
description: For items that are set up with backward flushing method, the default behavior is to calculate and post component consumption when you change the status of a released production order to **Finished**. For more information, see Flushing Method.
2+
title: Flush Components According to Operation Output
3+
description: For items that are set up with backward flushing method, the default behavior is to calculate and post component consumption when you change the status of a released production order to **Finished**.
44
author: SorenGP
55

66
ms.service: dynamics365-business-central
@@ -14,35 +14,48 @@
1414

1515
---
1616
# Flush Components According to Operation Output
17-
For items that are set up with backward flushing method, the default behavior is to calculate and post component consumption when you change the status of a released production order to **Finished**.
17+
You can define different flushing strategies, to automate registering of consumption of components.
1818

19-
If you also define routing link codes, then calculation and posting occurs when each operation is finished, and the quantity that was actually consumed in the operation is posted. For more information, see [Create Routings](production-how-to-create-routings.md).
20-
21-
For example, if a production order to produce 800 meters requires 8 kg of a component, then when you post 200 meters as output, 2 kg are automatically posted as consumption.
19+
For example, if a production order to produce 800 meters requires 8 kg of a component, then when you post 200 meters as output, 2 kg are automatically posted as consumption.
2220

2321
This functionality is useful for the following reasons:
2422

2523
- **Inventory Valuation** - Value entries for output and consumption are created in parallel as the production order progresses. Without routing link codes, the inventory value will increase as output is posted and then decrease at a later point in time when the value of component consumption is posted together with the finished production order.
2624
- **Inventory Availability** - With gradual consumption posting, the availability of component items is more up-to-date, which is important to maintain the internal balance between demand and supply. Without routing link codes, other demands for the component may believe that it is available as long as it is pending a delayed consumption posting.
2725
- **Just-in-Time** – With the ability to customize products to customer requests, you can minimize waste by making sure that work and system changes only occur when it is necessary.
2826

29-
The following procedure shows how to combine backward flushing and routing link codes so that the quantity that is flushed for each operation is proportional to the actual output of the finished operation.
27+
You can achive that by combining backward flushing method and routing link codes so that the quantity that is flushed for each operation is proportional to the actual output of the finished operation. For items that are set up with backward flushing method, the default behavior is to calculate and post component consumption when you change the status of a released production order to **Finished**. If you also define routing link codes, then calculation and posting occurs when each operation is finished, and the quantity that was actually consumed in the operation is posted. For more information, see [Create Routings](production-how-to-create-routings.md).
28+
3029

3130
## To flush components according to operation output
3231
1. Choose the ![Lightbulb that opens the Tell Me feature](media/ui-search/search_small.png "Tell me what you want to do") icon, enter **Items**, and then choose the related link.
3332
2. Choose the **Edit** action.
34-
3. On the **Replenishment** FastTab, in the **Flushing Method** field, select **Forward**.
33+
3. On the **Replenishment** FastTab, in the **Flushing Method** field, select **Backward**.
3534

3635
> [!NOTE]
37-
> Select **Pick+ Forward** if the component is used in a location that is set up for directed put-away and pick.
36+
> Select **Pick + Backward** if the component is used in a location that is set up for directed put-away and pick.
3837
3938
4. Choose the ![Lightbulb that opens the Tell Me feature](media/ui-search/search_small.png "Tell me what you want to do") icon, enter **Routings**, and then choose the related link.
4039
5. Define routing link codes for every operation that consumes the component. For more information, see [Create Routings ](production-how-to-create-routings.md).
40+
> [!IMPORTANT]
41+
> Do not use same routing routing link for different operations in the routing, as it will lead to registration of consumption of component for each linked operation.
4142
6. Choose the ![Lightbulb that opens the Tell Me feature](media/ui-search/search_small.png "Tell me what you want to do") icon, enter **Production BOM**, and then choose the related link.
4243
7. Define routing link codes from each instance of the component to the operation where it is consumed.
4344

44-
> [!IMPORTANT]
45-
> The component must have a routing link to the last operation in the routing.
45+
The consumption will be posted automatically when you register output. For more information, see [Batch Post Output and Run Times](production-how-to-post-output-quantity.md)
46+
47+
## Additional information about Flushing Method
48+
Available flushing method options you can define in the **Item** card or **Stockkeeping Unit** card.
49+
50+
|Option|Description|
51+
|------------|-------------|
52+
|Manual|Requires that you manually enter and post consumption in the consumption journal.|
53+
|Forward|Automatically posts consumption according to the production order component lines. <br><br>By default, the posting of component consumption occurs when you change the status of a production order to **Released**. However, if you use the **Routing Link** Code field on production order component lines, then posting occurs per operation when the operation starts. For more information, see [How to: Create Routing Links](production-how-to-create-routings.md#to-create-routing-links). <br><br> [!NOTE]<br>For forward flushing, the operation-specific posting that you obtain with routing link codes is based on the expected quantity that is defined on the component line. For information about operation-specific flushing based on actual output, see the description of **Backward** in this topic.<br><br>If the location or resources where this component is consumed are set up with a default bin structure, then the item is consumed from the **Open Shop Floor Bin Code**. For more information, see [How to: Set Up Basic Warehouses with Operations Areas](warehouse-how-to-set-up-basic-warehouses-with-operations-areas.md). <br><br> [!IMPORTANT] <br>Forward flushing also occurs when you choose **Refresh** on a released production order that was created from scratch. On these directly created released production orders, you cannot change bin information because the production order component lines are generated when you refresh the order, which at the same time forward flushes the components. Therefore, if you want to change bin information on production order component lines before forward flushing occurs, then that order must be created with the *Planned* or *Firm Planned* status.|
54+
|Backward|Automatically calculates and posts consumption according to the production order component lines.<br><br> By default, the calculation and posting of component consumption occurs when you change the status of a released production order to **Finished**. However, if you use the **Routing Link Code** field on the production order component lines, then calculation and posting occurs when each operation is finished.<br><br> [!NOTE] <br>Backward flushing and routing link codes can be combined so that the quantity that is flushed per operation is proportional to the actual output of that operation. For more information, see [How to: Flush Components According to Operation Output](#to-flush-components-according-to-operation-output).<br><br> If the location or machine center where this component is consumed are set up with a default bin structure, then the item is consumed from the **Open Shop Floor Bin Code**.|
55+
|Pick + Forward|Same as for Forward flushing method, except it only works for locations that use directed put-away and pick.<br><br> Consumption is calculated and posted from the bin that is defined in the **To-Production Bin Code** field on the location or machine center after the component has been picked from the warehouse.<br><br> [!NOTE] <br>If a component is set up with the Pick + Forward flushing method, then it cannot have a routing link code to an operation that is set up with the forward flushing method. The component would then be automatically flushed when the operation starts, which makes it impossible to request the pick activity.|
56+
|Pick + Backward|Same as for Backward flushing method, except it only works for locations that use directed put-away and pick.<br><br> Consumption is calculated and posted from the bin that is defined in the **To-Production Bin Code** field on the location or machine center after the component has been picked from the warehouse.|
57+
58+
4659

4760
## See Also
4861
[Create Production BOMs](production-how-to-create-production-boms.md)
@@ -54,4 +67,4 @@ The following procedure shows how to combine backward flushing and routing link
5467
[Working with [!INCLUDE[prod_short](includes/prod_short.md)]](ui-work-product.md)
5568

5669

57-
[!INCLUDE[footer-include](includes/footer-banner.md)]
70+
[!INCLUDE[footer-include](includes/footer-banner.md)]

0 commit comments

Comments
 (0)