SoftwareAG webMethods EDI Introduction
- 1. 1 What is EDI? Electronic Data Interchange (EDI) is the framework for automated exchange of crucial trading information in standard format between business partners. Orders, Invoices, Quotes are a few examples of EDI documents exchanged between trading partners. The standards for these business documents are defined by standards bodies such as ANSI, UN/EDIFACT EDI has existed at least since the early 70s, and there are many EDI standards (including X12, EDIFACT, ODETTE, etc.), some of which address the needs of specific industries or regions
- 2. 2 EDI
- 3. 3 Result of EDI Paperless Reduce re-entry labor cost Less human errors Less process time Less delivery time Less space for paper stock Less computer software and hardware
- 4. 4 EDI Sample (ANSI X12 Standard)
- 5. 5 Standard ANSI X12 - Message 850 - Purchase Order - to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services 856 - Ship Notice/Manifest - to list the contents of a shipment of goods as well as additional information relating to the shipment such as order information, product description, physical characteristics, type of packaging, marking, carrier information and configuration of goods within the transportation equipment 860 - Purchase Order Change Request - Buyer Initiated - to provide the information required for the customary and established business and industry practice relative to a purchase order change. 861 - Receiving Advice/Acceptance Certificate - to provide for customary and established business and industry practice relative to the notification of receipt or formal acceptance of goods and services. 862 - Shipping Schedule - used by a customer to convey precise shipping schedule requirements to a supplier and is intended to supplement the planning schedule transaction set (830). 863 - Report of Test Results - to transmit the results of tests performed to satisfy a specified product or process requirement 865 - Purchase Order Change Request/Acknowledgment - Seller Initiated - to convey acceptance or rejection of changes to a previously submitted purchase order by the seller or to notify the buyer of changes initiated by the seller to a previously submitted purchase order by the seller. 996 - File Transfer - to transmit file information in formats agreed to by the sending and receiving parties. 997 - Functional Acknowledgment
- 6. 6 Standard ANSI X12 - Message 810 - Invoice - provide for customary and established business and industry practice relative to the billing for goods and services provided. 820 - Payment Order/Remittance Advice - to make a payment and send a remittance advice. This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system. 824 - Application Advice - to provide the ability to report the results of an application system's data content edits of transaction sets. The results of editing transaction sets can be reported at the functional group and transaction set level in either coded or free-form format. It is designed to accomodate the business need of reporting the acceptance, rejection or acceptance with change of any transaction set. 830 - Planning Schedule with Release Capability - The planning schedule transaction may be used in various ways or in a combination of ways such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources such as labor or material; (3) a forecast that is also used as an order release mechanism containing such elements as resource authorizations period-to-date cumulative quantities and specific ship/delivery patterns for requirements that have been represented in ``buckets '' such as weekly monthly or quarterly.
- 7. 7 Interchange The outermost level is the INTERCHANGE Envelope, defined by ISA and IEA segments. Used to Identify the SENDER and RECEIVER of the EDI document. It Contains Interchange Control Numbers and Functional Group Counts Time/Date stamp same like the GS but does not include the century Data Element Separators, Sub-Element Separators, and Segment Terminators THE ISA IS A FIXED LENGTH SEGMENT
- 8. 8 Group
- 9. 9Transaction Set A single business document is defined by a Transaction Set Ship Notice, Invoice, Purchase Order are examples of Transaction Set Each set of transaction data is identified by a three digit code number Purchase Order – 850 , Invoice – 810 , Ship Notice – 856
- 11. 11 EDIFACT Sample UNB+UNOA:1+UNTRAD:ZZ+GENRLIMPORT- MEXICO:ZZ+860728:1055+148++MYKEY’ UNG+INVOIC+EC:21+M.THOMAS+871104:1400+GM21+OD+2’ UNH+865121+INVOIC:2’ BIN+1510+860728+CA’ PAR+SE+UNIVERSAL TRADING CY:PO BOX 2110:1202:GENEVE:SWITZERLAND’ PAR+BU+GENERAL IMPORT:CALLE PRINCIPAL 15:MEXICO CITY:MEXICO’ CTA+AR+:M.HELEN+6515308:TE’ CUX+II+CHF’ UNS+D’ LIT+25:KG+++++2500++CH+12 3456:BP’ LIT+16:KG+++++3000CH+654321:BP’ LIT+30:KG+++++4050++FR+665544:BP’ UNS+S’TIA+2550’ UNT+1+861521’ UNE+1+GM21’ UNZ+1+1480’
- 13. 13 Overview of EDI Module The webMethods EDI Module (EDI Module) enables business partners to exchange EDI documents within and across the extended enterprise, providing comprehensive EDI support. When you use the EDI Module along with other webMethods components, you can extend its capabilities. Integration Server: Parse, convert, format, and validate EDI documents Process EDI documents containing multiple interchanges/groups/transactions with multiple versions Transport EDI documents using the FTP, HTTP, and HTTPS protocols Trading Networks: Maintain information about your trading partners that exchange EDI documents Send EDI documents to and retrieve EDI documents from trading partners. Process EDI documents using the features of Trading Networks (e.g., processing rules) Batch the sending of EDI documents rather than sending them in real time Automatically generate functional acknowledgments (FA) for inbound documents Reconcile EDI documents with their corresponding functional acknowledgements (FAs) to create FA reconciliation reports View EDI documents that have passed through your system
- 14. 14 Overview of EDI Module – Continued.. webMethods Designer: You can use webMethods Designer to create EDI-based business process models. Trading Networks passes documents to process management to perform the actions you specify in your process models. You then can monitor the progress of your business process using webMethods MWS.
- 15. 15 Architecture When you install the EDI Module, two packages are installed into the Integration Server the WmEDI package and the WmEDIforTN package. Note: A package named WmEDIsamples contains sample EDI flow services, mappings, and IS document types that demonstrate how to use the EDI Module and webMethods Developer to execute typical EDI processing scenarios
- 16. 16 EDI Solution – Only with Integration Server When you use webMethods EDI Module (EDI Module) without other webMethods’ components, you are using only the WmEDI package of the EDI Module. There are two aspects to your EDI solution: How to send EDI documents to the Integration Server and how you process them; that is, inbound processing How you form EDI documents from internal-format documents (e.g., documents from back-end systems) and send the EDI documents outbound; that is, outbound processing
- 17. 17 Processing of Inbound EDI Documents Clients that send EDI documents to the Integration Server and services that process the inbound EDI document The EDI documents are documents in standard EDI format, such as ANSI X12, UCS, VICS, UN/EDIFACT, ODETTE, or EANCOM
- 18. 18Service to Process the Inbound EDI Document
- 19. 19 Forming EDI Documents to Send Outbound
- 20. 20 Using the EDI Module with Trading Networks
- 21. 21 Initial Processing of the EDI Recognizer
- 24. 24 Main Services The wm.b2b.edi:convertToValues service to convert an EDI to an IS document The wm.b2b.edi:convertToString service to convert an IS document to an EDI document