Data Upload Quality Control

Hi,

We have recently implemented a new Epic application and have began to noctice a negative perception on the application itself and Lawson that's stemming from information discrepancies

What we hope to find is some information on data quality management techniques and how other facilities upload/update information in Lawson.

We currently use the Lawson Add-Ins feature within Excel to upload new information. The process of running the uploads has worked well for us, but we have concerns with efficiently identifying duplicate information (i.e. descriptions) and ensuring that what we are loading is what we truly need to load.

We use GHX NuVia as a data cleanser and it has helped with assigning noun types, UNSPSC or HCPCS codes, but we noticed with a recent update that NuVia suggested for descriptions, we ended up duplicating the same description for mutliple items.

Any feedback on pre-load data quality check processes or post load audit checks would be greatly appreciated.

Thanks

Find more posts tagged with

Infor Lawson Supply Chain Management - Discussion

Comments

unknown

John,
We also use Add-ins for Lawson S3/Landmark and Lawson Spreadsheet Designer for Lawson Rich Client (Contract Mgmt module). We are also utilizing GHX Nuvia for the time-being. Our renewal is coming up due and we are entertaining the thought of opting out of our renewal due to data inconsistences (incorrect part # in Nuvia vs Order Center, desc's not standardized for like items, lack of information, difficulty with vendor matching due to mergers/acquisitions, etc. So what I'm saying is I feel your pain. One recommendation when doing mass uploads is always to use the Highlight Duplicates function in excel. This would have caught the duplicate desc's. We also attempt to gather as much information directly from the vendor as possible. I also have access via Microsoft Access to pull directly from the Lawson tables so I have some queries built that allow me to look for certain discrepancies and pull certain information. Hope this helps or at least lets you know that you're not alone.
Kyle

greenj

Kyle,
How did you link Microsoft Access to pull directly from Lawson tables? I would love to set this up where I work but the ability to do so have never been mentioned. We are linked with Microsoft Excel via addins but that's still not a direct link to Lawson tables. Thanks for any info you can provide.
Jerry

unknown

Duplicate descriptions are still a sore spot and we've been on Epic for years now.

We also use NuVia - we ended up "relinquishing" the IC11 D2 to Epic. We populate both D1 and D2 with the Nuvia descriptions - but there are still dupes as Stryker and synthes ortho screws are the exact same thing.

So the item upload is created with D1 and D2 from NuVia. We load into lawson everywhere but the IC12 for Epic. We send the upload to Epic.

What version of Lawson are you on? In 9 we were loading the NuVia description to UPN1 - it would cut off, but it transmitted as an alias field to Optime and reduced the calls of "what is this"

They review and change the D2 as desired or refuse the item to Epic altogether.

We then load to the Epic IC12 - which is what triggers the item to interface and transmit to Epic the following night.

unknown

Jerry,
I had to get access from our IT dept. to get connection through the ODBC.

Copyright © 2025 Infor. All rights reserved.