Data formats and sources

Any format in, the right format out

Not every system speaks EDI. Online stores send JSON, procurement networks use cXML, older applications export CSV or fixed-width files, and some processes read straight from a database. ECOM's B2B gateway transforms data between these formats and EDI, so every system and partner gets data in the shape it expects.

Talk to an EDI/API Expert Request a Demo

Summary: Data Formats and Data Sources

  • Data transformation converts information from one structure to another, for example from a JSON order to an X12 850 purchase order, or from a database table…
  • Not every system speaks EDI.
  • What ECOM covers: Format-to-format mapping, Validation rules, Enrichment and lookups.
  • What you gain: Connect systems without rewriting them, One place for transformation rules, Cleaner data.
  • Next step: talk to an EDI/API expert about your trading partners, documents and systems.
Discuss data formats

At a glance

  • Format-to-format mapping
  • Validation rules
  • Enrichment and lookups

What is data transformation?

Data transformation converts information from one structure to another, for example from a JSON order to an X12 850 purchase order, or from a database table to a CSV file, while checking that required values are present and correctly formatted along the way.

Outcomes

What you can expect

01

Connect systems without rewriting them

Applications keep producing the formats they already support; the gateway handles the conversion in between.

02

One place for transformation rules

Mapping rules live on the integration platform instead of in scripts scattered across servers and teams.

03

Cleaner data

Validation during transformation catches missing or malformed values before they reach a partner or your ERP.

Approach

How ECOM delivers it

  • Format-to-format mapping

    Maps between JSON, XML, cXML, CSV, flat files, EDI standards and database records, in either direction.

  • Validation rules

    Required fields, code lists and value formats are checked against the target format and partner rules.

  • Enrichment and lookups

    Values such as item numbers, units of measure and locations are converted using cross-reference tables.

Formats

Formats and data sources

The formats the B2B gateway reads and writes, alongside the EDI standards on the standards page.

EDI and B2B standards
  • JSON

    The lightweight format used by most modern APIs, online stores and SaaS applications.

    JSON in detail
  • XML

    Structured documents defined by a schema, used by many enterprise applications and industry standards.

    XML in detail
  • cXML

    The commerce XML format used by procurement networks such as SAP Ariba for orders, confirmations and invoices.

    cXML in detail
  • CSV

    Comma-separated files exported from spreadsheets, legacy systems and reporting tools.

    CSV in detail
  • Flat files

    Fixed-width and delimited text files produced by ERP and mainframe systems.

    Flat files in detail
  • Databases

    Reading from and writing to SQL and relational database structures when an application exchanges data through its database.

    Databases in detail

File layouts

Fixed-width, delimited and custom application files

Positional, delimited and user-defined layouts for applications that exchange their own files.

  • Fixed-width files

    Fixed-length files with positional records and fields, common in mainframe and legacy ERP exports.

    Fixed-width files in detail
  • Delimited files

    Variable-length files with configurable delimiters, including CSV and other delimited text with custom record and field layouts.

    Delimited files in detail
  • Custom application files

    User-defined positional, delimited, XML, JSON or EDI layouts for applications that exchange their own file formats.

    Custom application files in detail

Scenarios

Common scenarios

Online store to retailer EDI

JSON orders from an e-commerce platform become X12 documents for a retailer, and ship notices flow back.

Procurement network orders

cXML purchase orders from a customer's procurement network are converted for your ERP.

Legacy system exports

CSV or fixed-width files from an older system are transformed into the formats partners require.

Frequently asked questions

Can you convert JSON or cXML into X12 EDI?

Yes. The B2B gateway maps between JSON, cXML, XML and EDI standards in either direction, with validation against the partner's requirements.

Can the platform read directly from our database?

Where your application exchanges data through database tables, the gateway can read and write those records. ECOM confirms the database and access method during scoping.

Who maintains the mapping rules?

Depending on your delivery model, your team, ECOM specialists or both. The responsibility is set in your service agreement.

Map your data formats

Tell us which systems and formats you need to connect. ECOM outlines the mapping and validation approach.