Single document to PO

Currently we have set up our RQ/PO system to be "Single document to PO" in RQ01 and PO100 for all our requesting locations/Ship To's. We would like to start combining requisitions to PO for all our vendors except JIT.

The problem is that Lawson requires the vendor/ ven purch fr to be populated the requisition header in order to use the single document to PO settings in PO10.1 and PO10.2. We do not populate the requisition header vendor on our requisitions. The vendor information is populated at the requisition line level as items are added to the requisition. Also, the "one ship to per PO" setting on PO100 won’t work as many of our JIT requisitions share the same ship to and we do not want any JIT requisitions to be combined on a PO.

Does anyone have a good way to get the requisition line level vendor information to drive the one req to PO? If not is there another way for just our JIT vendor to be one req to PO? I have looked at setting all the requesting locations that have JIT orders to be one req to PO but those requesting locations order from other vendors as well and I want the other vendors to combine requisitions to PO. Any ideas would be appreciated.

Thanks, Warner

Find more posts tagged with

Infor Lawson Supply Chain Group - Discussion

Accepted answers

All comments

Stace Webley

Hi Warner - It sounds like you are already doing Single Document to PO which you said requires the vendor and purchase from to be populated at the requisition header level. You also said you do not populate the requisition header vendor on requisitions. Only at the line level. If that is the case how are you already doing Single Document to PO? Are you trying to go to Single Document to PO or go away from that? Thanks.

David Wong

Hey, Warner.

It's Dave Wong. How have you been doing?

Let me provide you with our PO100 Combining Reqs factsheet. It is found attached to KB 1211660. And if you got time now. There is a Lawson v10 Office Hours Series meeting about to start in 5 minutes. I'm trying to find your email address to forward the invite.

I thought PO10 combining works off the line level vendor information.

bone

Correct we are already doing single document to po for all requisitions/PO's. We are able to do that because requesting location is populated at header level and we have all requesting locations set to one source to one PO. We need to be able to get to the vendor/purchase from level which is not currently being populated at the req header for all requisitions.

bone

Hi David my email is wjohnson2@phs.org

Stace Webley

Hopefully, I'm understanding this correctly. If you have all of your requesting locations set to No for Single Document to PO then it will combine them which is what you want. However, at the PO Vendor level for JIT you would turn on Single Document to PO and hopefully in the hierarchy of things that will allow the JIT orders to be on their own PO's.

bone

PO Vendor level is not evaluated if the vendor on the requisition header (misc tab) is not populated. We do not populate the vendor info on the req header.

David Wong

Bottom line. Warner is trying to set up the majority of requisitions to combine to one PO. But there is at least one Vendor Purchase From location that they want to receive in separate packages from the vendor. We ruled out PO10/PO10.2 Location Control because all settings combines in some fashion. The only setting we are aware of that will not combine is the Single Doc to 1 PO flag. Controlling that flag at the vendor level is cumbersome. Having the requester manually set that flag is not reliable. We were hoping to find an easier method. So far, setting up multiple Par Locations is the best we could find.

jon-athey

I just ran this scenario through our test system. Setting the Single Document to a PO flag to 1 on the PO10.2 seems to work (Location Control flag set to N is also required). I created three reqs for different Req Locs (but same ship-to location) for the same item, released them and ran PO100 for the vendor/loc with the flag set to 1. PO100 created 3 separate POs. Then repeated the process but for a vendor/loc with the flag set to 0. PO100 combined the three reqs into one line. That is what you're trying to accomplish, correct?

unknown

What are you PO10.2s set for Location Control? I'm JIT and mine are all set to H (Cannot mix req loc on PO) and it works a charm. I don't care if two Cath Lab reqs combo JIT - as long as it doesn't also combo with the OR from the same doc.

unknown

Hi David!

This seems to be a bug. On PO01.4 you used to be able to make it look at PO10.2 FIRST for Single Doc to PO flag - in fact, it screwed me up when we first went to v10 in 2016.

But I just messed with my test setups and even if I make Req loc the last place to look - it overrides the vendor loc on the req line?

What's the PO01.4 controlling if not reqline?

dechevar

Warner,

OPTION 1

You could set up a PO10.2 just for your JIT vendor and tie the items to a contract for the JIT Vendor 10.2. That way you can use the PO10.2 One Document to PO setting for your JIT vendor it it would populate to the reqline automatically based on the Default Vendor settings. Your perpetual locations would order bulk from the main PO10 Vendor and requesting locations would order from the JIT vendor PO10.2. It creates a double load of your contract, but allows you to accomplish what you are trying to do.

This is assuming you have identified which items should be ordered JIT and that is the only way you order them. Otherwise, you set the Priority on the JIT contract higher than the non JIT contract and make your requesters enter the vendor without the purchase from when they need to combine orders.

OPTION 2

Set up JIT Requesting locations where appropriate and have them use that location when ordering JIT. Set the location to Single Document to PO. We do this with our Par Location for an AU. All Pars are set to One Document per PO. They can order from their default location or the Par location.

bone

Thanks for the two options Dan. I like option 2 as we don't require vendor or purch from on the requisition header (misc tab of rq10) so the PO10 one source to one PO options are not evaluated when the requisition is created.

Copyright © 2025 Infor. All rights reserved.