PO13 Cleanup

It's not a bug - it's a "feature" that got put in sometime around Contract Management came in. The only thing we've been able to do is inactivate them on PO13.3. I'd love to hear if anyone's been able to get rid of them.

Lovely "feature" Are you hearing of any RQC Search Catalog issues as a result of the inactive PO13? I have an incident open with Infor on this but they seem stumped. If a user searches for an item with both an active & inactive PO13 their search isn't found, as though the inactive PO13 is "in the way".

No ... but my "squeaky wheel" users all use the Special/Service to search, so they may just not have realized it yet.

I've not seen this either. We recently switched much of our Biomet PO13 records to Zimmer and inactivated the Biomet records. When I search for those items in RQC I see only the Zimmer records. What I'd really like to see is when you drill around on an item and open the PO Vendor Items folder that the drill shows whether a vendor item is active/inactive right in the list instead of having to click on each one to see it in the details. I should check if there's an enhancement request for this.

Hi, I have do delete the Inactive items from PO13. So can anyone tell me what steps to follow?

Anu:
Still no word on this "feature" being amended or any word of a workaround that I can see. It's the bane of my existence after inheriting a rather sloppy maintenance routine my predecessors established. No replacements on the PO13 screens, just line after line of either new pack gens, or just erroneous entries. The latter being the majority. Multiple active records as well on the same item which, for us, causes issues when transmitting implant/supply info to EPIC.

Hi Ardy!

We had some problems with PO13.3 having too many options. It's a major pain. There are two types.  One where it knows the correct item is marked as default, but not that it replaced the old one and didn't update PO25.6.  And the second one where it just flat out refuses to pick.

For PO13s where the correct value isn't the one on PO25.5

Step 1: Mark the old item as Active if it's not. Then mark as default.
 You should now have PO13 and PO25.6 agreeing with each other again.
 Step 2: Inactivate and Delete correct item.
 Step 3: Now use R to replace old item with correct item.

 If it doesn't let you delete the correct item, it's even more fun.

 Step 1: Remains the same. Mark the old item as Active if it's not. Then mark as default.
 You should now have PO13 and PO25.6 agreeing with each other again.
 Step 2: Keep the correct item active.
 Step 3: Now use R to replace CORRECT item with something else. We literally type WRONGITEM as the part number to avoid any possibility of future confusion.
 You should now have OLD item as the default tied to PO25.6, CORRECT item as inactive and WRONGITEM as active but not default.
 Step 4: You should now be able to delete CORRECT item.
 Step 5: Replace OLD item with CORRECT item using FC R.
 PO13 and PO25.6 should now match with the CORRECT item
 Step 6: You should be able to inactivate/delete OLD and WRONGITEM - but if not, you can at least inactivate them.

 GOOD LUCK.

In order to delete PO13 records, we had to close all of the inactive Vendor Agreements instead of them having the status of ON HOLD. When you have an inactive PO13, Contract Management will error and not allow you to enter a special on the agreement being there is Lawson data affiliated with it. Basically, CM compares the vendor items to all PO13 records, both active and inactive. Only way around that is to delete PO13 records, which as said above, can only be done if it is not attached to an existing Vendor Agreement, regardless if it is on hold or not. Inactive PO13's on Inactive VA's stop you from taking full advantage of Contract Management. Instead of putting the old agreements on hold, we chose to put them in the CLOSED status, which then allows you to delete the PO13 tied to it. Be sure to look for any reports you have built looking at agreements on hold, because they will no longer be in that status and the CLOSED VA's will start showing unless you build new logic into the report.

Hi GW - thanks so much for the information. We currently set our PO25's to purge by changing the start date to 1/1/1994 & putting them on hold. Then we have a recurring PO300 run monthly looking for 1/1/1994 & purging when it can. Some agreements have been out there for years & probably will never purge in current state so I will test using the CLOSED status.

This is the only way that I've been able to successfully deal with this. It's been hit or miss though.