EDI 856 ship notices

You can do this if you format the csv file correctly. I've attached the MA531 file layout for 9.0.1 and an example of the MA531CSV file from the 856 we received from our primary supplier this morning. Place the formatted file in lawdir/work/MA531CSV/ and run MA531. Run PO134 if you need to print the receivers.

Hi Joha and thank you! Just so that I understand this process, ED502 ran this moring at 7:05am and pulled/received 106 file(s) from NEOFTPGHX. Are these the files that update receiving so my users can see a po received in PO30? MA536 ran this morning but had lots of errors.

MA531 report
448 1 8 -0000 PO Line 000001
Error On: Receiver Line
Message: Validate PO = "Y" and POLine does not exist
253 004000


ED502 Log
20151208070548,111, RECEIVED DATA WRITTEN TO:
20151208070548,112, /prod/law/env/edi/comm/in/NEOFTPGHX.20151208070538
20151208070548,113, ARCHIVING RECEIVED DATA TO:
20151208070548,114, /prod/law/env/edi/archive/in/NEOFTPGHX.inb.20151208070538
20151208070548,115, Archived [/prod/law/env/edi/comm/in/NEOFTPGHX.20151208070538]
20151208070548,116, DATA RECEIVED FROM NEOFTPGHX

20151208070548,130, Application data written to:
20151208070548,131, /prod/law/env/edi/in/POEDIASN

The path set up in your 856 trading partner is different from ours but I would say based on the fact that the ED502 job wrote data to that path you are receiving 856 files. Do you mean MA531 had lots of errors? You can correct those errors in MA53. But I will say that we just delete the ones in error because there are only a few and receive off the packing slip for any shipments not processed by MA531.

JohA, I am having a problem because the MA531 does not find either a PO number or the company number. I contacted Lawson and they are saying it's not their system. I contacted GHX and they are saying they don't see anything wrong with their file. I animated the program and I can clearly see that some transactions are missing that information.

The PO number should be sent in PRF01 (see example below). If you look in the 856 file do you see a PO number for the ones that erred?

ISA^00^ ^00^ ^ZZ^SENECA ^ZZ^9898393328 ^151209^1930^U^00401^000015906^0^P^|~
GS^SH^SENECA^9898393328^20151209^193032^15906^X^004010~
ST^856^0001~
BSN^00^1788610^20151209^1930~
HL^1^^S~
TD1^^1^^^^G^1.0000^LB~
TD5^^2^SEN^^Seneca Truck~
REF^BM^1~
REF^CN^SENECA~
N1^SF^SENECA MEDICAL^92^SENECA~
N1^ST^MidMichigan MC-MIDLAND^92^1098~
N3^2700 W. Sugnet Road~
N4^Midland^MI^48670~
HL^2^^O~
PRF^675050~
REF^OQ^1~
HL^3^^I~
LIN^15^VC^469973^IN^88910~
SN1^15^1^CA~PID^F^^^^BANDAGE ELASTIC 6INX10YD REB~
CTT^3~
SE^20^0001~
GE^1^15906~
IEA^1^000015906~

This is very helpful. I found a record that got kicked out by MA531 because missing PO. Also, this PO is not in the Lawson translated file POEDIANS.

ISA^00^ ^00^ ^ZZ^GHXNEO ^01^118796036 ^151210^0412^U^00200^000865719^0^P^|~GS^SH^085685709^118796036^20151210^0412^865719^X^004010~ST^856^0001~BSN^00^3972317^20151210^0412~HL^1^0^O~N1^ST^01RP^91^0002~HL^3^2^I~LIN^005^IN^800800^VC^CFS001561~SN1^005^50^EA^^50^EA~SLN^005^^I^50^EA^^^^VC^CFS001561~CTT^1~SE^10^0001~GE^1^865719~IEA^1^000865719~ISA^00^ ^00^ ^ZZ^GHXNEO ^01^118796036 ^151210^0412^U^00200^000865719^0^P^|~GS^SH^085685709^118796036^20151210^0412^865719^X^004010~ST^856^0001~BSN^00^3972317^20151210^0412~HL^2^1^O~PRF^1491590~HL^3^2^I~LIN^005^IN^800800^VC^CFS001561~SN1^005^50^EA^^50^EA~SLN^005^^I^50^EA^^^^VC^CFS001561~CTT^1~SE^10^0001~GE^1^865719~IEA^1^

So Lawson doesn't want to look at this because we are running an unsupported script: laws_inb_ghx_91

I upgraded EDI and I am trying to run ED502 to test and the output file POEDASN is being written to PROD instead of the TEST environments. Any ideas how to change it to write to prod?

I saw your other post that said you only have the production EDI translation engine. You can still direct ED502 to write to TEST. In the App File Path field in your trading partner setup (ED10) change /prod/law/env/edi/in/POEDIASN to /test/law/env/edi/in/POEDIASN. Make sure that directory exists first.

Yes I was able to direct Ed502 to write to test. I am trying to figure out what program/script could be plugging the company and vendor.

Jon, how are the values in ED40 and 856 notices related? I want to verify these values but I am not sure what I am looking for. We are still having issues with the company not being mapped/populated correctly in MA536CSV file.

ED502 translates the 856 using the substitution table records (ED40). For every account number you have set up with the vendor and will be transacting via EDI, you will need an inbound company ([tpid]_I_COMPANY) and inbound vendor ([tpid]_I_VENDOR) record, at the very least. This is true for any inbound EDI - 810, 832, 855 or 856. The trading partner id [tpid] is the one assigned in ED10 for the vendor.

For example:
List Name: XX_I_COMPANY
Lawson Value: 0010 (needs leading zeros if company less than 4 digits)
External Value: 12345678

List Name: XX_I_VENDOR
Lawson Value: 1234 (needs leading spaces if vendor number less than 9 digits)
External Value: 12345678

During translation, ED502 first looks at the ISA ID to identify the trading partner, then looks for the External Value in the ED40 records for that tpid that match the account number the vendor sends in N1^ST04. If matching records are found the company and vendor are written to the MA531CSV (for doc type 856).

John, you are the best! Thank you for taking time out of your busy schedule to help me understand and troubleshoot this problem. I had to prove to GHX that it was an issue on their end. The POEDIASN file was not formatted correctly because the 856 was missing segment N1ST.

Hi Chesca,

I hope you can give me some input. We are trying to set up this in our system.  do you mind sharing with me how is your MA531 process?  I want to leave MA531 as unreleased. but we want the receivers to be able to release those receipts from the handheld.  Any information I will really appreciate it.

Hi - you can leave the MA531s unreleased, but MSCM does not support seeing any receiver header not created in MSCM. I went 9 rounds with Infor on this in 2019 and my enhancement request was archived. If you put in a new request, I'll gladly "me too" it.

You can see the unreleased MA531s in Receiving Self Service if it helps.