Lawson IC with Cerner Surgi-Net

Yes, we are currently doing that... and have been doing it for about a year now. What questions do you have?

One other point to make. We are running 9.0.1.5 Apps, on a 9.0.1.2 Env on Solaris Unix... We had to figure out most of this all on our own as the documentation from either side wasn't much help.

I'd be happy to share some of the shell scripts and report files that I had to write to make this work, but maybe off-line would be better?

Jim9: Is this information something you'd like to pursue? I'm still willing to share and help, if I can. No reason to re-invent the wheel.

Greg-

What exactly does your interface do?  Is it bidirectional?

Jon (others):
Since we maintain all of our items in Lawson, we found the need to update the item master in Surginet, so mostly by trial and error we worked out a modified IC527 job that does what we needed. This is an outbound (to Lawson) interface. We do have an inbound (to Lawson) interface for creating Req's and/or pick tickets based off of the information that is on the surgeon's pref card for cases that are scheduled tomorrow... so that they can be picked today. Really 2 separate interfaces, but accomplish "pretty much" a bi-directional flow.

Greg, great to hear someone has an interface with Surginet.  Our project plan has started to replace ORSOS to Surginet in collaboration with another project to consolidate 3 sterile processing (SPD) areas into 1 location.  Each of these locations have their own cost center for the supporting OR.  So the consilidation of items may need to continue to issue out to varius cost centers.  Our current model in each of the SPD areas is an expense inventory using MSCM to replenish.

You mentioned you had a second inbound interface to Lawson.  Is this area set up as a perpetual inventory or expense invenotry.  I am intersted in learning more about your process.  Do you support more than one cost center using this model?  How are your returns managed? etc.,  How do you manage items such as implants that would not be itemized on a preference card? 

Thanks,

yvonne: unforunately I don't know much of this process... I'm just the technical guy behind the scenes.
I can tell you that all of our OR's are set up as perpetual inventory.. they replenish from distribution as well as vendors and each other. (setup in IC12)
Our main 2 OR's were separate cost centers when we started, but have since merged into one, with little to no changes to the interface. There is a whole bunch of timing that we needed to get correct, but so far it's worked well. Except when we have holidays.... then it gets a little screwed up, but we manage.
The interface (inbound) uses tables in Cerner/Suginet that aren't populated all the time, to run a Crystal report against and create an RQ500 input file which we happily load into Lawson.
Returns are handled by purchasing tied to the original PO they came in on if possible. Receiving puts return into shipped state once it actually goes out the door.
Implants are put in RQ10 with the SN Lot # etc that go to a bill only PO. This is handled by distribution. Some have item #s some do not.This part is for vendor payment. Above are entered free text or using an item # in Cerner by OR staff. This part is for the patient charging.

I'll attach the scripts and Crystal report file when I can dig it up again...

Script to run the job to import the file that the Crystal report file produces.
Export the Crystal report with no delimiters.

We recently instsalled Surginet/Supply Chain into Lawson. Everything is working fine. We did the following:
- A cerner consultant wrote the interface file from Cerner and formatted it into the IC500 layout.
- A daily recurring job runs the IC500 job
- Someone manaully release the records from the IC21
- IC142 and IC141 runs to create the requisitions
- Someone approve the requistions in RQ10

We currently have 3 perpetual inventories. We replaced ORSOS.

Someone was asking about our IC500 process from Surginet, and I offered to post a sample input file.  Here it is.

Run it through
cnvimp file_in 382> file_out
and run the IC500 job.

I've received a new test file for our Item Usage interface and the IC500 is giving an error:  bad file status 9 018 on file SORTINVXCT-FILE.  The file is in the path \d$\lsftest\hht and the file name is LAWSON_2661150_20180319.  Any ideas??  We have never had a successful test with Cerner and this type of file.

Hi Casy,

 

Below are the provided steps from Infor.  Greg references the same, so it looks like the process hasn't changed since 

 

Resolution:

Under$LAWDIR/prodline/hht you will find the file name from the IC500 job parameters. In the hht directory, enter: cnvimpSORTINVXCT372 > [temporary file name] (The input file should be 372 characters long like the workdef file. Filler characters should be added to increase the size if needed.)   2. Copy the temporary file back to the original file [SORTINVXCT]. (If filler characters were added in step 1 to increase the file size to 372, this should be done with the command:cnvimp[temporary file name]372 > SORTINVXCT 3. Recover the job.

 

I've done the command and it still gives the same error. The sample file that Greg provided is not in the 1 continuous line format so makes me think this is not necessary but I'm very new to this so there is truly no telling.

Can someone explain why it keeps giving SORTINVXCT as the filename when that is not my file name? I've only been able to find a metadata file with that name in it.

I can help a little. The first issue is that the file is not in the continuous line format.. so you have to make it that way by running a cnvimp in_file 1000 > out_file on it... this will stick it all on one line for you. The SORTINVXCT file name error will probably disappear after you get the input file in the correct format.

I finally got the file in! The '372' was an old KB so once I did the cnvimp in_file 1000 > out_file it worked. I noticed this decremented inventory but didn't produce a requisition to pull the items and take back to the OR. How is that approached? Are we running the wrong job all together?

To create Reqs you'll need the RQ500 job.
I can probably help with sample files, params for that job too... if needed.

Oh, wait... if the inventory falls below your re-order point, all you should have to do is run PO100 and PO120 to generate PO's... (I think?)

I was thinking about this last night and I think it would just be like our regular inventory as far as replenishments. Really need to talk it through with our Supply Chain and OR department though to make sure I've got my head wrapped around what they need it to do. If the counts are managed in IC12 in Lawson, then there would be no need for a "req" other than the one that would replenish from the IC12 true main stock inventory location. I think.

If they want to request a "fill" from their stock - they want a req. If they want to tell their stock that it's gone now - they might just want IC500 to create an IC21 to issue it out to expense. Then whatever IC140/PO100 or IC142 replenishment should take care of the reorders.

Is there anyone that can provide the scripts or directions that the Supply Chain department is using to make this work? I believe I have most of the steps but there are obviously some missing as it isn't quite adding up. Step 1 is to run the IC500 job to pull in the Cerner usage file. Step2: Run IC141 to create Stock requisitions; Step3: Release/issue final on RQ10; Step4: Run the WH130 to produce picks; Step5: Navigate to IC23 to receive in the items in the location after delivered; Step6: Run the IC140 to create nonstock Replenishment records; Step7: Run the PO100 to create PO's; Step8: Receive in the PO's; Step9: How does the inventory get incremented at the location we are delivering to for PO related items? Anything else?

Please be more specific regarding "PO related items". It sounds like these are non-stock items and therefore incrementing stock will not occur. How are these items tracked on IC12 for the location you are running IC141? If NO, you will need to run IC142 to create those PO's. If YES, is your RQ01 for that location fill or kill? If fill, you might need to include WH110 to allocate warehouse backorders. If kill, you're telling the system not to replenish killed items.

"PO Related items" are non-stock, yes.  Our IC12 is set to track inventory and when i ran the IC140 and IC142 it is not showing that it is creating any PO's. 

We hit a few bumps in the road and are back to trying to implement the interface for item usage with Cerner.  The issue we are running into now relates to IC21.  Our Cerner Consultant told us that they cannot filter their file to us by only those items we need sent that are built on IC12.  The interface runs in the lines that don't exist on IC12 to a blank record on IC21.  This produces a lot of "dirty" data that will have to be cleaned up or else I am concerned it will impact month end.  Does anyone know of a way to clear blank records on IC21 OR is anyone familiar with a way to get the Cerner file cleaner before it comes to us??