Unwanted Delimiters in EDI segments

Guest · June 25, 2003, 9:51pm

Thanks for the quick response Manohar. No I am not supplying a sub-field delimiter. Here is how my data appears,
ISA00 * ZZE725 EZ25003015544774480898201315U0040100000000011P~:GSFAE725 E7250035544774482003062513150000000001X004010~ ST9978383~AK1IN21~AK28500219~AK5A~AK28100220~AK5A~
AK28100221~
AK5A~
AK28100222~
AK5A~
AK28100223~
AK5A~
AK28100224~
AK5A~
AK28100225~
AK5A~
AK28100226~
AK5A~
AK28100227~
AK5A~
AK28100228~
AK5A~
AK28100229~
AK5A~
AK28100230~
AK5A~
AK28100231~
AK5A~
AK28100232~
AK5A~
AK28100233~
AK5A~
AK9A151515~
SE348383~

reamon · June 25, 2003, 10:28pm

…1P~:GS… doesn’t look right.

It should be …1P*:~GS…

How is the ISA being created?

mrajanet · June 25, 2003, 11:17pm

You need to fill your sub-field delimiter also when you call your convertToString service and in your case, it looks like it is ‘:’ generated by system. As Rob pointed out, your ISA seems to be wrong.
The last 3 characters in your ISA just before ‘GS’ represents the delimiters field, subfield and segment respectively. These are mandatory.

Chris_L · August 9, 2003, 5:06am

FYI

IS 601 Fix17 fixes Unwanted Delimiters in EDI segments.