RQ500 Interface - File Example - LawsonGuru.com

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

Kevin

Basic Member Send Private Message

Posts: 9

6/12/2013 4:49 PM

Good afternoon! We are looking at using the RQ500 interface program to interface a requisition file from our TMS application. I have went out to Lawson KB and can see the file layout, but there is no reference of 'required' -vs- 'optional' fields. I would think that based on what we're going to be using, only a handful or two of the fields will be necessary. Is anyone doing this now and if so, would you consider sharing a sample of your interface file along with any other 'tips' you might be able to share? We are currently using Lawson RQC for Req entry and only a handful of RQ10 entries each week, as a majority of our orders go in as PO's into PO20. I appreciate any feedback that is offered. Thank you.

Greg Moeller

Veteran Member Send Private Message

Posts: 1498

6/12/2013 8:49 PM

Kevin:

Currently we have an RQ500 file interfacing from Cerner's Surginet...
From what I can remember, company number, seq number and the dates are pretty much required...
If you have a test system, you can start with that, and whatever won't load will let you know (pretty close) to what and where the problem(s) are.

I can't remember if it's required or not, but a standard record size of 1165 is used, so if you are getting an interface file created, it's much easier to have the file created with a fixed 1165 record length.

Due to our sample files containing Dr. and Patient information, I cannot upload them here. I'll see what I can mock-up though tomorrow.

Are you guys Windows or Unix?

Kevin

Basic Member Send Private Message

Posts: 9

6/17/2013 2:28 PM

Hi Greg - Thanks for the reply. We are running UNIX release 9.01.8.

StephanieD

Veteran Member Send Private Message

Posts: 39

6/19/2013 2:10 PM

Kevin, In the Lawson requisition file layout that i have, on the RQ500 tab, it does show the required fields for each record type (header, line, and comment) - listed right above the field list for each record.

Greg Moeller

Veteran Member Send Private Message

Posts: 1498

6/19/2013 6:38 PM

Kevin:

Here's an example file that you can use for comparison... I know for a fact that this file works here.

-Greg

Attachments

RQ500TEST.zip

Kevin

Basic Member Send Private Message

Posts: 9

6/21/2013 5:12 PM

Thank you Greg! I will see how this compares to what we have been working with. Have a good weekend! //Kevin

Chesca

Veteran Member Send Private Message

Posts: 490

1/6/2015 3:34 PM

Could you please tell me if RQ500 creates an output file? We interface with Pyxis and they send us a file rq500c that's input to RQ500; however I am not sure how to tell if it generates a file. Thanks in advance for your response.

Kat V

Veteran Member Send Private Message

Posts: 1020

1/7/2015 1:12 PM

Yes - the job generates a RQ500.prt to the print manager - ours shows up as user "pyxis". It shows the requester and req number created and will tell you any lines that error out.

Chesca

Veteran Member Send Private Message

Posts: 490

1/9/2015 7:43 PM

Thanks, Kat. I am new to supporting the procurement system. I am looking at job scheduled in REC def to process a file from pyxis. I am trying to figure out why there is a PO100 before run before and after RQ500. Any help would be greatly appreciated.

Ragu Raghavan

Veteran Member Send Private Message

Posts: 477

1/10/2015 10:46 PM

RQ500 will create Requisitions. PO100 needs to be run to create Purchase Orders based on released requisitions. RQ500 will generate an output file, if there are errors, in the folder $LAWDIR/productline/hht

JonA

Veteran Member Send Private Message

Posts: 1163

1/12/2015 12:25 PM

I would question why there's a PO100 run prior too the RQ500.

Kat V

Veteran Member Send Private Message

Posts: 1020

1/16/2015 5:52 PM

What are the parameters on the before/after PO100s? I kinda agree with Jon. Unless the idea is to make sure the RQ500s are on their own? In that case the first PO100 is to clear out "other/manual reqs" and then run the RQ500 and then PO100 - the second PO100 is then "only these orders"

Are the POs released both times?

Chesca

Veteran Member Send Private Message

Posts: 490

2/9/2015 4:18 PM

Ok, the parameters on the before PO100s are as follows:
Release purchase orders = Y
report level = D
vendor option = I
Vendor, purchase from = 1 (XXX Hospital Supply).

second po100
Release purchase orders = N
report level = D
vendor option = I
Vendor, purchase from = space (I guess all the vendors).

Chesca

Veteran Member Send Private Message

Posts: 490

2/9/2015 4:26 PM

According to last programmer's notes: There are two end results to this job, POs to XXX hospital and picklists all for the Pyxis machines

After RQ500 run

PO100

release purchase = Y

Vendor, puchase from = 1 (XXX Hospital Supply)

second PO100, same parameters

JonA

Veteran Member Send Private Message

Posts: 1163

2/9/2015 8:11 PM

I looks like kinda what Kat said. The intent is to seperate your Pyxis orders from the other orders going to XXX Hospital Supply. The first PO100 cleans out PO23 of all lines from other departments going to that vendor and RQ500 then creates the Pyxis lines and the second PO100 moves those to a seperate PO.