Problem with 997, BizTalk 06/Accelerator 3.3

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello all!

I'm currently using BizTalk 06 + Hipaa Accelerator 3.3. When
converting EDI documents to XML I'm having trouble with the 997 that
is generated.

I have a receive location setup. The pipeline on this location has
the HIPAA Disassembler. When I drop an EDI 837 in this port it
correctly converts the file to an XML document. It also creates a
997. However, the 997 is an XML document and its missing the ISA
nodes (ISA_InterchangeControlHeader) and GS Nodes
(GS_FunctionalGroupHeader). Is there a flag I need to set somewhere
to either generate the nodes or have the 997 created as EDI?

I also have this same setup on a BizTalk 2004 machine using HIPAA
Accelerator 3.0. With 04, I'm getting an EDI 997 generated. Did
something change in Accelerator 3.3?

Any help would be greatly appreciated!!

Thanks,
Jason
.



Relevant Pages

  • Meaning of message
    ... I am using Biztalk Server 2004 ... and the accelerator for HIPAA. ... The data being processed is an X12-834 edi ...
    (microsoft.public.biztalk.general)
  • Re: BizTalk EDI
    ... or Gentran that nornally translates EDI but is XML capable. ... translate XML to EDI and send via a VAN. ... and translate it to XML so I could pick it up with BizTalk. ...
    (microsoft.public.biztalk.general)
  • EDI, XML::Edifact, XML::LibXML::Iterator
    ... im EDI Format beschaeftigen. ... erhaeltlichen Spezifikationen fuer einige Nachrichttypen EDI in ... XML und XML in EDI konvertieren kann. ... Sind die Spezifikationen irgendwo in einem maschinenlesbaren ...
    (de.comp.lang.perl.misc)
  • Re: Need XSD for Base EDI Adatper - EDI 837
    ... The accelerator doesn't just provide schemas. ... The base EDI can't tell the difference between the 2000A, ... I'm working with a client that needs to process EDI 837 files. ...
    (microsoft.public.biztalk.general)
  • Does the Base EDI Allow multiple documents within one outbound doc
    ... We receive say an 850 EDI document and it will spit out two 850 XML ... <POLineItem> ... <TrackingInfo> ...
    (microsoft.public.biztalk.general)