In the documentation (which is suspect at times) it says a dynamic PCID “is one that you generate and disappears, or collapses, after its intended use.”
So how do you tell it to collapse or what its “intended use” is?
Is that when nothing remains in the PCID? simple as that?
I would have to check, but I believe it’s when the PCID status goes to empty. I don’t know if it really “Disappears” in the system. More like just stays at empty and doesn’t get used again. I think the dynamic has more to do with generating new numbers all of the time. So if you’re package is just a box, you give it a label with a unique PCID number. But if your PCID’s are reusable numbered pallets, you would use the number that’s on the pallet and not generate new numbers each time.
It’s all confusing and very poorly described. It’s a bit of trial and error.
Thanks Brandon, I will try it out and then mark as solution.
It does, and it’s dead. Get’s moved to the history table and cannot bring it back.
Not sure of the exact conditions for when it collapses, but I can find out.
We use it that way, but are looking at getting off of it so we can do returns / rma
back to the same pcid it left on.
I know we don’t need it after we empty it so this would be what we want.
If you could find out what condition makes it collapse that would be helpful. I am goign to test it myself.
My main question is though, can we control the event that makes it collapse? or is that even a thing? liek say you wanted one to collapse when it was transfered and received to another plant… or you wanted one to collapse after one inventory movement, etc…
Or is it a set event that makes it collapse?
I don’t remember all the rules, I’ll have to check my notes and talk to my associate.
Is that your friend in your head?
I can speak to SOPICK PCIDs.
We have ‘Archive PCID History’ turned off, and the life cycle of these PCIDs is
EMPTY → SOPICK → PACKED → SHIPPED
As soon as the shipment is invoiced, all PCID data goes poof.
Thank you Garret!