The following is the information flow of a normal eBusiness exchange cycle:

The sender creates the application file using their own Business Application System. The file is then translated into an eBusiness standard format (EDI or XML), and transmitted either through a value added network or direct connection. The receiver takes the transaction set and translates the file from the eBusiness standard format to a file that is usable by their own Business Application System. Thus the cycle of eBusiness continues.

To exchange information using eBusiness, documents must be translated into a format that complies with an eBusiness standard. Mapping is the initial process that describes how each element of the original document, such as a purchase order or invoice, relates to an eBusiness transaction that complies with the standard being used. The translation software uses this mapping to translate the eBusiness transactions so they can be used by the receiving organization.

To receive or send electronic transactions, you will need the following equipment and software capabilities:

• A computer (PC, server or mainframe).
• Translation software to format your business information into a standard eBusiness format (EDI and/or XML) for transmission or interpretation.
• Communications hardware (a modem and telephone line or cable connection).
• Communications software to handle sending and receiving data.
• Coomunication channel to handle the last two communications items above that can either be:
  • A Value Added Network (VAN), or
  • Direct Connect Communications using either:
    • An FTP server or access to an FTP Server and Encryption Software, or
    • EDI over the Internet (EDI-INT [AS1, AS2 or AS3], or ebXML MS)
• Your Trading Partners information (profile) and all eBusiness transaction maps of the messages to be exchanged (sending to and/or receiving from).