Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

EDI Unlisted Document version - Translation Failed

Status
Not open for further replies.

CodeDigger

Programmer
Jan 7, 2005
11
CA
I have an EDI file Document 996 for Format version 3020 (which is not supported by the BASE EDI Adapter out of the box:

[tt]
ISA*00* *00* *01*043073964 *12*6082744330 *20051220*0604*U*00302*000003522*0*P*$
GS*CG*043073964*6082744330**0604*50006*X*003020
ST*996*500060001
BGF*855*OQ*96243
K3*7997100
SE*4*500060001
GE*1*50006
IEA*1*000003522
[/tt]

Note I am not using Covast. When I use the Base EDI Adapter to pick up this instance it fails in the translation from EDI to XML phase. I keep getting the error from HAT – Error(30) Translation failed.

[tt]
Error encountered: ERROR (30), interchangenr 10012 :
The document does not contain a required element. Contact the sender.source format: [5 00405 ,X12-4050]
source document: [(unknown)]
source segment: [data#0,def#1,tag=ISA ,name=Interchange Control Header]
source element: [def#1,elm#1,comp#0,tag=9001,name=Authorization information qualifier], (msgnr:0 segnr:0)(line:1 pos:0 filepos:3)


Error encountered: ERROR (30), interchangenr 10012 :
The document does not contain a required element. Contact the sender.source format: [5 00405 ,X12-4050]
source document: [(unknown)]
source segment: [data#0,def#1,tag=ISA ,name=Interchange Control Header]
source element: [def#3,elm#3,comp#0,tag=9003,name=Security information qualifier], (msgnr:0 segnr:0)(line:1 pos:0 filepos:3)
[/tt]

And so on - note only the elm# and the name keeps updated to reflect all 16 expected segments of the ISA interchange header. But as you can see from the sample the ISA interchange header is all there. Also note the Format version is 4050 and not the 3020 as it should be. And yes I have followed all the points in KB article
(Set "Accept all unlisted documents" to "Yes" in the Receive Location configuration)

This error is obviously happening during the translation phase - when the EDI document is being translated into an XML Message. Any ideas?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top