Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stock : MTO sale order for products with reordering rule #462

Closed
rousseldenis opened this issue Jul 31, 2018 · 1 comment
Closed

Stock : MTO sale order for products with reordering rule #462

rousseldenis opened this issue Jul 31, 2018 · 1 comment
Labels
question stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@rousseldenis
Copy link
Sponsor Contributor

Hi all,

I have a use case which can be discussed (or have been already):

  • a product X stockable, with a reordering rule min 5, max 10

  • Make To Order + Buy is defined on it and the MTO route is available on sale order lines

  • its stock qty : 6

  • I sell 3 qty with MTO but I don't confirm the Purchase Order.

  • The scheduler runs

  • The system considers that we are under the min stock qty as the virtual stock is = 3 (6-3) and generates the remaining qty to get the max (10) => 7.

So, we get an order to refill stock but if we consider MTO orders won't change the stock level, can this could lead to unwanted behaviour ?

Has someone already implemented a solution to avoid this ?

The lead I see is to not taking into account MTO outgoing moves that have no ingoing ones (or corresponding draft Purchase Orders) in the virtual available as the line who triggers a new procurement is : https://github.com/odoo/odoo/blob/e11908d429435091828f224ee0751b90de8c99aa/addons/stock/models/procurement.py#L346

@OCA/logistics-maintainers

LRovira-PlanetaTIC pushed a commit to PlanetaTIC/stock-logistics-warehouse that referenced this issue May 15, 2020
…_date-dro

[10.0][ADD] stock_change_price_at_date
@github-actions
Copy link

github-actions bot commented Nov 7, 2021

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Nov 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant