RQC splitting into multiple purchase orders

The only reason that the system would automatically do this I can think of would be that there are different vendors on the req lines.

Here are a few ideas for you to consider.

Separate POs are always required for different vendors; I assume you are aware of that, but just wanted to start with the obvious.

Beyond that, the main driver of this is a flag called "single document to a PO", which can be setup in the RQ01, RQ04 and PO10 screens as well as the PO100 Auto-PO Creation job. This may even exist in other screens (PO01.4, I think), but I am working from memory here (on an airplane without Lawson access at the moment). Also, this field also exists in RQ10 (and possibly RQC) - when a requester changes the value in RQ10/RQC, this will override any over-arching setup. So, for example, I have a client that has asked requesters for "bill only" surgery reqs to manually alter the value in RQ10 to ensure reqs DO NOT combine with other POs. In other words, they typically allow reqs to combine on a PO, but they don't want this to occur on the BILL ONLY reqs.

Keep in mind - these flags are not as intuitive as you may think. And I have seen them work differently at different clients - either due to the version or the fact that these flags work in conjunction with other settings, such as the LOCATION CONTROL setting. So please make sure that you test your setup before you turn things on in production. (my advice - don't even try to use this setting in PO10.1/PO10.2; I don't think it works but if it does, it isn't likely to work as you may expect)

One final note: the PO100 job has a setting where you can set a "max # lines per PO"; this will also cause multiple POs for the same vendor (when applicable).

Hope this helps.

Req Reasons: Vendor #, Vendor purch from, check they didn't somehow put a different PO Ship to on the line. (edit) also check the lines all have the same buyer code.
PO100 Reasons: the max number of lines on PO100 has been set to 1 or some other undesired number, the items are two different item types and the PO100 is set to filter

Sorry - I misread your question and most of my answer is more relevant to the notion of forcing multiple reqs to combine.  

Let me try again

In addition to multiple vendors on the same req, one other option might be related to line-level approval; if an approver only approves part of a req, that req could slip through independent of the remainder of the req.  Another reason is the PO100 "max number of lines on a PO"

 

All the stuff I wrote about the Single Doc to a PO and Location Control is not relevant to this discussion, but I am leaving the comment as it might help you to understand how to allow reqs to combine.

Different vendors, buyers, or ship-to's or if you run separate po100's with filters that may pick up some lines and not others.

Same vendor on the req.  For example - we had a Mentor Breast Implant req split into three separate POs.  I do not see the line limitation field populated.  Could it be something else?

 

After a recent install/patch up we started to experience the same issue. We had one requisition that had about 70 lines and po100 created a separate PO for each line (so 70 PO's). We have worked with Lawson and no solution has been reached. So far this has only occurred for one requester (multiple times) and the only strange thing I noticed is it appear he was copying and pasting some strange characters into the requisition line descriptions. At this point the user has been advised to be cautious using copy and paste and we are monitoring to see if the situation occurs again.