Ok - pet peeve time.
The GS segment does not have either a Sender ID or a Receiver ID. What it
has is an Application Sender's Code and an Application Receiver's Code.
These are very different. They are intended to be used for routing and
translation map identification. We are using these elements to determine
both routing and mapping. In some cases, we need this information to
determine which application gets the data.
In fact, I would say that the GS elements can not be standardized.
Bob
Martin Scholl
<mscholl@martins To: WEDi/SNIP ID & Routing
<[EMAIL PROTECTED]>
choll.com> cc:
Subject: Trading Partner ID
05/29/2002 01:11
PM
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
