Distributing a Buyer's workload

We want to set up our top 20 vendors to go to a specific Buyer or Buyers. We can do that on PO10. But we also have the RQ01/Requesting Location set up by Buyer so that if an order is placed through RQC that when the RQ10 and the PO20 gets created it defaults in the Buyer Code from the RQ01. It appears that the RQ01 takes precedence over the PO10. If we remove the Buyer Code from the RQ01/Requesting Location keeping the Buyer code on the PO10 when items are selected for that vendor the RQ10 and PO20 get created with the Buyder code from the PO10. BUT with the RQ01 having the Buyer Code removed and we place an order to a different vendor that does not have a PO10 Buyer code assigned to it the RQ10 and PO20 get created without a Buyer Code. Does anybody have a different way to accomplish what we want or a whole different way of handling the distribution of orders?

Find more posts tagged with

Infor Lawson Supply Chain Management - Discussion

Comments

Stace Webley

Here are a couple of questions:
1. If there is no PO10 or RQ01 buyer code defaulting then it isn't set in either screen and therefore probably isn't one of your top 20 vendors correct? If I understand you right then your top 20 vendors will either have a PO10 or RQ01 buyer set.
2. Is there a problem with not having a buyer assigned?

Possible solution:
1. Because you are trying to route your top 20 vendors to a specific buyer(s) then use either the PO10 or RQ01 screen. For reqs that don't get a default buyer then use PO100 to default a buyer for orders where no buyer is defined.

0712131256598360.doc

Stace Webley

You can set a default buyer at the Item Location level (IC12.1).

jon-athey

The PO100 solution will work for nonstock items if there is a corresponding IC12.1/IC12.2 record for the requester's From Location. But it won't work for special and service type items. Setting a default buyer in IC12 leaves you with the same issue as setting it in PO10- RQ01 still overrides. Most buyers are responsible for departments or commodities. Setting up buyers by item location would be difficult to manage. I seem to remember submitting an enhancement request that would allow changes to the default buyer hierarchy. We wanted to be able to set the PO10 default buyer above RQ01. I don't know where the enhancement requests are anymore with the switch to Infor Xtreme. Doesn't help you much I know. Our old system did have the buyer for the vendor override the buyer at the department so we've been waiting for this change for a while.

[Updated on 7/18/2013 3:19 PM]

StephanieD

All our buyers are set by vendor on po10, except a couple buyers who are specific to a few req locs, but they enter their own reqs, so they put in their own buyer codes.
Is your requirement to have all non-inventory req lines for the 20 vendors get specific buyer codes from PO10 and then all other non-inventory req lines for other vendors to get the buyer code based on the requesting location?

Stace Webley

I've never done this, but on service type agreements you can set a default buyer in PO25.1 under the Header Type Specific tab. However, this doesn't address the original question. I'm only saying this because Jon mentioned the buyer not defaulting on X and S type items and I'm wondering if PO25.1 would take priority over RQ01.

cassie

Thank you all for sharing your wisdom and ideas. It appears that the way we are using Lawson...RQ01 will always over-ride. We manually release our purchase orders so we like them to have a Buyer ID on them for further tracking. We do commodity currently but considering doing it differently in the near future. I did find the PO04.3 and PO04.4 but no luck with that and in a chat session with Lawson they said those screens are to Limit buyers to specific information not to default buyer ID's in. Again thank you all!

cassie

Stephanie, yes to your question. That is exactly what we want.

StephanieD

If your requirement is to have just a few vendors set with specific buyers and then to have the rest of the non-stock po lines (RQ source) get the buyer based on req loc, you could setup a req loc attribute (MX00), where the buyer code would be set for each req loc (RQ01.2), then setup req loc lists (MX10) - one for each buyer, then you would have to run/schedule po100 separately for each req loc list (Req Location Attributes on Filters tab) and have the
appropriate buyer set in the po100 default buyer.

jon-athey

What version of Lawson has the MX screens? I asked our security admin for a list of all screens last fall to make sure I had access to all the supply chain related and no MX screens were in the list. We're on apps v. 9.0.1.4

jreese

MX screens go back to version 8 I believe. I know they are definitely in 9.0.1.4. They are part of the ifsrc codes.

StephanieD

I believe the MX screens have been around since before 9.0.1. An email that I have from when I got access shows the MX screens are under the IF system code, as jreese mentioned. I have been using these to group req locs (for a different reason) on PO100 since the beginning of this year. We're currently on 9.0.1.12.

Legacy Contributor

The MX screens were available for Procurement only with 9.0 and higher - previous to that you only had them on GL and AP side of the world.

I have PO100s running based on Req Loc Attributes so I can attest that that should work.

Jon - MX module still falls under GL - which is why LSF doesn't consider it part of Procurement roles.
[Updated on 7/31/2013 10:15 AM]

Copyright © 2025 Infor. All rights reserved.