@TimK
We are a smaller dealer and I've seen a few hiccups with the Delay PNC feature, but through experience I've discovered most of the pros and cons.
I've set up my sources on CDK/ADP to utilize the Delay PNC feature. When we run the monthly Parts Master Update (PMU), I immediately run Report Part Changes (RPC), and it will show me all the numbers ON FILE that have superseded to new numbers, along with which ones have Delay PNCs. Parts with zero OH will automatically supersede to new number. Usually there aren't too many parts with OH that have Delay PNCs. Then I can check the ones that are OH to see which method, RIM or not, they were last ordered under. If the part was Special Ordered, then I know it will need to go on a monthly return within the next 12 months UNDER THE OLD NUMBER. Usually when this occurs during the PMU, if the source for that particular part is set to update to the default GM Sources within CDK, the old numbers will update to Source 100. This also makes it easy to run an RPG Report of parts with Source 100 with an OH to monitor which parts may need returned on NON-RIM Returns.
RIM's treatment of these situations can be tricky also. One of the necessary steps to avoid problems when you have an OH of the Old Number, and the Delay PNC takes affect, the new number is often
Not Found in Inventory, i.e. not RIM managed, and it's best to
insert the new number
to be managed by RIM and it will tie the Old Number to the New Number.
There have been a few miscues here and there, but you will not find but a few parts in my inventory that have
white tags with new numbers written on them. And the ones that do, have labels indicating when the last RIM Order put the part in our inventory, with a note to contact RIM when it reaches 15 months from the Last Sale Date.
All this hoopla for the cases when old numbers cost more than the new number, and I want to get full reimbursement for the parts that don't sell. Not to mention eliminating return rejections.
