Iam using webMethods 10.7 trading netwworks while generating the EDI file , I see the content generated as below in a single line without breakdown into separte segments in new line, is it something missing in my TPA settings or is it default setting in webMethods ?

current format:

ISA010000000000010000000000ZZABCDEFGHIJKLMNOZZ1234567890123451011271719U004000000034380P>~GSPO44051978009999999992010112717191421X004010VICS~ST850000000010~BEG00SA08292233294**20101127610385385~REFDP038~REFPSR~ITD14324546~DTM00220101214~PKGF68PALLETIZE SHIPMENT~PKGF66REGULAR~TD5A92P3**SEE XYZ RETAIL ROUTING GUIDE~

expected format:

ISA010000000000010000000000ZZABCDEFGHIJKLMNOZZ1234567890123451011271719U004000000034380P>~
GSPO44051978009999999992010112717191421X004010VICS~
ST850000000010~
BEG00SA08292233294**20101127610385385~
REFDP038~
REFPSR~
ITD14324546~
DTM00220101214~
PKGF68PALLETIZE SHIPMENT~
PKGF66REGULAR~
TD5A92P3**SEE XYZ RETAIL ROUTING GUIDE~

How did you receive the file ?
Can you include the code you used to convert the EDI record to text etc?
regards
John.

I have generated the edi content passing flat file doc and TPA values to wm.b2b.edi:convertToString. segment terminator : ~

EDI does not need to use CR/LF or LF as a segment delimiter. And quite often does not.

The ISA segment indicates what the segment delimiter is. In this case, looks to be ~

The EDI and EDITN components will parse this just fine. If you want to generate it with a different segment delimiter, use a combination of the TPA and services to set it to the desired char(s). Whatever you and the partner agree upon (or direct) in the implementation guide.

(It’s been quite a while since I’ve worked on EDI stuff, so my comments may be a bit off, but the gist is accurate).

@reamon, you are right but I think he was expecting line feeds and TN normally will respect the line separator.
John.

when I use “\n” - I get a new line feed , but when i use “~\n” I dont get a new line feed.

Sorry for the errant inference that the segment terminator can be multiple chars. It is a single character. The usual common terminator is ~

If you want LF as the terminator, and the partner will accept that, just use that.

There is a notion of “blocked” data where the EDI string is blocked at 80 chars, wrapping at 80 regardless of the where the line break lands in the segment. I don’t think you’re referring to that (and I don’t recall if the wM EDI components handle that directly) but wanted to check.