TDM slide deck

The following slides are intended to be for a more technical audience (Solutions Sales Specialist,

MCS etc.)

<presenter’s name> – <company name>

EDI and AS2 Solutions

for

2004

Where does EDI fit in BizTalk Server?

Architecture

Stack Chart of EDI Functionality

What is needed to “do” EDI?

– EDI Auditing, managing & monitoring

– End-to-End acknowledgements

– EDI formats and document types support

– Control numbering

– Syntactic and Semantic validation

– Batching facilities

– Communication Protocols

Auditing

Acknowledgements

Formats and Types

Control Numbering

Validation

Batching

Communication

Native EDI – What Can It Do?

Auditing

Acknowledgements

Formats and Types

Control Numbering

Validation

Batching

Communication

Auditing

Acknowledgements

Formats and Types

Control Numbering

Validation

Batching

Communication

Native EDI EDI Accelerator

Native EDI – What Can It Do?

BizTalk Native EDI will suffice when:– You only use a limited number of standard X12 or EDIFACT messages

– Don’t need batching

– You don’t need VAN or other EDI specific communications

BizTalk “out of the box versus Covast EDI Accelerator summary

   

Feature BTS 2004 EDI out of the box Covast EDI Accelerator

ANSI X 12 versions and transaction sets

Specific versions and documents supported:2040: 810, 832, 846, 850, 855, 856, 861, 864, 867, 9973010: 810, 832, 846, 850, 852, 855, 856, 861, 864, 867, 9973060: 810, 832, 846, 850, 852, 855, 856, 861, 864, 867, 940, 944, 9974010: 810, 832, 846, 850, 852, 855, 856, 861, 864, 867, 940, 944, 997

ALL versions and transaction set of ANSI X 12 (as well as subsets such as VICS, UCS, WINS)

UN/EDIFACTversions and messages

Specific versions and documents supported:D93A: DESADV, INVOIC, INRPT, ORDERS, ORDRSP, PARTIN, PAYEXT, PRICAT, SLSRPTD95A: APERAK, DESADV, INVOIC, INVRPT, ORDERS, ORDRSP, PARTIN, PAYEXT, PRICAT, SLSRPTD95B: APERAK, DESADV, INVOIC, INVRPT, ORDERS, ORDRSP, PARTIN, PAYEXT, PRICAT, SLSRPTD97B: APERAK, DESADV, INVOIC, INVRPT, ORDERS, ORDRSP, PARTIN, PAYEXT, PRICAT, PRODAT, RECADV, SLSRPTD98A: APREAK, CONTRL, DESADV, INVOIC, INVRPT, ORDERS, ORDRSP, PARTIN, PAYEXT, PRICAT, PRODAT, RECADV, SLSRPTD98B: APREAK, CONTRL, DESADV, INVOIC, INVRPT, ORDERS, ORDRSP, PARTIN, PAYEXT, PRICAT, PRODAT, RECADV, SLSRPT

ALL version and messages of UN/EDIFACT + standards used with Europe such as EANCOM, TRADACOM, ODETTE, VDA, GENCOD

Functional Acknowledgments Not supported

Batching Not supported  

VAN –Communication support

Not supported

Validation Very limited validation Extensive validation according to the standard

EDI Accelerator - Communication

Value Added Networks– Atlas400, BusinessMail– GXS EDI*Express– IBM Information Exchange– ICC.Net– Inovis– Kleinschmidt– SITA– Sterling Commerce– GXS Tradanet– Transettlements– Uniplus 400 Net– Worldcom EDI*Net

Peer-to-Peer– AS2– OFTP– FTP– POP3/SMTP

– MSMQ– IBM MQSeries– HTTP– HTTP/s

EDI Accelerator - Batching

EDI Interchanges consist of multiple documents or even document types to be sent to one recipient– Cut communication costs

– Group logical batches of documents

Batching can be configured on the Send Port level from within the BizTalk Explorer

It can also be influenced from within a BizTalk Mapping

EDI Accelerator - Validation

All EDI Interchanges and Messages are validated agains the specification stored in the EDI Repository. The following is validated:– Syntax

– Mandatory elements and composites

– Segment repetition

– Separators

– Maximum and Minimum lengths

– Types

– Code sets

– Semantics (inter-segment and element relationships)

EDI Accelerator - Validation

EDI Accelerator – Control Numbers

Each EDI transaction is treated as a unique business document exchanged with a Trading Partner

This means that the transactions need unique identifiers

Control numbers can be generated per type of message and/or per Trading Partner

They can also be Transactional – meaning that no gaps will occur in the numbers and therefore the remote party can check if ALL transactions have been received

Inbound duplicates are NOT allowed

EDI Accelerator – Formats and Types

Supported formats:– X12 (U.S.)– VICS (U.S. General Merchandise Retail)– WINS (U.S. Warehousing)– UCS (U.S. Grocery Retail)– EDIFACT (Worldwide)– EANCOM (European Retail)– Tradacoms (U.K.)– VDA (German Automotive)– Odette (Automotive)– Cargo-IMP (Airfreight)– Gencod (France)– Name/Value pairs– Proprietary– Other (User Configurable)

EDI Accelerator - Acknowledgements

Full End-to-End handling of Functional and Technical Acknowledgments– X12 997 (Functional) and TA1 (Technical)

– EDIFACT CONTRL (Functional)

Interchange, Group and Document level acknowledgements

Time-out handling

Full reporting via Health and Activity Tracking (HAT)

EDI Accelerator - Auditing

All EDI documents passing through the EDI Accelerator are recorded in the database (metadata) and on disk (the EDI files themselves)

Timestamps for Receive, Translate and Hand-off to BizTalk MessageBox on the inbound

Timestamps for Receive, Translate and transmission to the EDI Partner on the outbound

Archive & Delete scheduler – prepare for storage on Tape or CD for legal purposes

EDI Accelerator - Auditing