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_mts_mto_rule] P.O not auto-generated for zero(0) stock products. #345

Closed
blutecsolutions opened this issue Oct 9, 2017 · 4 comments
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Milestone

Comments

@blutecsolutions
Copy link

blutecsolutions commented Oct 9, 2017

Hello,

Thanks alot for all efforts put in the modules

Concerning this module: https://www.odoo.com/apps/modules/10.0/stock_mts_mto_rule/
I've tried it on the OCA runbot:
When product has MTO + MTS route set + BUY route,

  • the Purchase Order is not auto-generated for products with zero(0) stock --
  • but products with stock more than 0 can be transferred successfully by Delivery Order.

What am i doing wrong.?

Thanks and your help is much appreciated.

@blutecsolutions
Copy link
Author

blutecsolutions commented Oct 9, 2017

EDIT: I'm not using the Manufacting.Order,

  • Delivery Order is created via the Sales.Order

@blutecsolutions
Copy link
Author

Ok i found out that the MTO + MTS Route is not configured by default after installing the module, i will record a short video tutorial and we can add it to the module description.
Thanks ,

@rousseldenis
Copy link
Sponsor Contributor

@Blu777 So, solved ?

@rousseldenis rousseldenis added this to the 10.0 milestone May 12, 2018
LRovira-PlanetaTIC pushed a commit to PlanetaTIC/stock-logistics-warehouse that referenced this issue May 15, 2020
…availability_button

[10.0][FIX] stock_disable_force_availability_button: Migration scripts
@github-actions
Copy link

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 Oct 31, 2021
@github-actions github-actions bot closed this as completed Dec 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

2 participants