<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: EDI Delimiters</title>
	<atom:link href="http://www.theintegrationengineer.com/edi-delimiters/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theintegrationengineer.com/edi-delimiters/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=edi-delimiters</link>
	<description>When it just has to work.</description>
	<lastBuildDate>Tue, 10 Jan 2012 15:48:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Roy</title>
		<link>http://www.theintegrationengineer.com/edi-delimiters/comment-page-1/#comment-8505</link>
		<dc:creator>Roy</dc:creator>
		<pubDate>Wed, 05 Oct 2011 21:09:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.theintegrationengineer.com/?p=24#comment-8505</guid>
		<description>Cevin,

Thanks, and my condolences for having to work in MS -Access.  If you are familiar with the 850 format, the 855 should be pretty straight forward.

But the question as I understand is can a document use a different delimiter set in some segments?  The answer to this question is a resounding no.  The only delimiter characters allowed in the EDI file (ISA to IEA) are defined at the end of the ISA segment .  (Characters 104, 105, and 106 of the ISA)

Also, the (`) character is not a hyphen.  I have always called it a &quot;back tick&quot; but there may be another name for it.

It does sound like a cut and past error.  Or we could call it laziness. In either case, when you actually work with the real data it needs to comply with the delimiters in the ISA.

Thanks for the question.  Please let me know if you run into any other odd information.

Roy</description>
		<content:encoded><![CDATA[<p>Cevin,</p>
<p>Thanks, and my condolences for having to work in MS -Access.  If you are familiar with the 850 format, the 855 should be pretty straight forward.</p>
<p>But the question as I understand is can a document use a different delimiter set in some segments?  The answer to this question is a resounding no.  The only delimiter characters allowed in the EDI file (ISA to IEA) are defined at the end of the ISA segment .  (Characters 104, 105, and 106 of the ISA)</p>
<p>Also, the (`) character is not a hyphen.  I have always called it a &#8220;back tick&#8221; but there may be another name for it.</p>
<p>It does sound like a cut and past error.  Or we could call it laziness. In either case, when you actually work with the real data it needs to comply with the delimiters in the ISA.</p>
<p>Thanks for the question.  Please let me know if you run into any other odd information.</p>
<p>Roy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cevin</title>
		<link>http://www.theintegrationengineer.com/edi-delimiters/comment-page-1/#comment-8500</link>
		<dc:creator>Cevin</dc:creator>
		<pubDate>Wed, 05 Oct 2011 19:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.theintegrationengineer.com/?p=24#comment-8500</guid>
		<description>Roy,
First off, AWESOME site.

I&#039;m working on overhauling an MS-Access database I built over a year ago that has been generating the 856 ship notice for uploading to our trading partner.  A new customer wants us to reply to their 850 purchase orders with 855 PO Acknowledgements, so it&#039;s back to the drawing board.  I&#039;m still waiting on our interchange to get straightened out so I can look at an actual file, but their documentation examples use different delimiters, and in some cases, different delimiters in the same document.

For example, their 850 uses the * (asterisk) in the ST, BEG, REF, PER, TD5, PO1, CTT, and SE lines, but uses a ` (backwards hyphen?) in the N1, N3, N4, SCH, and MSG segments.

That&#039;s impossible, right?  Please confirm for me that this is probably a cut-and-paste error from someone responsible for writing a manual, not writing code, and has no idea what they&#039;re writing.

Thanks,
Cevin</description>
		<content:encoded><![CDATA[<p>Roy,<br />
First off, AWESOME site.</p>
<p>I&#8217;m working on overhauling an MS-Access database I built over a year ago that has been generating the 856 ship notice for uploading to our trading partner.  A new customer wants us to reply to their 850 purchase orders with 855 PO Acknowledgements, so it&#8217;s back to the drawing board.  I&#8217;m still waiting on our interchange to get straightened out so I can look at an actual file, but their documentation examples use different delimiters, and in some cases, different delimiters in the same document.</p>
<p>For example, their 850 uses the * (asterisk) in the ST, BEG, REF, PER, TD5, PO1, CTT, and SE lines, but uses a ` (backwards hyphen?) in the N1, N3, N4, SCH, and MSG segments.</p>
<p>That&#8217;s impossible, right?  Please confirm for me that this is probably a cut-and-paste error from someone responsible for writing a manual, not writing code, and has no idea what they&#8217;re writing.</p>
<p>Thanks,<br />
Cevin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy</title>
		<link>http://www.theintegrationengineer.com/edi-delimiters/comment-page-1/#comment-651</link>
		<dc:creator>Roy</dc:creator>
		<pubDate>Mon, 21 Dec 2009 17:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.theintegrationengineer.com/?p=24#comment-651</guid>
		<description>Charles,

Some EDI software has a default recommended delimiter set that it preferes to use.  In that case I would include those in my specification.

If your EDI application does not care or have a prefferenece, I recommend using the ^&#124;~ combination, or ^ for the element delimieter, &#124; for the sub-element, and ~ for the segment delimiter.

You can find an example and more discussion on this at my &lt;a href=&quot;http://www.theintegrationengineer.com/edi-enveloping-part-two-the-isa/&quot;&gt;EDI Enveloping post about the ISA.&lt;/a&gt;

Let me know if there are more questions, please let me know.

Roy</description>
		<content:encoded><![CDATA[<p>Charles,</p>
<p>Some EDI software has a default recommended delimiter set that it preferes to use.  In that case I would include those in my specification.</p>
<p>If your EDI application does not care or have a prefferenece, I recommend using the ^|~ combination, or ^ for the element delimieter, | for the sub-element, and ~ for the segment delimiter.</p>
<p>You can find an example and more discussion on this at my <a href="http://www.theintegrationengineer.com/edi-enveloping-part-two-the-isa/">EDI Enveloping post about the ISA.</a></p>
<p>Let me know if there are more questions, please let me know.</p>
<p>Roy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles</title>
		<link>http://www.theintegrationengineer.com/edi-delimiters/comment-page-1/#comment-646</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Fri, 18 Dec 2009 16:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.theintegrationengineer.com/?p=24#comment-646</guid>
		<description>Hi,

Where can I find those recommended delimeters you refer to?

Included with my EDI Usage Specification are a set of recommended delimiters.  I set my transformer to use them as default, and encourage my trading partners to do the same.

I searched the site without success...

Thanks,

CAL</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Where can I find those recommended delimeters you refer to?</p>
<p>Included with my EDI Usage Specification are a set of recommended delimiters.  I set my transformer to use them as default, and encourage my trading partners to do the same.</p>
<p>I searched the site without success&#8230;</p>
<p>Thanks,</p>
<p>CAL</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Database Caching using disk: basic

Served from: www.theintegrationengineer.com @ 2012-02-05 11:43:15 -->
