# Trading Network not recognizing segment terminator

**URL:** <https://techcommunity.softwareag.com/t/trading-network-not-recognizing-segment-terminator/108566>\
**Category:** Forum\
**Tags:** EDI\
**Created:** [May 27, 2005, 7:30am UTC](https://techcommunity.softwareag.com/t/trading-network-not-recognizing-segment-terminator/108566 "2005-05-27T07:30:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tuurit](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@tuurit](https://techcommunity.softwareag.com/u/tuurit)\
**Post date:** [May 27, 2005, 7:30am UTC](https://techcommunity.softwareag.com/t/trading-network-not-recognizing-segment-terminator/108566/1 "2005-05-27T07:30:08Z")

</div>

We are encountering an issue when processing EDI transactions from one of our trading partners.

The EDI document is submitted through the ‘Submit Test EDI Data’ option within the EDI Module of the Integration Server. When processing the document, it appears the internal webMethods processing determines the segment terminator from the ISA segment and places the value within a parameter called ‘record’ within the processing variable ‘@delimiters’.

One of our test cases involves an 850 purchase order document within the version 3020. The issue occurs when the segment terminator ‘µ’ is not identified and placed into the ‘record’ parameter. As a result, there is no segment terminator identified and the process ends with error.

The ISA segment is similar to the example below……

ISA~00~ ~00~ ~01~0123~01~ABCD~050317~0906~U~00200~900000049~0~P~\>µ  
GS~PO~0123~ABCD~050317~0906~900000049~X~003020µ  
ST~850~0001µ

---

<div class="post-metadata">

**Author:** ![Chris\_L](https://avatars.discourse-cdn.com/v4/letter/c/ba9def/32.png) [@Chris\_L](https://techcommunity.softwareag.com/u/Chris_L)\
**Post date:** [May 27, 2005, 8:46am UTC](https://techcommunity.softwareag.com/t/trading-network-not-recognizing-segment-terminator/108566/2 "2005-05-27T08:46:29Z")

</div>

Tim try changing your encoding value when submitting the document to TN.  
Try ISO88859-1.

HTH

---

<div class="post-metadata">

**Author:** ![Chris\_L](https://avatars.discourse-cdn.com/v4/letter/c/ba9def/32.png) [@Chris\_L](https://techcommunity.softwareag.com/u/Chris_L)\
**Post date:** [May 27, 2005, 8:45pm UTC](https://techcommunity.softwareag.com/t/trading-network-not-recognizing-segment-terminator/108566/3 "2005-05-27T20:45:17Z")

</div>

Tim,

It’s actually ISO8859-1.  
See this post.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:05pm UTC](https://techcommunity.softwareag.com/t/trading-network-not-recognizing-segment-terminator/108566/4 "2021-04-02T15:05:16Z")

</div>