Here's the discussion of the GS02, etc. (copied & pasted) from the X12 4010 book X12.59, section 6.4.2 (Internal Identification--Functional Group Level):
Internal identification addressing information is carried as codes in the Application Sender's Code and
the Application Receiver's Code control elements in the functional group header (GS segment). The
values for these codes can be used for any routing internal to the organization, or any other identification
purpose providing further information for trading partner record keeping.
 
There is no universal meaning to the data content of instances of those codes. For example, if an
instance of the Application Receiver's Code contains the value "9876543", the internal identification
could be a telephone number, a department (e.g., accounts payable), etc.
 
Because there is no universal meaning for these values, they can only be used for internal identification
by the organization that understands their meaning. Meaning for particular values can be established by
an individual organization, by trading partner agreements, or by industry groups.
 
Because of the internal nature of functional group addressing, there is no implied semantic relationship
between instances of addressing at this level and that of the interchange and communications exchange
levels (which are external routing levels).
 
Similarly, because this information has no universal meaning, there is no implied semantic relationship
between instances of addressing at this level and that at the business application level (i.e., information
within transaction sets).
 
Such relationships, if defined by trading partner agreements or by industry groups, would be outside the
scope of the ASC X12 standards.
Sounds to me like it's up to you and your trading partner(s) and will depend upon what the business and/or audit needs might be.  Obviously the easiest thing to do would be to make them match, which is fine if you don't need anything else from them.
 
Hope that's helpful.
 
Best regards,
Bill Chessman
Peregrine Systems, Inc.
-----Original Message-----
From: Martin Scholl [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 10:12 AM
To: WEDi/SNIP ID & Routing
Subject: Trading Partner ID

I have a conceptual problem with the different Sender and Receiver IDs.
 
If I receive a transaction, I key the trading partner to the ISA_06 element.  Under this number I record the transmission mode, like ftp or email or dial-up, passwords etc.
Then I have another Sender ID in the GS_02.  Should this be the same as ISA_06? The IG recommends to define this in the trading partner agreement.  My feeling would be to make these numbers identical or could they identify different departments within the trading partner's organization? are they subordinate to ISA_06?
Then in the 837 I also have this pesky 1000A loop with another set of Sender IDs.  Again, I would intuitively think that this could be the same as ISA_06 and GS_02.
 
For me the issue is: What do I use as a unique key to store trading partner rules and information under?
What do others in the field do?
 
Martin Scholl
Scholl Consulting Group, Inc.
301-924-5537 Tel
301-570-0139 Fax
[EMAIL PROTECTED]
www.SchollConsulting.com

Reply via email to