summaryrefslogtreecommitdiff
path: root/addons/base_import_module/tests/test_module
diff options
context:
space:
mode:
authorArnold Moyaux <arm@odoo.com>2021-03-03 13:29:33 +0000
committerArnold Moyaux <arm@odoo.com>2021-04-20 07:58:50 +0000
commitf939c7b2c4143d685c25d155a164d63070d36ed2 (patch)
treee2101657e1c0f03e2cefed89b9a417836a0ffd35 /addons/base_import_module/tests/test_module
parent4cad0ab17ae1917b7acc71cfb0fe2255845cdc94 (diff)
[FIX] stock: replenishment flow
Usecase to reproduce: - create a product with 0 stock - Sale order 500 units - a RFQ is created for 500 units - in replenishments, you have 0 units to order, OK - RFQ --> confirm PO - in replenishments, now the quantity to order is 500 --> should still be 0, it leads to confusions It happens because the replenish action check the missing quantity for today. It result by -500 units since the delivery is planned for the next day (default supplier lead days = 1). But since the orderpoint exist, the quantity forecasted is already computed correctly with the right lead time. But the action will remove the 500 missing today from the quantity forecasted (The idea is to add the missing quantity on the main location. e.g. I have -10 units in WH/Stock/Shelf1 -20 units in WH/Stock The orderpoint will only look for its own location -> 20 to reorder The replenishment report look by warehouse and not by location -> 30 missing. So 30 missing + 20 incomming -> 10 to add (by default on WH/Stock) The fix is to add a step when a product is missing then compute its virtual available with lead days (to avoid missing confirmed moves during the lead time). opw-2456978 closes odoo/odoo#67278 Signed-off-by: Arnold Moyaux <amoyaux@users.noreply.github.com>
Diffstat (limited to 'addons/base_import_module/tests/test_module')
0 files changed, 0 insertions, 0 deletions