Mapping and translation

Accurate maps, built and maintained by specialists

Maps are where partner requirements meet your ERP data, and small mistakes cause rejected documents and penalties. ECOM's mapping specialists build, test and maintain maps across standards and platforms.

Talk to an EDI/API Expert Request a Demo

Summary: Mapping and Translation

  • EDI mapping defines how data in one format corresponds to data in another, for example how fields in an X12 850 purchase order populate a sales order in an ERP.
  • Maps are where partner requirements meet your ERP data, and small mistakes cause rejected documents and penalties.
  • What ECOM covers: Standards coverage, ERP formats, Platform coverage, Testing.
  • What you gain: Fewer rejected documents, Reusable designs, Documented logic.
  • Next step: talk to an EDI/API expert about your trading partners, documents and systems.

At a glance

  • Standards coverage
  • ERP formats
  • Platform coverage
  • Testing
  • Ongoing maintenance

What is EDI mapping?

EDI mapping defines how data in one format corresponds to data in another, for example how fields in an X12 850 purchase order populate a sales order in an ERP. A map includes field relationships, code conversions, calculations, looping logic and validation rules, and it must reflect each partner's implementation guide.

Why teams choose it

Benefits

01

Fewer rejected documents

Maps that follow partner guides closely reduce errors and penalties.

02

Reusable designs

Template-based maps speed up changes and new partners.

03

Documented logic

Clear documentation makes future changes faster and safer.

Scope

What's included

  • Standards coverage

    X12, EDIFACT, XML, JSON, CSV and flat files.

  • ERP formats

    SAP IDocs, Oracle interfaces, NetSuite and Dynamics formats, and custom files.

  • Platform coverage

    Maps on PRISM and on IBM Sterling B2B Integrator.

  • Testing

    Validate maps with sample data and partner test cycles.

  • Ongoing maintenance

    Update maps when partners change requirements or your ERP changes.

Fit

When it fits

New partner maps

Build maps for a new customer or supplier.

Partner guide changes

Update maps when a partner releases a new version.

Implementation

How implementing Mapping and Translation works

Integration projects move through these five stages. What changes is who does each task, which depends on the delivery model you choose.

  1. Discover and scope

    ECOM
    Reviews your trading partners' requirements, documents, systems and volumes, and confirms the scope in writing.
    Your team
    Share partner guides or vendor manuals, sample documents, your ERP and version, and your deadlines.
  2. Design and build

    ECOM
    Designs the flows and builds the maps, rules and connections, or supports your team building them on the platform.
    Your team
    Confirm business rules and field meanings, and provide test data and access to the right people.
  3. Test and certify

    ECOM
    Tests each document internally, then completes the partner's testing or certification steps.
    Your team
    Check test results in your own systems and approve them before go-live.
  4. Transition and go-live

    ECOM
    Plans the cutover, including a move from a current provider or platform, and watches the first live transactions.
    Your team
    Approve the go-live date and coordinate your internal teams and partner dates.
  5. Support and improve

    ECOM
    Monitors and supports the integration as your delivery model and service agreement define, and handles partner changes in scope.
    Your team
    Tell ECOM about business changes, new partners and priorities.

What affects timing and price

ECOM sends a scoped proposal after reviewing your requirements. These factors make the most difference:

  • How many trading partners and document types are in scope
  • Each partner's testing and certification process and schedule
  • Your ERP or application, and whether a standard connector fits or custom integration is needed
  • Custom business rules, data quality and the work needed to map them
  • Connection methods (AS2, SFTP, VAN, API) and security requirements
  • Delivery model and support coverage, for example 24×7
  • Transaction volumes and any migration from an existing platform

Scope my project Who does what in each delivery model

Frequently asked questions

What is the difference between mapping and translation?

Mapping is designing how data elements correspond between formats. Translation is the runtime process that applies the map to convert actual documents.

Can you work on our existing maps?

Yes. ECOM maintains maps on PRISM and supported platforms such as IBM Sterling B2B Integrator.

How are maps tested?

Maps are tested with representative ERP data and partner test documents before production use.

Talk to an EDI/API expert

Tell us about your partners, systems and goals. We will show you how PRISM and our team can help.