IFS Slow Shipping Processes

​@cweidner have you tried setting up the Shipment Type so that it automates some of the steps inside the shipment?

For example you could automate that the reservation + picklist creation + picklist printuing is done automatically. Then once you reported picking, complete + deliver + even invoice creation can be done automatically.

Then one other thing that could be useful would be the Pick By Choice - enabled at site level. This will give more flexibility with the ‘gathering’/reporting picking.

Thanks Marcel for the response, 

I’ll add some details here for Craig….. 
Yes, we are aware of the Shipment Type automation options. 

Concerns are not greatly related to Reserving and Creating the pick list. 

Slow downs are in the use of the Wadaco Config for Picking. 

We are Pick By Choice Allowed, shipping with Handling Units. 
Core Capture Process ID - REPORT_PICKING_HU --- didn’t play nicely for us in a Pick by Choice Allowed Site, so we are using the REPORT_PICKING_PART as the Capture Process for our scan configuration. 

Current Scanning Order is:
Pick List (Holds Memory, enter through)
Shipment Handling Unit (Holds Memory, enter through)
Part No
Handling Unit ID
Lot/Batch No
Qty Picked

We’d like to reduce scans to: 
Pick List (Holds Memory, enter through)
Shipment Handling Unit (Holds Memory, enter through)
Handling Unit ID

We had over 600 ‘child’ or box handling units on a recent shipment and you can imagine the extended time it would take to scan 4 to 6 fields per box. Does the idea or request seem too difficult to configure in IFS?

It’s a bit tricky to suggest improvements through this medium to broad questions.  While the community is an excellent resource for many, many topics, it’s challenging because there’s likely a lot of nuances and unique aspects of your business that would need to be carefully considered before making changes to increase your shipping efficiency.  

If you haven’t yet, I’d recommend reaching out to IFS support to request a consultancy service or reach directly out to an IFS Partner who may be able to assist.  

Hi ​@TBugner , 

Is it a performance issue that you experience when using the REPORT_PICKING_HU process. With the mentioned details, it is hard to understand why you can’t use the REPORT_PICKING_HU process. Can you provide more information.

BR

Choolangee

Hello ​@Choolangee ,

No, not really a performance issue in the sense of speed of interaction with IFS. But it is a concern on the quantity of fields required for scanning each box. The fewer the required entries by the user, the more efficient the process will be. 

Sounds to me like this is more of not knowing how to configure your process.

“We’d like to reduce scans to: 
Pick List (Holds Memory, enter through)
Shipment Handling Unit (Holds Memory, enter through)
Handling Unit ID”

The template configuration is almost like this already, only thing is that it will re-ask Shipment Handling Unit every time, was that your issue with this process perhaps?

You could do this in the REPORT_PICKING_HU by copying the template and do some slight changes, like make the process/configuration loop on itself and then change “Use subsequent value” functionality set to Fixed or Default on Shipment Handling Unit item and set Subsequent Data Item ID to SHP_HANDLING_UNIT_ID, it will then pass the value between the sessions/loop laps. The only problem is if you suddenly want to change shipment handling unit, the system have no knowledge on when you want to change value, so if you set the use subsequent value to Default you will have the chance to change the value or you just press save to continue if don’t want to change it.