Comments on: EDI Enveloping Part Three (The GS) http://www.theintegrationengineer.com/edi-enveloping-part-three-the-gs/?utm_source=rss&utm_medium=rss&utm_campaign=edi-enveloping-part-three-the-gs When it just has to work. Tue, 10 Jan 2012 15:48:21 +0000 hourly 1 http://wordpress.org/?v= By: venkataraman http://www.theintegrationengineer.com/edi-enveloping-part-three-the-gs/comment-page-1/#comment-3002 venkataraman Fri, 07 Jan 2011 05:23:31 +0000 http://www.theintegrationengineer.com/?p=47#comment-3002 So from your above comment do you mean that even in ISA it is not in practice to include the white spaces if the length is less than 15 characters. I have gone through the entire EDI primer. Actually I am new to this EDI and your blog was very useful to understand the basics. So from your above comment do you mean that even in ISA it is not in practice to include the white spaces if the length is less than 15 characters.

I have gone through the entire EDI primer. Actually I am new to this EDI and your blog was very useful to understand the basics.

]]> By: Roy http://www.theintegrationengineer.com/edi-enveloping-part-three-the-gs/comment-page-1/#comment-2997 Roy Thu, 06 Jan 2011 17:54:07 +0000 http://www.theintegrationengineer.com/?p=47#comment-2997 Right. The value of the ISA Identifiers for does not include the white space that may be left in the fixed width fields. At least I have never included it, and all of the EDI software that I have used didn't need me to enter the spaces to reach the 15 character size. In this way, the value of the GS and ISA identifiers can be the same value and there is no conflict based on the field size. It sounds like we are both on the same page. Let me know if there is still a question about any of these values. And thanks for your comments, quick or late it is nice to know people are getting value from the blog. Roy Right. The value of the ISA Identifiers for does not include the white space that may be left in the fixed width fields. At least I have never included it, and all of the EDI software that I have used didn’t need me to enter the spaces to reach the 15 character size.

In this way, the value of the GS and ISA identifiers can be the same value and there is no conflict based on the field size.

It sounds like we are both on the same page. Let me know if there is still a question about any of these values. And thanks for your comments, quick or late it is nice to know people are getting value from the blog.

Roy

]]> By: venkataraman http://www.theintegrationengineer.com/edi-enveloping-part-three-the-gs/comment-page-1/#comment-2988 venkataraman Thu, 06 Jan 2011 06:30:42 +0000 http://www.theintegrationengineer.com/?p=47#comment-2988 Thanks for the reply sir. Sorry for the late reply from my side. I understood that "in ISA06 if the sender id is not 15 characters we should represent the remaining fields with a blank space since the length is fixed as 15 characters, whereas in GS02 the length of the characters is not fixed and hence there is no need for the white space as we did in ISA06" Thanks for the reply sir. Sorry for the late reply from my side.
I understood that “in ISA06 if the sender id is not 15 characters we should represent the remaining fields with a blank space since the length is fixed as 15 characters, whereas in GS02 the length of the characters is not fixed and hence there is no need for the white space as we did in ISA06″

]]> By: Roy http://www.theintegrationengineer.com/edi-enveloping-part-three-the-gs/comment-page-1/#comment-2849 Roy Wed, 22 Dec 2010 22:23:47 +0000 http://www.theintegrationengineer.com/?p=47#comment-2849 The GS02 and GS03 elements are functional sender and receiver Identifiers. So they function the same way the ISA06 and ISA08 values. Unlike the ISA segment and elements, the GS does not have the fixed field size. Check out the ISA enveloping page to get a full explanation of this. So this mean that there should not be any white space around the Identifier value. The GS is the functional group, so it also does not need to be the same values found in the ISA segment. These can be functional values comparatively, in the ISA, we can say the document is from Vendor to Retailer, and the GS or functional can indicate it is from Account Receivable to Accounts Payable. Take a look at the ISA and GS enveloping pages and examine the way the sample segments look. If this doesn't help with the explanation, then let me know and I will try to be more clear. Hope this helps. The GS02 and GS03 elements are functional sender and receiver Identifiers. So they function the same way the ISA06 and ISA08 values.

Unlike the ISA segment and elements, the GS does not have the fixed field size. Check out the ISA enveloping page to get a full explanation of this. So this mean that there should not be any white space around the Identifier value.

The GS is the functional group, so it also does not need to be the same values found in the ISA segment. These can be functional values comparatively, in the ISA, we can say the document is from Vendor to Retailer, and the GS or functional can indicate it is from Account Receivable to Accounts Payable.

Take a look at the ISA and GS enveloping pages and examine the way the sample segments look. If this doesn’t help with the explanation, then let me know and I will try to be more clear.

Hope this helps.

]]> By: venkataraman http://www.theintegrationengineer.com/edi-enveloping-part-three-the-gs/comment-page-1/#comment-2832 venkataraman Mon, 20 Dec 2010 08:49:56 +0000 http://www.theintegrationengineer.com/?p=47#comment-2832 I cannot understand the following line in GS02 and GS03. If possible can u explain it "This element has the same restrictions on content, a 15 character alpha-numeric. But unlike the ISA sender, this one is not fixed in size.------>" This means that the delimiters fit around the value without including any white space"<-------" I cannot understand the following line in GS02 and GS03. If possible can u explain it
“This element has the same restrictions on content, a 15 character alpha-numeric. But unlike the ISA sender, this one is not fixed in size.——>” This means that the delimiters fit around the value without including any white space”<——-"

]]> By: Sherdy Balingit http://www.theintegrationengineer.com/edi-enveloping-part-three-the-gs/comment-page-1/#comment-1886 Sherdy Balingit Mon, 13 Sep 2010 03:03:20 +0000 http://www.theintegrationengineer.com/?p=47#comment-1886 Many people don’t understand what GS segment really means and how it works. Good thing they explained all the important information in this post. Many people don’t understand what GS segment really means and how it works. Good thing they explained all the important information in this post.

]]> By: How to hold Accountability of EDI Transactions with a Trading Partner | The Integration Engineer http://www.theintegrationengineer.com/edi-enveloping-part-three-the-gs/comment-page-1/#comment-1194 How to hold Accountability of EDI Transactions with a Trading Partner | The Integration Engineer Wed, 23 Jun 2010 16:24:33 +0000 http://www.theintegrationengineer.com/?p=47#comment-1194 [...] versed in the EDI enveloping levels you have already realized the  link of between the 997 and the GS level of the EDI envelope.  Also you may remember that you can request a 997 be returned for your transaction in the ISA [...] [...] versed in the EDI enveloping levels you have already realized the  link of between the 997 and the GS level of the EDI envelope.  Also you may remember that you can request a 997 be returned for your transaction in the ISA [...]

]]> By: ST EDI Enveloping | The Integration Engineer http://www.theintegrationengineer.com/edi-enveloping-part-three-the-gs/comment-page-1/#comment-1092 ST EDI Enveloping | The Integration Engineer Mon, 17 May 2010 04:16:18 +0000 http://www.theintegrationengineer.com/?p=47#comment-1092 [...] Looking for the  GS enveloping page? [...] [...] Looking for the  GS enveloping page? [...]

]]>