[WIP][15.0][MIG]stock_picking_consolidation_priority : Migration to V15 #591
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This module adds an option "Raise priority when partially available" on operation types. When the option is set on an operation type, the first time a packing operation is made partially available (goods have been moved for instance from a picking), all the other moves that will bring goods for the same packing transfer have their priority raised to "Very Urgent". If the moves that bring goods to the packing transfer involves a chain of several moves, all the moves of the chain have their priority raised.
In the following graph:
PICK/001 ━► PACK/001 ┓
┃
PICK/002 ┓ ┣━► OUT/001
┣━► PACK/002 ┛
INT/001 ━► PICK/003 ┛
If we have the consolidate flag on "PACK", we want to raise the priority
only when we start to move goods in PACK/001 or PACK/002 (not INT/001),
because this is in the packing zone that we are limited in space.
Also, when for instance a move of PICK/002 or PICK/003 is set to done,
*any* move (all products) that go to PACK/002 are concerned by the
priority raise: we want to finish the transfer.
Adapt to new priority values (introduced in v14 odoo/odoo@e40553723b893bcd ) Add consolidate_priority setting in the view
Currently translated at 100.0% (7 of 7 strings) Translation: wms-14.0/wms-14.0-stock_picking_consolidation_priority Translate-URL: https://translation.odoo-community.org/projects/wms-14-0/wms-14-0-stock_picking_consolidation_priority/es_AR/
Following this v14 core change: * odoo/odoo@e405537 The priority field on stock.move is now a computed and it is the one on the picking that is stored to the db.
|
/ocabot migration stock_picking_consolidation_priority |
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.