|
|
 |
Technical Bulletins |
 |
Communications Between Information Exchange Users and Internet
Data and Document Exchange Users
|
|
|
| |
Date posted: 17 April 2001
Customers affected: All Information Exchange
users who wish to exchange messages with Internet data and
document exchange users.
|
|
|
|
|
|
| |
This Technical Bulletin contains information about how
Information Exchange users can now exchange messages with
Internet data and document exchange users.
|
|
|
| |
| |
GXS
has been enhanced with a new commerce engine, Internet data
and document exchange. The Internet data and document exchange
commerce engine incorporates open Internet standards to provide
cost-effective, business-to-business document exchange services.
As an Information Exchange user, you can now exchange messages
with Internet data and document exchange users. This includes
exchanging EDI (X12 and EDIFACT), XML, binary, and plain text
messages with your trading partners who use Internet data
and document exchange to communicate. |
| |
|
|
| |
The
ability to exchange messages with your Internet data and document
exchange trading partners is easy. You simply need to know
their user information and their EDI ID. Their user information
consists of the Information Exchange system ID, account ID,
and user ID assigned to them when they registered with Internet
data and document exchange. The EDI ID is also be known as
their "company ID" within the Internet data and
document exchange service.
As an Internet data and document exchange user, you will
also need to register your Information Exchange user information
and EDI ID within Internet data and document exchange. Internet
data and document exchange users are responsible for registering
all of their trading partners. If you do not have an EDI
ID, a "company ID" will be assigned to your system
ID, account ID, and user ID during this registration process.
|
|
|
| |
|
|
| |
- Split billing -- The billing agreement between
Information Exchange users and Internet data and document
exchange users is "split." Split billing indicates
that the "sender" must pay the send charge,
and the "receiver" must pay the receive charge.
When exchanging data with your Internet data and document
exchange trading partners, you must set the payment levels
in your user profile or trading partner list to indicate
you are willing to pay both the "send" charge
as the sender, and the "receive" charge as the
receiver.
- CC Partner -- When an Internet data and document
exchange user is the partner in a carbon copy relationship,
that user cannot be requested to pay the carbon copy receive
charge or the carbon copy processing charge.
- CC Recipient -- When an Internet data and document
exchange user is the recipient in a carbon copy relationship,
that user must be requested to pay the carbon copy receive
charge. That user cannot be requested to pay the carbon
copy processing charge.
Please refer to the Information
Exchange Administration Services User's Guide
for detailed instructions regarding updating user profiles
and trading partner lists.
|
|
|
| |
|
|
| |
- Character set translation -- All messages transmitted
between Information Exchange and Internet data and document
exchange enter a character set translation process. This
translation process will:
- Convert ASCII characters to EBCDIC characters for
messages entering Information Exchange
- Convert EBCDIC characters to ASCII characters when
sending from Information Exchange
- Preventing character set translation and binary
data type -- To prevent character set translation
of messages that you send to your Internet data and document
exchange trading partner, you will need to mark the data
type as "binary." To prevent character set
translation of messages that you receive from your trading
partner, the trading partner will need to ensure the data
is marked as "binary."
- Exchanging X12 data -- When exchanging messages
containing X12 data, binary segments such as BIN, S4S,
and S3S cannot be used. The character set translation
process will corrupt any binary data contained in the
EDI envelope.
- Receiving EDIFACT interchanges -- When receiving
EDIFACT interchanges from your Internet data and document
exchange trading partner, the Common Data Header will
not contain the following items:
- EDI sender ID qualifier
- EDI sender ID
- EDI receiver ID qualifier
- EDI receiver ID
- EDI interchange control ID
- Exchanging XML documents -- XML data that you
send to or receive from your Internet data and document
exchange trading partner is treated as plain text.
- Message status within audit trails -- For messages
sent to an Internet data and document exchange trading
partner, the message status in the audit trail is set
to X (for transferred) when the Internet data and document
exchange service accepts the message. A message status
of X is not a confirmation that your Internet data and
document exchange trading partner has received the message.
|
|
|
|
Highlight