|
|
 next
|
  Subject: No Topic
Author: Tony Lavinio
Date: 14 Aug 2006 02:28 PM
|
I've read over the SDQ file, and it is nothing more than a standard X12 850 Purchase order with some of the segments removed.
Specifically, the start of the file should include the prologue of ISA and GS segments, and the end of the file should have the epilogue of GE and IEA segments.
Also, before each BEG segment there should be an ST segment, and after each CTT segment there should be an SE segment.
Without some of those missing segments, no general-purpose adapter will be able to handle the file, and here's why:
The ISA segment tells what the element and segment separator characters will be. X12 doesn't supply default values, so that segment is needed for those.
The GS segment tells us which version of the transaction sets the message will include. Otherwise, we won't know how to decode the values, or even which validation rules to apply.
The SE segment tells us that the data is in the 850 Purchase Order transaction set. We can't just infer this from the presence of SDQ segments alone, since in addition to the 850, the 163, 180, 210, 212, 214, 223, 810, 830, 840, 843, 846, 852, 855, 856, 860, 862, 865, and 940 transaction sets also use SDQ segments.
Also, I could not find a reference to "SDQ Format" in any of the X12 documentation we have, nor could I find references in the members-only portions of the site. It's possible that it exists somewhere and is poorly indexed, but I could not find it.
In short, I think your vendor has created for you a file that includes some, but not all, of the X12 standard.
What are your options?
1. Have your vendor add the missing pieces so that they emit X12 EDI that is according to the published X12 standards, without omitting mandatory segments.
-or-
2. Use Convert-to-XML and build your own map. Since only a few segment types are used in this message, you'd only have to develop a few pattern matches.
Let us know if we can help further.
|
|
|
|
|
top