-
-
Notifications
You must be signed in to change notification settings - Fork 723
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
[RFC][WMS] Split warehouse operations in relevant picking type #640
Comments
A second round to implement a new module "stock_full_operations_info". Context As we split operations in picking type per zones, the operator loose the sight of whether is doing a full order or only a portion of it. For this reason we need to give him back this information. This will allow him to take decisions on how to proceed the best according to the situation (e.g. if he is the only picker of an order, he might follow a shortened process). Two infos are required:
Use caes You have 3 orders:
The operator processing the picking by zone will have to know :
|
Hi @jgrandguillaume I will work on this requirement for version 12.0 On our project we have several zones on warehouse, mainly we have Stock Zone and Picking Zone. We create as two warehouses, and Stock Warehouse will supply Picking Wharehouse. We create reordering rules to:
The problem is that the route that create a picking from stock zone to picking zone will create a big picking with all products. We need to generate several pickings, split by hall or area in stock or picking zone. On other process we need to do pickings product by product... but it's other requiremente... I will start to play with rules and routes. |
Close as final version is there: #788 |
Source : https://docs.google.com/document/d/1mct6bFFWJqW01wGFcjc-uQNEjyCxvh6Y9TuFdRhe-b0/edit#
Part of: OCA/wms#1
This RCF to propose a POC implementation for the following
Example: Split operation by zones
→ basically, after the action_assign, if you're sourcing from a zone location, you call again _assign_picking to redistribute moves among the proper picking type picking (according to default src location of the picking type)
→if one move is classified in another picking_type picking after action_assign AND the default dest location of the new picking.type picking is different from the move:
→ you create a new move (src = default dest of the picking.type of the picking; dest = original dest of the move)
→ The new move origin and destination moves link are updated, and action_assign is recall on it in order to classify it in the proper picking.type picking
The text was updated successfully, but these errors were encountered: