WIP Tracking and Labeling Across Operations in IFS

This is great news, Björn.

We had been considering a configuration using Handling Units to support this requirement, as the customer wants to track each individual part—even though the parts are not serialized.

For example, if the lot size is 100 pieces, they want to ensure that all 100 pieces completed from the first operation are physically identified and remain available near the work center for the next operation. To support this, they are looking for a labeling approach such as:

<Order No> – <Completed Operation No> – <Sequence No>
e.g., 152435-10-01, 152435-10-02, …

The intention is to generate a unique barcode label for each WIP piece to enable clear identification and tracking on the shop floor.

With the introduction of WIP Products, do you think this type of piece-level barcode labeling can be achieved through standard configuration, or would it require customization?

Thanks again for sharing this update—it’s very helpful.

Packing of WIP products into handling units are not supported in 26R1. You can print labels for each piece, but it’s not possible to generate any unique identifier for each item, 

​@Vulcan Here is a high-level summary of a solution implemented in Apps10 at a customer without the labelling of each piece.

1. Created a zero-cost Inventory Part for the WIP part (e.g., [MAIN PART]-WIPCOMP).
2. Added this part as a component AND as a by-product in the Product Structure.
3. When the operation is reported, receive the by-product into stock.
   1. This was received into an inventory location (a cart with an ID tag on it) and then moved to the next machine. I proposed that this cart could be a Handling Unit as it would move to another machine but the customer wanted the 'mobile' inventory locations.
4. As the by-product part is also a shop order component, this by-product would then be consumed at the next operation.

Thank you Matt