Are there any other users out there using GHX for their EDI transactions? I'm pretty fond of them thus far.

But up to this point, all we've done is 850s and 855s. I am really pushing to get the price updates (832) and the electronic invoicing (810) for our primary distributor (Owens-Minor) this year, but noone in the facility has done either of these transaction sets, and I'm wondering what to expect.

The way I read the 810 documentation, my carrier is fine, since we're already trading. I'll need to set up a trading partner entry for the 856 transaction, and I'll need to make any entries necessary in the substitution table <-- are there many? Once I have that done, and can successfully translate the inbound file, I run the MA540 job, and that picks up the translated file and inputs the invoice(s), and generates the matches - then we release the document (provided everything else works correctly)?

Do I have the scenario correct, and is there anything I'm missing, or need to watch out for?

Our Purchasing dept decided against getting the pricing update because we have some contracted pricing and they were afraid of the 832 overriding that contracted price. Not sure if this is something that can actually happen, just giving my $.02.

It would be a concern in some scenarios, I agree. With our primary distributor, they load our contract prices in their system (+ markup), so I assume that would be the figures they send me in the 832 file.

Thanks for the input!

We utilize 850's and are in the process of enabling 810's. We also use GHX as our EDI Carrier. ED502 is used to retrieve the Vendor EDI file via GHX (in EDI protocol) and translate to MA540CSV comma delimited. It is necessary to make a few ED40 table mapping entries for the data to translate properly. The MA540CSV file is then used as the input file for MA540 to Add/Match Invoices for PO's. Reports are generated to list exceptions.
We are working with GSC on Special items corrections using MA54.

Not sure if you are still working on this issue or not. We don't use GHX yet, but will be switching to them in about 4-6 weeks. We currently use Neoforma and I am told the transition will be easy (yeah, right!)

Anyway, we have been doing both the 856s and the 810s for about 1 1/2 years. It's usally a struggle at 1st, and your substitution table are where you will solve your problems. Currently, we are having little to no issues with the 810s and they are worked daily in the MA54 by AP mostly with line # corrections.

The 856s are another story. I really haven't been real successful figuring out which substitution tables need work. I am on a big project to get this all straightened out before we move to GHX (target date 6/1/06).

832s are something that we never did figure out and have abandoned. I hope to pick this issue up this fall. :rolleyes:

1.For 810's and 856's you will need an ED10 record for each of the tranaction types and TPID.
2.As noted earlier, you may have some ED40 work, but if you have your (tpid)_I_COMPANY, (tpid)_I_VENDOR, and (tpid)_O_SHIPTO's setup you should be on your way.
3.For your 856 (known to be the problem child) - You will need to run the MA531 job, but the details is where the fun is at. Layout, procedure, history(we move the file daily), zero quant or cancelled lines, etc. We have Cardinal.
4.For your 810's you run the MA540. You may want to create separate files for each 810 vendor. Same stuff, layout, procedure, history. One of the biggest issues we had was the processing of MA54. No one was doing it, and they did not know how to work through all of the different errors. Also, when the month closes the errors that are in the MA54 need to have their date updated to post to the new period (MSAddins works well). MA60 volume may bump up as well so keep an eye on it. Make sure to run the MA540 against the Database to grab any of the fixed errors.
5.Timing of your processes are key, especially if any have failed. If your 856 fails, inventory levels don't get updated, etc. If you run the 810 before the 856, and the vendor sends the receipt and invoice the following day, everything goes to MA60.
6.Just some stuff - have fun!

Oh ya, for the 832, they nixed it, and are using MS Addins to update future date and price on the contract items.

Thanks for all the information, all...I love this place.

We're skipping the 832 for the time being, as we (slowly) transition to a different way of handling our contracts...so, we're jumping on the 856 bandwagon instead.

So far, I've managed to kill off two 856 files by trying to run the ED502 as myself, instead of the edi user. My profile does not have the directory permissions to write the MA531 file...so, a valuable lesson learned, and a clear resolution found in the knowledge base. Hopefully, I'll be able to process this afternoon's 856, keep your fingers crossed for me.

Okay, after more than a year's hiatus, I decided to tackle the 856 transaction again. I've got the EDI side functional (I think), and the MA531CSV file is getting written to the right place. However, when I run the MA531 job, I get a colorful assortment of errors, from UOM to buyer code, etc.

So I take a look at the csv file itself, and it looks like some of the data is in the wrong place. For example, according to the Lawson MA531 file format, the buyer code should be in field 45, and the bill of lading number should be in 46 - but the BOL number is in 45, and the buyer code is nowhere to be found. Same story for the vendor item number - it's in field 63 instead of 64.

Any ideas? Is this a setup error somewhere? It doesn't strike me as a problem with the substitution table...perhaps I've got the wrong process or map settings on the ED04 record? If anyone else has pulled this transaction off with 8.0.3, GHX and Owens, can you give me any clues?