EDI docs are just a stream of bytes.
The ISA segment appears first and is a fixed length (106 bytes + 1)
segment, all fields are required.
The characters at select positions of the stream determine what separators
are looked for in the rest of the stream:
pos 4 - element separator
pos 106 - sub-element separator
pos 107 - segment separator
since the segment separator is a single byte, you can't really ever have
CR/LR as a segment separator. You often see just LF in Linux/Unix based
documents. Some EDI mappers can strip "illegal" CR/LF, but it's not a wise
idea to count on that.
I usually see the tilda ~, use as a segment separator.
When generating EDI, you should be able to specify what separators to use,
just in case the data/partner requires a change from your company's default.
When reading EDI, you have to examine the first 107 bytes, and store the
separators being used for that document.
On Tue, Aug 12, 2014 at 12:26 PM, Jim Franz <franz9000@xxxxxxxxx> wrote:
This has been the issue - my specs and interaction with their help(not)desk
- these answers:
see the X12.org requirements. See DISA.org , etc
No indication of wrapped, unwrapped. No specs except the values required
for the detailed data.
No specs for the standard ISA and GS segments.
Their assumption is we all have an EDI software package that does this for
us (and we don't).
I'm already doing edi with Federal gov (medicare) with no problems, but
this is a state agency who outsourced their edi to a large US insurance
I ask questions and get vague answers days later.
No docs on "file format".
Last test returned an email with this exact text:
Invalid file has been received, please correct and resend the file.
Reason: Index was out of range. Must be non-negative and less than the size
of the collection. Parameter name: index
There is nothing in the file called index...
On Tue, Aug 12, 2014 at 12:05 PM, Nathan Andelin <nandelin@xxxxxxxxx>
when I write the last segment, should it have a CRLF or some kind of
Wouldn't that depend on a spec from your EDI partner?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives