Carsten Rohlehr

Create an option to define a max shipment size (lines) within the shipment consolidation policies.

By this new load lines shall only consolidate into an open shipment if the max. shipment size is not reached.

We are currently seeing situations where the shipments grow to a size they cannot be handled anymore.

And even the wave threshold isn't considered when consolidating.

Let’s explain the problem on an example:

Wave template with line threshold of 200 lines.

Before:

Open wave with two shipments:

• Shipment 1, 100 lines
• Shipment 2, 105 lines

Now 5 new sales order are released with each 50 lines and all of them are eligible to be consolidated into shipment 1, then the system will consolidate.

After

Open wave with two shipments:

• Shipment 1, 350 lines
• Shipment 2, 105 lines

Now we have two things which are not good for handling. One shipment with a size which is not good to be handled (350 lines).

And a wave where the wave threshold was exceeded by more than 100%.

If we could define a threshold for the shipment consolidation, of e.g., 100 lines, such a situation could be avoided.

In cycle count reporting it's necessary to distinguish between countings by source

Actualy that's not possible in an easy way:

• Work pools are available for counting plans, counting thresholds and manualy created counts but not for spot counting or count created via work exception.
• Work templates / Work classes can only be used for counting plans and here not for the one counting empty locations
• Counting reason codes are only set for discrepancies

The idea is to make work pools available for spot counts and counts created via work exception as well.

By this work pools could be used as unique identificator.

Side effect - it would increase flexibilty of the MDMI setup, with work pool as filter.

On cycle count thresholds there is the parameter “Process cycle counting immediately”. Activating this parameter cycle counting gets shown during the picking operation. But it's a none or all decision. If a counting work exists for the picking location, the system will ask to count, irrespective of the threshold. The idea is to restrict the execution of cycle count work during picking to those situations where the threshold is met.

Let me clarify by an example:

Cylce count threshold is active with threshold qty 5. And the checkbox “Process cycle counting immediately” is active.

Location 1 – On hand 8 – cycle count work already exists

Location 2 – On hand 8 – no open cycle count work

Location 3 – On hand 15 - cycle count work already exists

On each location we have to execute a pick of qty 5 :

The situation we see:

Location 1: (threshold is met 8-5 = 3)

• No cycle count work created as already existing
• Open cycle count work must be executed during picking

Location 2: (threshold is met 8-5 = 3)

• Cycle count work gets created as threshold is met
• Open cycle count work must be executed during picking

Location 3: (threshold is not met 15-5 = 10)

• No cycle count work created as threshold is not met
• Open cycle count work must be executed during picking -- This is the incorrect from our point of view --

In this example we would like to count only for location 1 & 2 during picking but not for location 3.

The benefits we see:

• less interuptions of picking operations by counting to be executed (only the counts we want them to count during picking)
• enabling a confirmation of empty locations during picking (threshold 0)

Current Process (5 Steps):

1. Tap "Change Shipment" button
2. View Details
3. Tap Edit
4. Enter or scan new shipment number
5. Confirm

Proposed Improvement (2 Steps):

1. Tap "Change Shipment" button
2. Enter or scan new shipment number

Benefits:

• Faster Workflow: Reduces steps by 60%, saving time per operation.
• Improved Usability: Simplifies the user experience, especially for high-volume environments.