Tracking EDI Part Number Discrepancies

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

Red

Veteran Member Send Private Message

Posts: 87

12/12/2011 9:46 PM

Hey Folks,
    I think this is going to end one of two ways:
    1) Someone is going to say something obvious, at which point I will smack my head and say, "Duh..."
    2) The answer will be a concise, "No."

    But here goes anyway...
    We use GHX as our EDI partner. Within their portal page, you can run a report showing all of the vendor part number discrepancies over a given period of time. This is terrific except: 1) You cannot schedule the report to run as needed, and 2) you have to rebuild the report request each and every time you log in to run the report. Doing this manually is not difficult, but it is a small, tedious pain, and I have enough of those in my life.

    So I thought that maybe I could somehow cobble something in either Excel AddIns, or in Crytsal Reports...and I hit a wall. It seems that when the EDI 855 (PO Acknowledgement) is processed, it should report differences in the recieved vendor part number compared to the sent value. It has been ages since I have looked at the report, so I could be optimistically mistaken. Assuming I am somewhere in touch with reality, if Lawson reports on the discrepancy, might it also not store the incoming value? (I know, I know...I am drifting away from the "real world".)

    So, on a very, very off chance, does anyone know if Lawson stores the incoming vendor part number from an 855. And, if so, any ideas where it might be stored (table name and data element). If I get any concrete leads, I promise to share the results of my labor.

    Much appreciated in advance,
        Red

Robert Spurr

Veteran Member Send Private Message

Posts: 130

12/13/2011 2:27 PM

Not sure how helpful this will be but Lawson documents the 855 and what it does/doesn't map. I took a look and I think it answers your question. the KB article is (AR_522654)

Red

Veteran Member Send Private Message

Posts: 87

12/13/2011 7:58 PM

Well, there's the smack to the head. That should have been my first move. So, thanks, Robert, for the reminder.

But, alas, everything that I was able to glean, from the document you mentioned and from other sources, seems to point to the fact that this probably not feasible. When the PO122 runs, it does create a report and a workfile, but it does seem to store the information in a table. There is probably still a way to make that work somehow, but extracting the report into a CSV or ftp'ing the workfile on a periodic basis essentially makes more work that playing with the GHX report.

Thanks for the assistance,
rw

JonA

Veteran Member Send Private Message

Posts: 1163

12/14/2011 12:18 PM

Have you approached GHX to see if they have a way of creating a custom report that could be emailed to you?

Red

Veteran Member Send Private Message

Posts: 87

12/14/2011 2:28 PM

Jon,
    That is a good point as well. I am not overly optomistic though... I seem to remember a request we made for the background/detail information that comprises the quarterly reports. This would have allowed us to port the information into our internal dashboard reports. I honestly do not know if we ever got that request fulfilled, I would not be the recipient of the extracts. I do know there was a lot of back-and-forth in the discussion and GHX was not very willing up front.
    Due to some other factors, I will have to bring this up with GHX early next year. We shall see...
    Thanks,
        Red

Rob Conrad

Veteran Member Send Private Message

Posts: 73

1/20/2012 5:59 PM

Hi Red -

I built a solution to pull this information from the ANSI X12 855 directly without using Lawson EDI and it sounds like that might be relevant for your reporting needs. The data could easily be ported into your SQL datawarehouse etc.

Please contact me if you would like to see a proof of concept demo and I'll put it on the calendar via Webex.

RC