Hi @Markus.Blomsterlandet
With the given data setup we are not in a position to demonstrate the existing functionality to satisfy your requirement. But, my opinion is that there are high chances you can satisfy your requirement with the existing functionality.
I will add how transport task consolidation works for your reference:
********
The automatic consolidation that take place every time a Transport Task line is created. Meaning that newly created Transport Task lines should be added to existing Transport Task if possible. Otherwise there will a new transport task created. Currently there do exist some firm rules for consolidation:
· “Single” lines with the same part no (including configuration), order reference and from and to location are added to already existing Transport Task headers in status created.
It should be possible to configure the rules that should be applied for consolidation of newly created Transport Task lines. And that it should be possible to have different set of rules per site.
It should be possible to define which criteria that should be considered when performing consolidation of newly added transport task lines. The implemented criterias to consider are:
The different options available are:
· Part by:
Single Configuration/Single Part/Multiple Parts
· Source By:
Single Reference/Single Ref1/Multiple References
· From Location by:
Site/Warehouse/Bay/Row/Tier/Bin
· To Location by:
Site/Warehouse/Bay/Row/Tier/Bin
(Optional criteria that might be included for consolidation:
Ownership/Owner/Project ID, activity, sequence/Lot batch no/Max number of lines
When new Transport Task lines are created we will use the criteria specified above to find similar Transport Task that are in status Created where the new lines could be added. In addition to those criteria the Transport Task lines considered for consolidation should also have:
· From and to site must be the same as on the Transport Task where they should be added.
· Location group for new lines must be the same (for From location) on the Transport Task where they should be added.
· New lines can only be added to Transport Task that are not set as Fixed
· Note that Destination will also always be a source for consolidation – separate destinations (Transit or Inventory) will be on separate transport tasks.
*****
Regards,
Piyal
We also have the same scenario which is raised in the question.
@Piyal Perera as I understood by the system behaviour and also by your explanation, the current consolidation impacts when a new TT line should be added to any existing TT header or not. This is working perfectly.
However, our requirement is an ability to consolidate/group lines in a given Transport Task. The need for this is dire for the warehouse workers in picking. (warehouse tasks solution is not used) Since the part no cannot be aggregated in the transport task, the transport task report has its part lines scattered, so the inconvenience for the picker. Even the aggregation tab only aggregates based on either per handling unit or per location. So @Markus.Blomsterlandet it seems you will need to pick multiple times.
Hi @Vimukthi Mahakumbura,
Yes. I can understand. After transport tasks consolidations, it is better if we can think the best way to pick.
regards,
Piyal
We have this scenario too. We have reserved the same part for multiple different shop orders. The created transport task has 5 lines, all for the same part located in the same location that will be moved to the same location for further consolidation. Currently WADACO would treat them as separate lines, so the user would have to pick line 1, pick line 2, pick line 3, pick line 4, pick line 5, in order to get the same parts and move them from one location to another without losing the reservation information. To make the warehouse workers efficient, we would like to pick all 5 lines worth of qty as one pick. Is there any way to make this work, and it really doesn’t have to do with the Transport Task Consolidation Rules, more the rules for the data feeding into Wadaco process.
