# Unwanted Delimiters in EDI segments

**URL:** <https://techcommunity.softwareag.com/t/unwanted-delimiters-in-edi-segments/108328>\
**Category:** Forum\
**Tags:** EDI\
**Created:** [June 3, 2003, 10:16pm UTC](https://techcommunity.softwareag.com/t/unwanted-delimiters-in-edi-segments/108328 "2003-06-03T22:16:15Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![Guest](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/guest/32/75_2.png) [@Guest](https://techcommunity.softwareag.com/u/Guest)\
**Post date:** [June 25, 2003, 9:51pm UTC](https://techcommunity.softwareag.com/t/unwanted-delimiters-in-edi-segments/108328/21 "2003-06-25T21:51:27Z")

</div>

Thanks for the quick response Manohar. No I am not supplying a sub-field delimiter. Here is how my data appears,  
ISA_00_ \* _ZZ_E725 EZ25003_01_554477448_089820_1315_U_00401_0000000001_1_P~:GS_FA_E725 E725003_554477448_20030625_1315_0000000001_X_004010~ ST_997_8383~AK1_IN_21~AK2_850_0219~AK5_A~AK2_810_0220~AK5_A~  
AK2_810_0221~  
AK5_A~  
AK2_810_0222~  
AK5_A~  
AK2_810_0223~  
AK5_A~  
AK2_810_0224~  
AK5_A~  
AK2_810_0225~  
AK5_A~  
AK2_810_0226~  
AK5_A~  
AK2_810_0227~  
AK5_A~  
AK2_810_0228~  
AK5_A~  
AK2_810_0229~  
AK5_A~  
AK2_810_0230~  
AK5_A~  
AK2_810_0231~  
AK5_A~  
AK2_810_0232~  
AK5_A~  
AK2_810_0233~  
AK5_A~  
AK9_A_15_15_15~  
SE_34_8383~

---

<div class="post-metadata">

**Author:** ![reamon](https://avatars.discourse-cdn.com/v4/letter/r/b77776/32.png) [@reamon](https://techcommunity.softwareag.com/u/reamon)\
**Post date:** [June 25, 2003, 10:28pm UTC](https://techcommunity.softwareag.com/t/unwanted-delimiters-in-edi-segments/108328/22 "2003-06-25T22:28:10Z")

</div>

…_1_P~:GS… doesn’t look right.

It should be …_1_P\*:~GS…

How is the ISA being created?

---

<div class="post-metadata">

**Author:** ![mrajanet](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@mrajanet](https://techcommunity.softwareag.com/u/mrajanet)\
**Post date:** [June 25, 2003, 11:17pm UTC](https://techcommunity.softwareag.com/t/unwanted-delimiters-in-edi-segments/108328/23 "2003-06-25T23:17:28Z")

</div>

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.

---

<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:** [August 9, 2003, 5:06am UTC](https://techcommunity.softwareag.com/t/unwanted-delimiters-in-edi-segments/108328/24 "2003-08-09T05:06:30Z")

</div>

FYI

IS 601 Fix17 fixes Unwanted Delimiters in EDI segments.

---

<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/unwanted-delimiters-in-edi-segments/108328/25 "2021-04-02T15:05:10Z")

</div>



[Previous page](https://techcommunity.softwareag.com/t/unwanted-delimiters-in-edi-segments/108328.md?page=1)