Art Douglas reminded us of the trading partners "...who can't seem to
send different values in GS Receiver ID and ISA Receiver ID...."
My good friend, Rachel Foerster, who is usually not as serious as a
heart attack, rejoined with "There is nothing within the X12 standards
that requires that the value of the ISA Receiver ID and the GS Receiver
Code must be different. They can be the same identifier and this is
totally acceptable to the X12 standards." She then solemnly proceeded to
quote from the X12 scriptures.
Dear Rachel:
Lighten up. Shame on you. Art Douglas surely knows that the ISA and
GS receiver IDs can be identical - and they usually are. But in his
case, he wants his partner to send a *DIFFERENT* value in the two
receiver IDs - and nothing in the X12 standards requires that the value
of the ISA Receiver ID and the GS Receiver Code must be *IDENTICAL*,
either.
Sometimes the GS03 Application Receiver ID is simply used to identify
organizational departments for internal routing, whereas the ISA08
Receiver ID may be the DUNS of the organization itself. Other times,
the ISA receiver field is the mailbox ID on a particular VAN, and the GS
would contain a UCS comm ID. The two receiver IDs have nothing much to
do with each other, except by custom, VAN requirements and trading
partner agreement.
Speaking of the ISA, does anyone want to ask if the ISA is a fixed
length record so we can see if that guy who always talks about the
negative control numbers comes out of the woodwork?
William J. Kammerer
FORESIGHT Corp.
4950 Blazer Memorial Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600
Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"Commerce for a New World"
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
