-
-
Notifications
You must be signed in to change notification settings - Fork 206
Open
Labels
enhancementNew feature or requestNew feature or requestno staleUse this label to prevent the automated stale action from closing this PR/Issue.Use this label to prevent the automated stale action from closing this PR/Issue.
Description
cluster picking execution - lines sorting
Have an option “Sort method for processing move lines”
Have implementations:
- by priority & location
- this is the current implementation and should be the default
- help: each line is sorted by priority and then by location to perform a smart path in the warehouse
- by location grouped by product
- help: in case of multiple move lines for the same product, break the sorting to finalize a started product by processing all other move lines for that product in order to group a product on a picking device. When stacking products on a pallet, this prevents to spread a same product at different level on the stack.
- by custom
- to allow for example to sort by SO lines sequence
cluster picking execution - destination package
Have an option “Destination package selection”
Have implementations:
- by transfer
- this is the current implementation and should be the default
- help: Group products on the picking device by transfer. Allow to freely choose a destination package for the first transfer move line. Then for each next line, that package will be suggested. You can choose a new empty one but you cannot select a package used for another picking.
- by partner
- replaces module alc_shopfloor_cluster_picking_by_partners
- help: Group products on the picking device by partner. Allow to freely use a destination package for the first partner move line. Then for each next line, that package will be suggested. You can choose a new empty one but you cannot select a package used for another partner
- by single kit or line
- help: Group products on the picking device by single kit. Each compartment of the picking device will contain all components of a single kit. If the move line doesn’t relate to a kit, then it will contain a unique move line. Allow to freely choose a destination package for the first move line. Then for each next component of the kit, that package will be forced
- here we need to split line by single kit. If you sell 3 kits and in each kit there are 2 times the first component, then we need 3 move lines with qty 2. The first line, it needs to go in PACK1 and the second line in PACK2. The next components of the kit must respect those destinations. I think, the easier is to split all move lines to have a single kit and to record the destination pack on each of those move lines.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestno staleUse this label to prevent the automated stale action from closing this PR/Issue.Use this label to prevent the automated stale action from closing this PR/Issue.