EDI integration software for flat files.
DataBridge maps, validates and moves the CSV files that your EDI translator or provider produces and consumes, between your ERP's database, SFTP servers and shared folders, on a schedule. It does not translate raw X12 today.
What DataBridge does with EDI.
Your translator or provider handles the X12 side. DataBridge handles the files on either side of it.
The EDI Complete Pack
CSV layouts for nine X12 transaction sets and six ready mappings between those layouts and ERP-side sales order, invoice and shipment layouts. Open it from the Marketplace, which any paid module unlocks.
SFTP, FTP, folders and more
Pick up inbound files from SFTP, FTP or FTPS servers, shared folders, HTTP addresses, Azure Blob Storage or Amazon S3. Deliver outbound files by SFTP, FTP or FTPS, to a folder, by HTTP, by email, or to Azure Blob Storage or Amazon S3.
Validate, translate codes, keep proof
Validate each file against its layout, turn partner IDs into your customer numbers with a crosswalk that fails the row when a code is missing, write rejects to a file, and keep each delivery's size and SHA-256.
Which documents have layouts.
Layouts describe the flat file your translator produces or consumes, not the X12 wire format.
| Set | Document | CSV layout | Ready mapping |
|---|---|---|---|
| 850 | Purchase Order | Yes | 850 to Sales Order |
| 855 | Purchase Order Acknowledgment | Yes | Sales Order to 855 |
| 860 | Purchase Order Change Request | Yes | None |
| 810 | Invoice | Yes | Invoice to 810 |
| 820 | Payment Order and Remittance Advice | Yes | None |
| 856 | Advance Ship Notice | Yes | Shipment to 856 |
| 940 | Warehouse Shipping Order | Yes | Sales Order to 940 |
| 945 | Warehouse Shipping Advice | Yes | 945 to Shipment |
| 997 | Functional Acknowledgment | Yes | None |
| The 855 mapping stamps the run date and accepts every line at the ordered quantity, and the 856 mapping fills the carrier SCAC and ship-to code from fields your ERP may keep elsewhere. Read the pack's mapping notes before go-live. | |||
Inbound and outbound, step by step.
Each path has its own guide with the full steps and limits.
Purchase orders into SQL Server
Pick up the 850 file, validate it, translate the buyer ID, load a staging table and notify someone.
OutboundInvoices and ship notices from SQL Server
Read new documents with a query, send each one once, validate the file and push it where the translator collects it.
The whole workflow is in EDI flat files with trading partners. Crosswalks are covered in duplicate customers and crosswalks.
Where it runs unattended.
Build a layout for a sample partner file and validate it. The file is read in your browser and is not uploaded. It has no sources, destinations or schedules.
With Transfer, delivers to all seven destination types, and with Flow runs scheduled jobs while the app is open. It has no Sources screen today.
Picks up partner files from sources and runs schedules unattended. Needs Transfer and Flow, plus Database to read outbound documents from your ERP. What each edition includes.
What it does not do.
- DataBridge does not read or write raw X12: the ISA, GS and ST envelopes, delimiters and 997 acknowledgments. You need an EDI translator or provider.
- DataBridge has no AS2 or VAN connection. Your translator or provider handles trading partner connectivity.
- The 997 layout describes a flat file. DataBridge does not generate acknowledgments.
- Loading a database needs an administrator to switch on writes for that connection.
Translating X12 documents
We plan to add a translator for X12 documents. It is not shipped, and it is not part of any plan today. Its status and estimated window are on the roadmap. Windows are estimates, not promises.
EDI questions.
Can DataBridge convert an EDI 850 to CSV?
Not from raw X12. DataBridge does not parse X12 envelopes, so your EDI translator or provider produces the CSV. DataBridge then validates it against the 850 layout in the EDI Complete Pack, maps it to your order layout and loads it. See EDI 850 to SQL Server.
How does X12 EDI mapping work in DataBridge?
A file template describes the CSV layout your translator produces or consumes, and a field mapping turns it into your ERP's layout, with transform rules and crosswalks for partner codes. The EDI Complete Pack ships layouts for the 850, 855, 860, 810, 820, 856, 940, 945 and 997, and six mappings: 850, 855, 810, 856, 940 and 945.
Can I load EDI data into SQL Server?
Yes, from the flat file. A Write to database step inserts, updates or inserts, or replaces rows in a staging table, on a connection an administrator has enabled for writes, and rejected rows can go to a file. The 850 guide lists the modules it needs.
Does DataBridge work for small distributors?
It suits a distributor that already uses an EDI translator or provider and needs the files to flow into and out of its ERP database. The free browser edition lets you check a partner file first, and paid modules are month to month. See pricing.
How do EDI files reach my trading partners?
Through your translator or provider. DataBridge picks up files from SFTP, FTP or FTPS servers, folders, HTTP addresses, Azure Blob Storage and Amazon S3, and delivers to those and by email. It has no AS2 or VAN connection.
Will DataBridge translate X12 itself?
Not today. A translator for X12 documents is planned. See the roadmap for its status. Windows there are estimates, not promises.
Test a partner file before you buy anything.
The free browser edition needs no sign-in and never uploads your files. See what leaves each edition.