This blog describes Flow of Electronic Documents:
EDI Definition:
Electronic Data Interchange (EDI) is the exchange of business data from the computer of one enterprise to the computer of another enterprise using a standard format like PO, Invoices e.t.c. I.e Intercompany Electronic Exchange of Business Documents in a Standard Format. EDI is used with trading partners who are EDI capable and use EDI as a technology to improve the efficiency of their business. Not all trading partners are EDI capable or choose EDI as their technology of choice.
EDI Transactions from ANSI X12 Standard
EDI Transactions from EDIFACT Standard
Guidelines and Specs:
- The guidelines and specification documents are written to help the business partner accomplish EDI implementation as quickly and smoothly as possible. Take some time to review the implementation guide before you begin and if you have any questions along the way contact your Client Representative for clarifications.
- EXAMPLES: EDI 810 Implementation Guide Version 004010
- Monthly Market Invoice – With DTM segments
- Manual Billing or Settled Bill – Without DTM segments
EDI Translation:
- We need to be able to generate and convert EDI standard data, while keeping the data in machine readable format
- Provide a single application to reformat your data for electronic communication with many trading partners.
- How can we communicate with Trading Partners who do not have the same back-end applications and/or platforms?
- Most EDI Trading Partners utilize the service of a Value Added Network which has the capability to convert file formats
- If the file format is usable there still needs to be a common language between partners. EDI Standards are the common language. Along with the type of standard the version must be agreed upon as well. Continue to drive standards to realize savings & efficiencies.
.
EDI Interchanges, Functional Groups & Messages:
SEEBURGER – AS2 Adapter :
- AS2 (Applicability Statement 2) is a specification about how to transport data securely and reliably over the Internet. Security is achieved by using digital certificates and encryption.
- AS2 works by providing an “envelope” for the data, allowing it to be sent over the Internet (or another TCP/IP based network) using the HTTP protocol, which powers the World Wide Web.
- The receiving organization’s server then listens out for messages addressed to it. Like a call to a phone with no answering machine, the message will be missed if the receiver server is not available to take the call. So the receiving computer must be connected to the Internet at the time the document is sent.
Why AS2??? :
B2B commerce requires:
- Partners to use common data formats (these days, typically EDI or XML)
- Common network connectivity, so that a network path exists between trading partners
- Secure document delivery, so that only the intended recipient receives the message
- Secure document transmission, so that no one can read the document in transit
- Non-repudiation, so that the recipient can be sure that a document was actually sent by the claimed sender
- Reliable document status, so that a sender knows exactly what has happened to a document
- AS2 Standards contains all above
Implementation of AS2 Solution :
- Business need to make a number of decisions—some internal and some in conjunction with their trading partners before they begin sharing documents using AS2.
- AS2 be adopted easily by any organization if an organization can host a website 24x7, it's have the basic infrastructure for receiving documents from partners via AS2 without needing to know any technical specifics about their platforms
- Following points to be considered to set-up AS2 relationship.
1. Firewall Security
2. Digital Certificates
3. HTTP Protocol
4. Receipts
5. Encryption Algorithm
6. Signature Algorithm
- When establishing an AS2 communication with a Business Partner needs to decide whether to put the AS2 solution behind a firewall or in a “DMZ” (de-militarized zone) isolated from their own systems.
- Get a certificate (the public/private key) from company a third-party provider or generate your own certificate
- Agree whether to use HTTP or HTTPS (SSL-secured HTTP) as the transmission protocol
- Agree on a “receipt policy”
- Determine the encryption algorithm to be used
- Determine the signature algorithm to be used
Configure your AS2 Adapter with information about your trading partner:
a. URL for sending documents
b. Identity of partner
c. Signing method
d. Encryption method
e. Receipt method
f. Whether compression will be used
- Load the partner’s certificate (public key) into Trusted CA’s.
- Send a test document to confirm both systems have been configured correctly
- To have un-interrupted AS2 connectivity with trading partners need to manage
1. AS2 service must available to receive AS2 message when trading partner want to send the messages.
2. Keeping track of expiring certificates
3. Detecting problems when sending messages to partners
4. Detecting Security issues
This blog will help us to understand the flow of Electronic Documents and it will show us the clear picture.
Reference Links:
http://wiki.sdn.sap.com/wiki/display/bpxproj/EDI+with+PI
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/08/30/edi-seeburger-as2-oftp-adapters