PO100 Creates duplicate POs

Has anyone else experienced multiple POs being created when PO100 is ran? If so what have you found to be the cause...any input would be helpful.

Find more posts tagged with

Infor Lawson Supply Chain Group - Discussion

Comments

unknown

Could be some default settings you have set up in programs such as PO00, PO01, RQ01 - for instance, I see a flag in RQ01 where you can specify one PO per requisition.

unknown

If I had flagged RQ01 as one PO per req (or any other setup form), ALL the reqs would be doing this, not just a few occasional ones, with no logical consistency.

Infor HRCM - Stay Prepared, Engaged, and Informed - HRCM v20.1 Web.pdf

unknown

Wouldn't know that from the original post - thought it was going on all the time instead of randomly.

unknown

Sorry, I didn't do the original post - just responded with what we experienced - which I think actually appended to another duplicate post.
I should probably have let the original poster respond about the flags.

unknown

Are you (either of you) having the issue of 1 requisition with multiple lines generating multiple POs? Or multiple requisitions to the same vendor creating multiple POs when you think it should just create one? Or both? Or something else entirely?

unknown

Our experience was that the ValueLink items would be all from one req, and were processed by one EDI job.
There were a few days in February when it created a hundred one line POs (in addition to the normal multiple line POs), and some days when it created only a few one liners (the others on those days were multiple line POs as expected).
Lawson recommended application patch JT 223233 (CTP 77946), and we were leery of applying it, as the readme showed it touching lots of stuff. However, when I finally did apply it, only PO100 was compiled (although it did some other updates).
The large number of one line POs has not reoccurred, but that was also true before I applied the patch (I was on LOA, and didn't apply it until early March, when I returned).
So I really don't know what caused it, or what fixed it.

rommel-gutierrez

Guys thanks for your responses...

I think you hit it on the head, it is inconsistent. There are some scenrios with some vendors where PO100 will consolidate all lines and others that won't. At first I thought it was realtive to pfroms designated on the requsitions, but even that proved to be inconsistent.

@gPadgett- regarding your post at 3:40pm 4/1/2013; our issue is primarily your second scenrio.

unknown

PO10.2 also has a flag per vendor/purch from that will prevent reqs and req lines from batching together. Your scenario - multiple reqs not combining - sounds like the PO10.2 Location Control (bottom of the main tab) is set to N - "Cannot Combine Requisitions"

We use H - "Cannot mix req loc on PO" for all.

Copyright © 2025 Infor. All rights reserved.