Skip to Content
Dette spørgsmål er blevet anmeldt
bugPOv14replenishment
2 Besvarelser
5088 Visninger
Avatar
Apiuser

Hello,


Problem:

We have set the replenishment rules to 0 min / 0 max / 1 multiple (which would be replenish on demand) and still SOME of our automatic POs are generated with more units than we need.


Has anyone expiriencied this as well?


Example: 

We have a product B that needs 5 product C, and another product D that needs 2 product C. When we order to manufacture product A which is made of 1 B and 1 D a PO is generated asking for 9 B instead of 7 B.


Our build:

We are running ODOO14 com. ed. with Manufacturing, Inventory, Purchase, Sales, Invoicing and Contacts modules. We do have some customs and have checked if this is the cause of the problem, but if it is we were not able to find how.

Avatar
Kassér
Avatar
Apiuser
Forfatter Bedste svar

The answer was to use MTO, as if we do not want min stock and we replenish as much as we consume it makes no sense to use replenishment rules.

Avatar
Kassér
Avatar
Business Cycle Consulting - PT. Manggala Jaya Solusitama, bunhin
Bedste svar

This is "bug" or "feature?" in odoo 14, i believe. May end up rule is not trigerring procurement or triger procurement more than is needed. in Odoo 14  lead times is become a variable in the replenisgment logic. But Odoo is lack of documentation about this changes and i think need a brief guide on the variable lead time used..

For example if your lead time to purchase is say 14 days,  and we have generated PO for arrival in 20 days to replenish the forecast negatif qty,  Odoo 14 dont consider that PO. So it will recreate other RFQ.

In other side, if there is needs to deliver in 30 days time,  Odoo 14 will not trigger any procurement yet.

Or try to update odoo code, may some improvement or fix apply

Avatar
Kassér
Relaterede indlæg Besvarelser Visninger Aktivitet
Adding a column in Replenishment
Studio v14 replenishment
Avatar
2
nov. 23
3584
Possible Bug with Google Maps extension on v14 Løst
bug v14 googlemaps
Avatar
Avatar
Avatar
Avatar
4
maj 22
7353
Archiving an opportunity mark it as "Lost" which is not correct.
bug Studio v14
Avatar
Avatar
1
mar. 22
4817
v14 bug regarding drag & drop WOs between work centers Løst
bug Manufacturing v14
Avatar
Avatar
1
dec. 20
4673
Strange error while computing fields with odoo Studio: Module <module 'time' (built-in)> can not be used in evaluation contexts
bug computed-fields v14
Avatar
Avatar
4
okt. 20
11652