EDI orders, invoices and ship notices mapped to your ERP.
DataBridge maps the flat files that your EDI translator or provider produces and consumes to and from your ERP's layouts. It does not read or write raw X12.
Trading partners send purchase orders as EDI. A translator or provider turns them into flat files, and someone still has to get those files into the ERP and send invoices and ship notices back out.
Modules. Integrate bundle (Transfer and Flow) for file-to-file jobs. Add Database, which is the Everything bundle, to read outbound data straight from the ERP's database.
Edition. DataBridge Server for unattended schedules.
How DataBridge does it.
Each step names the feature as it appears in the product.
- Step 1
Sources
Pick up the translator's inbound files from an SFTP server or a shared folder. A source remembers what it has ingested, and after a successful run the file is left, archived or deleted.
- Step 2
File templates
The EDI Complete Pack ships CSV layouts for the 850, 810, 856, 855, 860, 820, 940, 945 and 997, with mappings for the 850, 855, 810, 856, 940 and 945. Validate each inbound file against its template before anything is loaded.
- Step 3
Crosswalks
The 850 mapping fills CustomerID with the buyer's EDI party ID and OrderNumber with the PO number. A crosswalk turns the buyer ID into your customer number, and it can fail the row when a code has no entry, so a wrong customer number never reaches an order.
- Step 4
Write to database or Push results
Load the validated rows into a staging table your ERP's import reads, or deliver them as a file to the ERP's import folder.
- Step 5
Outbound documents
For invoices and ship notices, a saved query reads the ERP's data, a mapping fills the 810 or 856 layout, and Push results writes the file where the translator collects it.
- Step 6
Push History
Each delivery records the file name, byte count and a SHA-256 hash of what was handed over, so you can compare it with what the partner received.
What this does not do.
- DataBridge does not read or write raw X12: ISA, GS and ST envelopes, delimiters and 997 acknowledgments. You need an EDI translator or provider on the wire side.
- The 855 mapping stamps the run date and accepts every line at the ordered quantity. Edit it if you change or reject lines.
- The 856 mapping takes the carrier SCAC from CarrierCode and the ship-to code from CustomerID. That is correct only if your ERP stores those values there. Read the pack's mapping notes before you go live.
Marketplace packs used: EDI Complete Pack. See the Marketplace.
Related pages.
Try the parts that are free today.
The free browser edition needs no sign-in and never uploads your files.