Discrete picking

Discrete picking

lamygdalou
Observer Observer
110 Views
3 Replies
Message 1 of 4

Discrete picking

lamygdalou
Observer
Observer

Hello forum members,
I'm working with version 21.1.4, and I'm encountering an issue. I want the operators to begin discrete picking using the orders listed in the picking list, which I have configured in the global table. However, the process doesn't progress beyond the "Pull from list" step. As a result, the subflow doesn't start, and the picking process can't begin.
Has anyone faced a similar issue or does anyone know what might be causing this?

0 Likes
111 Views
3 Replies
Replies (3)
Message 2 of 4

xavier_low
Contributor
Contributor

In your source, the Quantity value references the table name "Picking_List" and not "Picking_list", so no token is created when you run your model.

xavier_low_1-1748919578257.png

 

0 Likes
Message 3 of 4

lamygdalou
Observer
Observer

thanks for the reply, I made the change but it still doesn't work. If you have any other suggestion i would appreciate your help

0 Likes
Message 4 of 4

moehlmann_fe
Enthusiast
Enthusiast

All of the lists are empty. Based on how the picking flow is structured, it seems that the "Picks" list should contain tokens that hold the information from the picking table as labels and  the created pallets should be pushed to the "Inventories" list.

You also use the "Label Access On Parent Only" option in both Run Sub Flow activities. But you reuse the "pulled" label when pulling a pallet to pick from. Each pull would overwrite the parent token's "pulled" label, meaning only the latest pull would be available on the token. Either don't allow "write" access on the parent labels or use different labelnames to store the pulled references.

And in the section that has the operator load the item, you use a label "item" which was not previously declared. 

0 Likes