1 Req, 1 vendor, 2 PO's created

 7 Replies
 2 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
Bev Edwards
Veteran Member Send Private Message
Posts: 366
Veteran Member

I have a user who created a req for 2 items, one a service, and one a special for the same vendor.

When the PO100 was run, 2 PO's were created instead of 1.

Why would they have not gone on the same PO??

Is it because they are 2 different types.

David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
Do you run separate PO100 jobs by item type?
David Williams
Bev Edwards
Veteran Member Send Private Message
Posts: 366
Veteran Member

Hi David!!

The buyer staff does run separate PO's for X type items.

Thinking that 2 different PO100's were run, that grabbed one and then the other?

David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
Yes, that's sounds like what happened.
David Williams
Kat V
Veteran Member Send Private Message
Posts: 1020
Veteran Member
PO66 can confirm the timestamp when the PO was created if that helps you tie it back to a job.
Bev Edwards
Veteran Member Send Private Message
Posts: 366
Veteran Member
Thanks for the PO66 tip!
I found that she ran one PO100 to pull 'X' items and another to pull 'S' items.

brupp
Veteran Member Send Private Message
Posts: 165
Veteran Member
Why the separate PO100 for xtype & service? Just curious. Our Purchasing scrutinizes those orders & that might be an option to quarantine those orders.
Kat V
Veteran Member Send Private Message
Posts: 1020
Veteran Member
We separate X items from the rest and leave unreleased for the buyer to confirm to reduce EDI errors and pricing "surprises". If you are using process flow to route for approval, you can also add the buyer for X or S type lines as a "review" (as we don't like to imply the buyer has to approve something that a director is submitting.)