New PO Suggestions / Requisitions and POs

Hi there,

We went live on 2022.2.17 from E10 just over a week ago. We have noticed that requisitions for same vendor, same date, same everything, are getting made into separate POs when clicked for buy (at same time) on New PO suggestions. Is anyone else seeing this behavior? I looked for new field to see if there’s a setting, but have come up empty.

Thanks for input,
Nancy

Nancy,

I remember a part plant toggle that controls this… and I am drawing a blank on whether it did or didn’t work for me way back when and it really turned out to be due date driven.

Nancy, here’s a thread I had on it a while back… maybe it will help?

1 Like

Thanks Utah. I have found that part class might have an effect here too. When I test with a requisition for particular part classes, they all end up on same PO, then for others, separate PO per requisition line.

Ugh… Still not sure what it is, the only difference I can see between the part class that behaves one way vs the other is one that does get the Req lines combined on a PO has a buyer assigned. The part class that has no buyer assigned happens to be the one that the Req lines are generating one PO each to same vendor. They both are checked for allow requisitions and both are unchecked for split PO.

Nancy

1 Like

Split PO uses the comment field to know if they need to be split. If the comments are the same or blank are those the ones getting combined? Maybe they are silently splitting even if the class does not have it set since there is not a buyer.

1 Like

Good point Greg, it’s been so long since I reviewed this functionality that I’m not sure of anything on this subject anymore.