Home Page

Altova's MapForce for EDI: Adds Power to XML and Cuts Cost

       EDI Transaction Sets Now Available in Enterprise

 


Other Services
» New Installations
» EDI Maintenance
» EDI Training
» AS2
» HIPAA EDI
» Auto Notification
» E-Invoicing
» Replace Your
Costly Outsourcer
 

Need a Stronger
Supply Chain?
We Can Help!

 

Significant savings can occur when a specific instance of EDI is needed by using an XML tool with built-in EDI schemas. Products such as Altova’s MapForce™ 2008 Enterprise Edition readily process single use messages such as inbound Sales/Inventory (X12 Transaction Set 852) or outbound Price/Catalog data (1SYNC). This means you can readily create a stand-alone instance of EDI for a specific purpose without disrupting your production EDI system. Additionally, the Altova display or data entry capability uses a Web form or spreadsheet, technology with which most office professionals are familiar.

Overview

Many instances of EDI would benefit your company through improved process automation for faster processes and lower head count. Consider loading EDI data automatically loaded into Microsoft Server for SQL™ tables from which you can build applications. Examples include sales data and complex pricing.

Most EDI is X12 formats instead of the XML formats with which you are familiar. X12 is universally used due to very fine granularity of data definition and business codes exchanged. Since both are data and tag protocols the conceptual leap is not large; It is straight-forward, but not trivial. An XML tool with built-in X12 schemas for data validation bridges the gap.

The benefit is lower cost of launch. However, an XML tool creates only the EDI X12 map so these other components must also be built.

    1. Field definition
    2. Table structure
    3. Business rule execution
    4. Human interface and reporting
    5. Temporary table for import/export
    6. Data transmission (usually AS2 or FTPS), with recovery

Fortunately, in many instances, a developer already has the first, second, and sixth in place.

Here are the steps:

  • Ask users about repetitious, time wasting data entry or spreadsheet creation processes for Vendor Managed Inventory (VMI) or Price Sheets
  • Contact the Trading Partner to learn if the EDI Transaction Set and direction is available (obtain an EDI Implementation Guide and sample data)
  • Map and test
  • Train the user staff in the new process and another in your I.T. group as a back-up for troubleshooting.

Conclusion

Process automation remedies a labor intensive process. An investment in automation can have a quick return and later build outs can yield further savings. DCS knows the processes of large Trading Partners, so setup is quicker and economical with our help. On-going improvements are also easier when DCS is there to assist as needed. Your first step is easy, contact DCS for a budgeting estimate at info@dcs-is-edi.com

Contact DCS    |  Links    |  Careers    |  Home

© Copyrights 1991 - 2008, Data Communication Solutions Inc. All Rights Reserved.