We are in the “design” stage of a new Epicor Kinetic implementation. We have AMM, and have been looking at WIP PCIDs. It’s appealing to us because our WIP travels around our shop floor in containers - rolling cages, sometimes pallets - but always in some sort of container.
I understand this is still a relatively new feature. Has anyone here gone whole-hog on using WIP PCIDs to track their WIP as it moves around the shop floor? Do you love it? Hate it? Any side benefits, fallout or downstream implications we should know about?
We are working with an Epicor implementation consultant and he’s awesome, but he hasn’t had many customers using WIP PCIDs yet. He suggested I throw it out here and see if I get any bites.
PCID’s for inventory are great, for WIP also, but only if you receive your Job to inventory at the end. Shipping PCID from WIP directly still seems to be impossible.
I’m relauching this conversation, we are on 2024.2 and want to use PCID for WIP flows in production.
Our objective is to : group multiple sub-assemblies (S-ASMs) and materials into a single PCID, in preparation for the first operation of a parent assembly.
Here’s the use case:
We generate a PCID via the MES (End Activity) when completing an S-ASM operation (e.g., from cutting or saw).
We want to add several S-ASMs and materials into the same PCID, so that this “WIP container” can be sent to the welding operation (Op 10 of the parent ASM).
Once welding is done, we plan to either empty and delete the PCID, or reuse it for another set of components.
These PCIDs are for internal WIP only — not received to inventory or shipped.
The issue:
When we generate the PCID from MES, it is created with status “WIP”
We’re able to add only one S-ASM to the PCID.
When trying to add another, we get the error:
“Status for staged PCID PLT1 is not valid, it must be one of the following values: EMPTY, WIPFG.”
According to the documentation, WIP is not a valid or documented status — only “EMPTY” and “WIPFG” are accepted for WIP operations.
We’re trying to understand:
Why is the PCID created with status “WIP” instead of “WIPFG” ?
Is this due to Package Code setup, MES behavior, or a missing configuration/BPM?
Has anyone experienced the same situation in a similar WIP scenario?
Any input or experience would be greatly appreciated!
