Does the Base EDI Allow multiple documents within one outbound doc

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

We are right now working on an XML to EDI translations.

We receive say an 850 EDI document and it will spit out two 850 XML
documents.

Now if we have an XML document with one document it'll create the EDI
document without a problem. If we have two items to convert it won't work.
Below is a sample of the working and non-working documents. Anyone have ANY
idea? We're using the Base EDI adapter in BizTalk 2006.

Works
<EDI856Records>
<EDI856>
<ShipDocId>docid-01</ShipDocId>
<ShipDateCreated>2007-01-20</ShipDateCreated>
<ShipDate>2007-01-20</ShipDate>
<PO>12345</PO>
<ShipmentID>USPS</ShipmentID>
<ShipmentType>XRPSIUG</ShipmentType>
<ShipFromName>From</ShipFromName>
<ShipFromAddress1>Address 1</ShipFromAddress1>
<ShipFromAddress2></ShipFromAddress2>
<ShipFromCity>city</ShipFromCity>
<ShipFromState>IN</ShipFromState>
<ShipFromPostalCode>12345</ShipFromPostalCode>
<ShipFromCountryCode>US</ShipFromCountryCode>
<VendorNO>ABCD0001</VendorNO>
<ShipToName>Name</ShipToName>
<ShipToAddress1></ShipToAddress1>
<ShipToAddress2></ShipToAddress2>
<ShipToCity>city</ShipToCity>
<ShipToState>IN</ShipToState>
<ShipToPostalCode>12345</ShipToPostalCode>
<ShipToCountryCode>US</ShipToCountryCode>
<UniqueID>235456</UniqueID>
<LineItems>
<POLineItem>
<LineItem>00010</LineItem>
<Qty>10</Qty>
<PartNumber>M9643Z/A</PartNumber>
<VendorOrderNumber>0001972019</VendorOrderNumber>
<TrackingInfo>
<TrackingNumber>abcd</TrackingNumber>
<SerialNumber>1234</SerialNumber>
</TrackingInfo>
<TrackingInfo>
<TrackingNumber>efgh</TrackingNumber>
<SerialNumber>5678</SerialNumber>
</TrackingInfo>
</POLineItem>
</LineItems>
<Segments>1</Segments>
<TotalQty>10</TotalQty>
</EDI856>
</EDI856Records>

Doesn't Work - states the header doesn't exist
<EDI856Records>
<EDI856>
<ShipDocId>docid-01</ShipDocId>
<ShipDateCreated>2007-01-20</ShipDateCreated>
<ShipDate>2007-01-20</ShipDate>
<PO>12345</PO>
<ShipmentID>USPS</ShipmentID>
<ShipmentType>XRPSIUG</ShipmentType>
<ShipFromName>From</ShipFromName>
<ShipFromAddress1>Address 1</ShipFromAddress1>
<ShipFromAddress2></ShipFromAddress2>
<ShipFromCity>city</ShipFromCity>
<ShipFromState>IN</ShipFromState>
<ShipFromPostalCode>12345</ShipFromPostalCode>
<ShipFromCountryCode>US</ShipFromCountryCode>
<VendorNO>ABCD0001</VendorNO>
<ShipToName>Name</ShipToName>
<ShipToAddress1></ShipToAddress1>
<ShipToAddress2></ShipToAddress2>
<ShipToCity>city</ShipToCity>
<ShipToState>IN</ShipToState>
<ShipToPostalCode>12345</ShipToPostalCode>
<ShipToCountryCode>US</ShipToCountryCode>
<UniqueID>235456</UniqueID>
<LineItems>
<POLineItem>
<LineItem>00010</LineItem>
<Qty>10</Qty>
<PartNumber>M9643Z/A</PartNumber>
<VendorOrderNumber>0001972019</VendorOrderNumber>
<TrackingInfo>
<TrackingNumber>abcd</TrackingNumber>
<SerialNumber>1234</SerialNumber>
</TrackingInfo>
<TrackingInfo>
<TrackingNumber>efgh</TrackingNumber>
<SerialNumber>5678</SerialNumber>
</TrackingInfo>
</POLineItem>
</LineItems>
<Segments>1</Segments>
<TotalQty>10</TotalQty>
</EDI856>
<EDI856>
<ShipDocId>docid-01</ShipDocId>
<ShipDateCreated>2007-01-20</ShipDateCreated>
<ShipDate>2007-01-20</ShipDate>
<PO>12345</PO>
<ShipmentID>USPS</ShipmentID>
<ShipmentType>XRPSIUG</ShipmentType>
<ShipFromName>From</ShipFromName>
<ShipFromAddress1>Address 1</ShipFromAddress1>
<ShipFromAddress2></ShipFromAddress2>
<ShipFromCity>city</ShipFromCity>
<ShipFromState>IN</ShipFromState>
<ShipFromPostalCode>12345</ShipFromPostalCode>
<ShipFromCountryCode>US</ShipFromCountryCode>
<VendorNO>ABCD0001</VendorNO>
<ShipToName>Name</ShipToName>
<ShipToAddress1></ShipToAddress1>
<ShipToAddress2></ShipToAddress2>
<ShipToCity>city</ShipToCity>
<ShipToState>IN</ShipToState>
<ShipToPostalCode>12345</ShipToPostalCode>
<ShipToCountryCode>US</ShipToCountryCode>
<UniqueID>235456</UniqueID>
<LineItems>
<POLineItem>
<LineItem>00010</LineItem>
<Qty>10</Qty>
<PartNumber>M9643Z/A</PartNumber>
<VendorOrderNumber>0001972019</VendorOrderNumber>
<TrackingInfo>
<TrackingNumber>abcd</TrackingNumber>
<SerialNumber>1234</SerialNumber>
</TrackingInfo>
<TrackingInfo>
<TrackingNumber>efgh</TrackingNumber>
<SerialNumber>5678</SerialNumber>
</TrackingInfo>
</POLineItem>
</LineItems>
<Segments>1</Segments>
<TotalQty>10</TotalQty>
</EDI856>
</EDI856Records>

The error we're getting on trying to send two or more entries is

Event ID 24
Error enountered: ERROR (40), docnr 10049: The document has too many of
these segments. Contact the sender.source format: [101 0 XML 1.0] source
document: [856 00401DEFAULT X, Ship Notice/Manifest] source segment:
[data#15,def#70,name=HLLoopOrder] source element:
[def#1,elm#0,comp#0mname=PRF1] occ: [#2] max. occ [#1], (msgnr:1
segnr:15)(line:1 pos:603 filepos:883)
.

Relevant Pages

  • 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)
  • Problem with 997, BizTalk 06/Accelerator 3.3
    ... I'm currently using BizTalk 06 + Hipaa Accelerator 3.3. ... When I drop an EDI 837 in this port it ... correctly converts the file to an XML document. ...
    (microsoft.public.biztalk.general)
  • Webinar: Exploiting EDI and Flat Files in an XML World
    ... Attend a webinar event on how to modernize your EDI infrastructure and ... Exploiting EDI and Flat Files in an XML World ...
    (comp.text.xml)