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 - How to use with products that have a Bom type =set #218

Closed
sdalexander opened this issue Nov 7, 2016 · 5 comments
Closed
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@sdalexander
Copy link

Hi Guys
I have installed this module and it works well for most product set up's , however I am trying now to get it working with products that have a BOM with type = set .
ie. product A has a Set BOM to pull qty 2 of product B,which has a Normal BOM . Stock can be held against product B, No stock is held against Product A.
so If I have an sale order for 10 of product A, with 5 in stock of product B.
I expect an MO for 15 of product B to get the 20 needed to satisfy the sale order
I have tried a number of combinations of route setting against the products.
but I always end up with MO for the Full order qty of 20 as if it is using MTO linked back to the sale order.

will this module work with Bom type set?

Any ideas of a route/procurement rules that will achieve this?

thanks in advance

Steve

@florian-dacosta
Copy link
Contributor

Hello,
I am not sure, I think it your case can't work for one step delivery, but it may work for a 2 step delivery...
Anyway, it would probably be a good improvement to make for the module

@alyngsoe
Copy link

Hi sdalexander
Did you find a solution for your issues with MTS module for BOM products ? We have the same issue/needs.

yk2kus pushed a commit to thinkopensolutions/oca-stock-logistics-warehouse that referenced this issue Mar 16, 2017
…stics-workflow

[8.0] Manage lot directly on stock logistics workflow details
@rousseldenis
Copy link
Contributor

@sdalexander @alyngsoe Fixed ?

@alyngsoe
Copy link

@rousseldenis No, this was an issue for a version8. The customer ended up with creating re-ordering rules instead to push MO's. So we did not try the fix.

@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 24, 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

4 participants