|
From: John H. <jo...@zo...> - 2004-04-14 13:50:51
|
Darren, The code dynamically identifies the seperators used in the source data file. Specifically, it gets the element seperator from the fourth character, the segment seperator from the 106th character, and the sub-element seperator from the 105th character. I have assumed that a x12 document creator will use seperators from the basic or extended character sets, but it may be possible to use seperators from the basic or extended control sets. I will have to test that. On Wed, Apr 14, 2004 at 08:51:34AM -0400, Darren Hartford wrote: > Just an FYI, changing the special element seperator characters to "*",":"= , and "~" seemed to have corrected the issue. However, my data normally co= ntains these characters (which I had to change for this test case), so I wo= uld like to add these as element seperators. Where should I look in the co= de for these seperator identifiers? > -D >=20 > > -----Original Message----- > > From: Darren Hartford =20 > > Sent: Monday, April 12, 2004 11:23 AM > > To: 'pyx...@li...' > > Subject: 835 file - convert using pyx12?=20 > >=20 > > Hey all, > > Finally, a simple, open-source tool to take care of HIPAA conversions, = yay!!! =3D) > >=20 > > I'm gonna play ignorant here a little bit - I have files from providers= that are in 835 format. Whether this is an EDI or an X12N I'm not sure on = (or if there is a difference). > >=20 > > When I run the x12xml/x12html/etc. I get an error along the lines of: > > "ERROR x12n_document 84 This does not look like a X12 data file" > >=20 > > Obviously, I can't share the file, but the beginning of the file looks = like this: > >=20 > > ISA=1C00=1C =1C00=1C=20 > >=20 > > Is this something pyx12 can convert? > > John mentioned the problem may be related to the element seperator(s), = so attached is a small part of the file. > > TIA for any help! > > -D > >=20 > > << File: 835edi.txt >>=20 --=20 John Holland=20 jo...@zo... http://www.zoner.org |
