We recently change our part #'s to new part numbers. I inactivated all of the old part numbers. However, some of those old part numbers were used to issue material in jobs that were not completed by the time new part #'s went into effect.
My problem is now whenever we try and make a scheduling change to a job that have a fully issued old part number we are met with an error that the old part # is inactive.
Is there a way around this? System won’t allow a part # change to the issued line (in E10 it does, but I can’t figure out a way in Kinetic).
Thoughts on how to resolve this w/o reactiving those old part numbers? If I’m forced to do this - I’m worried users will start using the old part #'s again.
How many jobs are in this state (not complete with old part numbers)?
If there’s not that many, I would handle manually by reactivating the part numbers temporarily to perform the scheduling change.
If there’s a lot, it may require a more elaborate BPM to prevent users from using the old part numbers while they remain active. In this case, is there anything unique about the old vs new part numbers we could use in a BPM?
Probably 20 at this point. But some jobs may be around for some time. Meaning this could go on for months.
There really isn’t anything unique about the old vs new PN’s that I could think of. What type of uniqueness would you be thinking of? Old part numbers have no structure and new PN’s do have a structure. But that new “structure” varies by part type, unfortunately.
For example if your new part numbers only follow the format “####-##-###” you could use a Regex expression to detect if the provided part number is in this format. Anything outside of this format would throw an error and prevent the user from using it.