Microsoft promotes XML while large companies use X12. This means the support of both data formats is needed as large companies using X12 find its extremely precise level of detail effective in high volume, “lights out” environments. Microsoft also promotes the transmission of data through the Internet, which the EDI INT AS2 specification satisfies. Fortunately BizTalk Server^TM 2006 R2 readily supports X12 and AS2 so implementing EDI is now easier and more economical.

Overview

Briefly, both XML and X12 are formats for passing data and tags. The definition of a tag by all participants in an industry such as Consumer Products is necessary for more reliable data transmission. This means a vendor and a large company do not negotiate and agree upon tag definitions, it means the vendor to a large company will do as instructed. XML is then only useful when adapted as an industry format such as GS1^TM, RosettaNet^TM, ACORD, etc. (A XML user may define tags when controlling both sides of an application such as moving data from plant to headquarters level. The promotion of an “open” tag is deceptive.)

Data transmission is independent of data format. In the ‘90’s EDI data was sent by third party Value Added Networks (VAN) which provided “store and forward” capability as the value add. With the advent of the Internet, traffic is moving away from pricey VANs. However, some large firms continue to insist upon use of a VAN as they have negotiated very deep discounts from the VAN. EDI INT AS2 is the standard adapted by large companies such as Wal-Mart, the Departments of Defense and Human Services, Home Depot, and others. Any AS2 vendor certified by the Drummond Group (an independent certification firm) is worthy of consideration. Buyer beware: AS2 should not be purchased in a pack of trading partners. Just as you would not purchase a FTP utility that capped the number of connections, DCS suggests you find a vendor that sells unlimited connections for a fixed price.

Use of both XML and X12 requires setting different data paths, which can be nettlesome. Yet, the data is eventually sent to the same business application. To lessen the difficulty of this process, integration using ODBC instead of flat files is now common place. Use of adapters can save some time, but they do not provide completeness. For example, a Consumer Products adapter is a good first step when linking to a key customer such as Kohl’s.

A common confusion is the instance of XML. It can occur from the trading partner to BizTalk or from BizTalk to the application.

The example of the industry standard 1SYNC (UCCnet) with standardized tags is useful. Data format to/from trading partners is XML format but data format to/from the business application is a positional, flat file format or ODBC. With Microsoft Dynamics GP data format to/from trading partners is likely X12 format but data to/from the business application can be XML or ODBC. Be cautious if a vendor minimizes the difficulty of integration. (A comma, pipe, or otherwise delimited file is not recommended due to the inevitability of the character appearing in the data.)

EDI users on a Microsoft platform should consider BizTalk Server 2006 R2 as a complimentary tool for B2B E-Commerce. It is approaching the maturity of Gentran^TM, Trusted Link^TM, Mercator, GXS, or other EDI systems. It is excellent for lower volume, less routine messages such as warranty claims or data exchanged in an Excel^TM spreadsheet format. Specifically, BizTalk generates Web forms that lower volume customers can complete to automate loading tables. This process is similar to B2C E-Commerce, so portions of the existing infrastructure can likely be re-used. If AS2 capability is needed apart from EDI, then other vendors should be considered.

Conclusion

Full automation implies reliability, robustness, security, and efficient management of data flows. The “magic” of immediate exchange is simply not the way business-to-business (B2B) data exchange is done. For example, a company does not automatically accept a customers PO without scrutiny. Unfortunately, senior management does not understand the distinction between B2B processes and selling to consumers on a company’s web site.

Second, BizTalk is not an economical package, so users contemplating its purchase need to have a well developed statement of use and a roll out plan. DCS expertise with EDI for B2B since 1991 means we are adept at explaining to management that a wide variety of data formats (X12, XML, UN/EDIFACT) and secure data transmission methods are needed to provide satisfaction to key customers. This also means that self-reliance can readily occur when systems are flexibly designed. A good first step is to learn XML in B2B by automating a GS1 manual process. Using a seasoned expert who knows EDI and BizTalk will save you time and headaches. DCS is eager to work with your Microsoft dealer: we do not seek non-EDI work. BizTalk will play a role in E-Commerce as the relentless march to automation continues. DCS views BizTalk as another tool in the arsenal of EDI managers, but not as a replacement to traditional EDI. The first step is easy, just e-mail us for your Free EDI Assessment.