PO100-Purchase orders - LawsonGuru.com - LawsonGuru.com Forums -

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

Chesca

Veteran Member

Posts: 490

8/28/2017 12:46 PM

For some strange reason, all of the sudden the PO100 auto job is now creating purchase orders intol 1 single PO# for different ship to locations/Pyxis locations. We need to have 1 purchase order created for Each Separate Location. So if we have orders from Location 1X & 2X for example - these must each get their own PO number.
They can not be combined into 1 Purchase Order.
Up to RQ500 the settings/parameters were fine and it created individual source documents..
Once the PO100 ran - it took those individual source documents and combined them all into 1 Purchase Order.

Any ideas why this might be happening or how to fix it?

JimY

Veteran Member

Posts: 510

8/28/2017 1:18 PM

A couple of places you can check would be RQ01 - Requesting Location and PO10 - PO Vendor.

Chesca

Veteran Member

Posts: 490

8/28/2017 2:47 PM

RQ01 for location ANEST pyxis is set to N, should we change it to Y?

MChism

Basic Member

Posts: 15

8/28/2017 3:14 PM

What are your parameters in PO100. Specifically on the Main screen. This has been working in the past and is not working now all of a sudden? Any patches or updates recently installed?

JimY

Veteran Member

Posts: 510

8/28/2017 4:30 PM

Mine shows 0 or blank for do not combine. 1 would be combine.

MChism

Basic Member

Posts: 15

8/28/2017 5:04 PM

Our reports are similar. I have a "N" in One ship to per PO and a "N" in Combine on PO Line. Those two fields stuck out to me so I wanted to confirm.

Chesca

Veteran Member

Posts: 490

8/28/2017 6:25 PM

The last patch applied on on 7/30 patch 113621.
parameters:

company = 00
Include cost option = N
Release purchase order Y
maximum number of lines on PO blank
one ship to per po N
system code RQ
Default Delivery Days 1
Combine on PO line N

MChism

Basic Member

Posts: 15

8/28/2017 6:40 PM

I'm assuming that you all run the jobs more frequently than once a month so the patch on 7/30 would have no affect correct? You have ran the 100 successful since the patch?

Parameters are how I have my jobs set.

In RQ01 for that location can you check to see the setting for "Single Document to a PO" field. I have a 1 in that blank.

Chesca

Veteran Member

Posts: 490

8/28/2017 6:48 PM

Single Document to a PO" = blank/no default

JimY

Veteran Member

Posts: 510

8/29/2017 9:30 AM

Is it possible that the record coming over from Pyxis is populating the field with a value to combine the lines? Did something change on the Pyxis side?

Chesca

Veteran Member

Posts: 490

8/29/2017 6:50 PM

Ok I asked Infor and the Vendor what field this is and what it does and found out that Single Document to a PO is set to 0 by the vendor. According to Infor, If the single document to a PO needs to be set to a 2 on RQ10 then have the vendor set the value to 1 in position 623 in our file. This will create the requisition in RQ10 with a 2 set that that field and resolve your issue going forward. This is not a Lawson issue and the system is working as it should.
The issue is that this field has always been set to a 0 and we didn't have this issue and it's not only happening to our pyxis location but all the locations.

Sandi

New Member

Posts: 1

12/18/2019 4:08 PM

How often do you run Lawson ERP PO100, multi-day, daily, weekly, or monthly?

Greg Moeller

Veteran Member

Posts: 1498

12/18/2019 4:27 PM

We run PO100 via a scheduled job daily, and then the purchasers sometimes run it themselves.

JonA

Veteran Member

Posts: 1163

12/19/2019 1:20 PM

Same as Greg. We have scheduled PO100 jobs that run every half hour for specific req locs, others that run a couple times a day, and then buyers will run it as needed.

Kat V

Veteran Member

Posts: 1020

12/23/2019 7:22 PM

We have several PO100s throughout the day based on PO Type:
8am - bill onlys
10am - special shipping (overnights)
11am - regular orders
12pm - special shipping (overnights)
2pm - late regular orders
We also have PO100s running triggered by an IPA for our eBuilder interface.