Sign in Start free
Start free Sign in Create account
Integration · EDI

EDI 850 to SQL Server integration

Your translator turns the 850 into a flat file. DataBridge validates it, maps it, translates the buyer ID to your customer number and loads a staging table.

EDI 850 flat file (CSV) → SQL Server staging table

Start free All integrations
What you need

Modules. Any paid module opens the Marketplace. Transfer, Flow and Database, the Everything bundle, run this unattended.

Edition. DataBridge Server for unattended schedules.

Pricing and what each edition includes.

Limits, stated plainly
  • DataBridge does not read raw X12 (ISA, GS and ST envelopes). You need an EDI translator or provider that produces the flat file.
  • The staging table must exist, and an administrator must switch on writes for the connection.
  • Read the pack's mapping notes before go-live. They list what each mapping fills and what to check.
Steps

How it works.

Each step names the feature as it appears in the product.

  1. Step 1

    Source

    Pick up the translator's 850 file from an SFTP server or a shared folder. A source remembers what it has ingested.

  2. Step 2

    EDI Complete Pack

    The 850 template describes the CSV layout, and the 850 mapping fills CustomerID with the buyer's EDI party ID and OrderNumber with the PO number.

  3. Step 3

    Crosswalk

    A crosswalk turns the buyer ID into your customer number and can fail the row when a code has no entry.

  4. Step 4

    Write to database

    Insert into a staging table your ERP's import reads. Bad rows can go to a reject file.

  5. Step 5

    Notification

    Email the right person when a file is loaded or a run fails.

Marketplace packs used: EDI Complete Pack. See the Marketplace.

Questions

Common questions.

Does DataBridge parse X12 850 files directly?

No. It maps the CSV that your EDI translator produces and consumes, and it does not parse raw X12.

Which EDI documents have layouts?

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.

Keep reading

Related use cases and integrations.

EDI 850, 810 and 856 Flat File MappingDuplicate Customer Matching and CrosswalksEDI 810 and 856 files from SQL ServerEDI integration overviewWhat DataBridge connects to

QuickBooks, Sage 100, NetSuite, Salesforce, HubSpot, Dynamics 365, Shopify and Amazon are trademarks of their respective owners. Names are used only to say which system a connection, layout or file is for. ExtensibilityCo is not affiliated with or endorsed by any of them.

Next step

Try the parts that are free today.

The free browser edition needs no sign-in and never uploads your files.

Start free All features