-
-
Notifications
You must be signed in to change notification settings - Fork 719
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
[13.0] Add stock_checkout_sync #907
Conversation
d843351
to
3b07412
Compare
For now stock_checkout_sync is: OCA/stock-logistics-warehouse#907
3b07412
to
139aab5
Compare
For now stock_checkout_sync is: OCA/stock-logistics-warehouse#907
For now stock_checkout_sync is: OCA/stock-logistics-warehouse#907
139aab5
to
739d870
Compare
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.
Looks good overall, just some functions names to fix and questions.
314f5fb
to
3a44c64
Compare
4a193f1
to
04ccb9e
Compare
The test which fails in |
For now stock_checkout_sync is: OCA/stock-logistics-warehouse#907
82364e7
to
fbbec98
Compare
I fixed the error with
This one happens because
is not computed. It fails after: odoo/odoo@3a6ac95 |
Add an assistant to select the same destination location for all the moves that will reach the same transfer. Generally used on packing locations.
Co-authored-by: Akim Juillerat <[email protected]>
m is supposed to be part of moves_to_update.move_dest_ids, and moves_to_update is already a subset of self so it's always True
The test creates 2 product.product on the same product.template, which is illegal if they don't have different attribute values. No error is raised, unless another modules runs a "flush", which does the INSERT in database and fails with: psycopg2.IntegrityError: duplicate key value violates unique constraint "product_product_combination_unique" DETAIL: Key (product_tmpl_id, combination_indices)=(31, ) already exists.
c5aa718
to
d4d8ed7
Compare
Tests are now successful after rebase (fixed by #1035). |
This PR has the |
Note: do not merge, will be moved to OCA/wms as asked by @jgrandguillaume |
@guewen shall we close this in favor of OCA/wms#115 ? |
Replaces #862
Regroup moves at the same location when they reach an operation type.
Example of use case:
Based on these assumptions, we have these pickings, all for the same order:
The operator uses the button "Checkout Sync" on a pick transfer,
for instance SHELF001, and select Packing/PACK2 as destination.
We want all the lines that reach PACK001 to be updated with:
Packing/PACK2
we constrain the user to move the goods there as we want to move
all the goods at the same place for the packing.
Works best when used with
stock_available_to_promise_release
:creates the whole chain of moves) only when we know that we have the
quantities in stock (otherwise the module splits the delivery). Any exception
(which is now rare when you release this ways) that would lead to a backorder
is handled by canceling the remaining line.
changed at the same time
Compatible with
stock_dynamic_routing
.