-
-
Notifications
You must be signed in to change notification settings - Fork 209
[16.0][IMP] stock_storage_type: Allow to recompute putaways + several improvements #1040
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
base: 16.0
Are you sure you want to change the base?
[16.0][IMP] stock_storage_type: Allow to recompute putaways + several improvements #1040
Conversation
… location for a selected move line
… been populated
In the case of no product mixing, if a destination location has already been computed and
in the meantime, the location has been populated by another product, the computation
still propose the same location.
Exclude locations in that case.
…uantity
The current implementation was triggerring queries (read_group). Rely now
on ORM to get records as 'quant_ids' field exists on locations
|
Hi @jbaudoux, |
0e0aa56 to
0d1b526
Compare
… filled in If every possible destination location (e.g.: for pickable stock) is filled in with products, but with one outgoing move is in progress (picked but not yet validated), the location should become available to store incoming products. The putaway strategy should propose that location. So, add a condition to select 'empty' and 'being emptied' locations along with the 'location_will_contain_product/lot_ids' property to avoid too much restriction
jbaudoux
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG
|
FYI @sebalix |
|
/ocabot merge minor |
|
This PR looks fantastic, let's merge it! |
|
@jbaudoux your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-1040-by-jbaudoux-bump-minor. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
Supersedes : #938 (rebased on new code)
Includes several improvements: