EDI Mapping

Let us show you how quickly your EDI maps can be written, tested, and fully implemented!

Mapping is the process of transforming data in such a way that it can be seamlessly used by internal business systems while complying with each trading partner’s unique requirements. Through EDI mapping, businesses leverage their investments in ERP and other applications, while reducing errors and the amount of time that is necessary to process trading partner data such as purchase orders, invoices, and shipping notices. EDI mapping can comply with any data format required by your trading partner community and internal systems.

  • Map EDI (or other) transactions to/from internal formats (such as IDoc and XML)
  • Implement EDI transactions using various standards, such as—
    • Electronic Data Interchange (EDI)
    • X12
    • HIPAA
    • EDIFACT
    • TRADACOMS
    • Extensible Markup Language (XML)
    • Japanese Center for Informatization of Industry (CII)
    • IDoc
    • Proprietary (Positional or Variable-Length-Delimited)
    • Structured Query Language (SQL)
  • Utilize your mapping application, including, but not limited to—
    • Gentran Application Integrator
    • Gentran Visual Mapper
    • Liaison Softshare Delta®
    • Trinary EDI WINDOWS™
    • GXS TrustedLink® Enterprise Mapping Workbench
    • WebSphere® Integration

EDI transactions are seamlessly converted to/from application data formats while complying with partner-specific requirements. They are automatically integrated with all required internal and external interfaces. Our experienced EDI resources provide support for documents in various EDI, XML, IDoc, proprietary, and other data formats as necessary in your unique environment. We offer any-to-any mapping for all major EDI middleware applications.

We will provide rapid and accurate deployment of your solution by:
  • Analyzing required source and destination application formats
  • Creating document-specific mapping and translation specifications by trading partner (customer, vendor, financial institution, freight carrier/forwarder, etc.)
  • Developing interface maps
  • Configuring, developing, and testing all interfaces while ensuring the most cost-effective and transparent trading partner implementation possible
  • Providing mentoring and ongoing support

When you have an electronic document in one format (e.g. ANSI X12 850 Purchase Order from your customer) and the document is needed in a different format (e.g. an ORDERS IDoc to be consumed by your SAP ERP system), you must transform the source document data format to another format. A translation service transforms the data, and a “map” contains the necessary logic to do so.Translation occurs when the source transaction is analyzed, and based on its contents, the intended target format is determined. Then, the appropriate logic (as defined in a map) is executed. The resulting data, in the agreed format, is then seamlessly passed to the intended internal application system and/or external trading partner.