PO Compiling

Yes, we have been using it for about three years without any issues!

Hi, sorry I did not see the reply!  Can you tell me the steps for setting this up? We currently compile all vendors daily. I went to PO10 and set a specific day (Thursday) for one vendor. But this vendor still compiles daily. What other fields do I need to set to make specific day happen for specific vendor.

Thanks!

Can we reopen this topic. We want to Compile a particular Vendor for Nonstock items. We want this Vendor to compile/order only on particular days as we need to meet a minimum order.  You cannot combine multiple Req locations per PO since they are with different Buyers. We were told by Lawson that only Inventory orders can be set to compile on particular days.

Does any one have a Vendor (for Nonstocks) that they compile based on dollar amounts, or days of the week ?

 

Thanks!

We don't do what you're asking but here's a thought. When an order comes into PO23 for this vendor, have your buyers change the buyer code to some code that you don't run a PO100 for. You could even create a code specifically for this. Leave those items alone and they'll accumulate in PO23 and you can run a PO100 (or schedule one to run weekly) on your order day for the vendor. You could change the buyer code in PO20 if necessary before release. You could replicate this process for any vendor that you have specific order days. All your buyers would have to be aware of the process of course.

I think the issue would be how to catch the PO23, as we have them process right out of there, the buyers never even look in PO23. But I like the thought of somehow keeping it from compiling and building up in there...

PO100 has all kinds of run options, but it depends on how your're setup of course -
We use a combination of Requesting Location Attributes, Vendor Attributes, Item Type and Include/Exclude options on the PO100.
Look upstream to the source of lines for that vendor you're trying to compile - if you can make them different (Like JonA suggested with the Buyer Code) you can manipulate your PO100 to process separately.

Thanks, will have to give this some thought. We do not use attributes, but should be able to flag these items somehow. And then make changes to the PO100 to accommodate them.

 

Thanks, will have to give this some thought. We do not use attributes, but should be able to flag these items somehow. And then make changes to the PO100 to accommodate them.

 

Assigning attributes is something I haven't been able to figure out. I've looked at it but it just doesn't click for me. Is there a guide on what screens are needed to do this?

Also Sheri, you can exclude up to 4 vendors on the PO100 job. Kind of limiting especially if you already exclude some vendors for other reasons. But your buyers could use this to avoid pulling those items out of PO23.

Hey, that sounds like a good method. We have the PO100 set up in recdef. Not sure how happy the IT guy will be to work a new one, but that sounds like something that may work for us.

Thanks

 

Yea that attributes looked like a lot of layers last time I checked into them. We have never gone very far into trying to figure them out.

Folks, I have two thoughts (and then I have hit my quota for the day)...

Thought 1 - Define PO100 jobs, or step jobs, explicitly identifying the vendors you want run at particular time or time/day parameter. The primary benefit is that you can be VERY granular in your mapping (Office supplies once everyday at 2:30PM, and Lab products every Tuesday at 11:00AM). The downside is that this can be a bear to manage and maintain (but this is what we actually do to some extent).

Thought 2 - Use the Order Days functionality of the PO Vendor/PO10 and Purchase From/PO10.2. We do not use this (although I have been a proponent of experimenting with it). By Lawson/Infor's own definition, this is their intent. The only downside I can think of, with no experience, is that there is no guarantee that you will not have multiple orders on the defined days (based on how your "sweeps" are configured).

Good luck,
Red

Thanks for those thoughts! :) we will def be checking into this option and all these details help!

 

 

Okay... So three thoughts.

Thought 3 - Following up on Attributes (now that I look at it). Attributes are not that difficult to set up, but it definitely helps to have the end-goal in mind. (We just defined attributes for Vendor Diversity Classification). You could set up a single attribute that defines the OrderDay. You would then need to assign a value to all of your vendors. Then you would need to set up a separate PO100 job related to each value you defined. My thoughts run towards the following values:
- DAILY
- WEEKDAY
- SUNDAY
- MONDAY
- etc.
It replicates my understanding of the Order Days I suggested, but gives you more flexibility ("TUESDAY PM" or "THURSDAY 1500"). Again, each defined OrderDay attributes would need a correlated PO100 built.

I could see this working as an answer.
Red

We have attributes on RQ01. Assuming Vendors are the same: You create the Attribute on MX00 and tie it to object Vendor.  You will have to click on the Attributes button on AP10 to see what screen you need to upload the values to.

I would suggest making ONE attribute called POBATCH - and assign the values: DAILY, THURSDAY, WEDNESDAY, etc.  I would consider making it required, but unfortunately there is no way to set a default that I know of.

Then go to MX10 and create a list for vendors called DAILY where the POBATCH attribute is Daily - Daily.  One called THURSDAY where it's Thursday - Thursday, etc.

 

These MX10 list names are what go on your PO100.