Browse Business Software Categories

A
B
C
D
E
F
H
I
M
N
P
R
S
W
Close  

Distribution

ERP

Supply Chain Management

SAP Business One EDI Integration: Providers and Mapping

Sherman Hsieh
Share This Post!
Published
SAP Business One EDI Integration: Providers and Mapping

Last updated: November 6, 2026 · Independent guide · We do not sell rankings or coverage.

This guide covers SAP Business One EDI integration through a third-party provider. SAP Business One’s Integration Framework includes an EDI scenario for sending marketing documents to trading partners, but SAP’s help page for it does not mention X12, AS2 or VAN connectivity, and it asks you to check first whether your trading partner already has a matching scenario (SAP Help, Electronic Data Interchange, no date shown). A provider translates X12 or EDIFACT documents and posts them into SAP Business One, while you prepare the master data that every map depends on: business partner codes, ship-to address IDs, item numbers, units of measure and bar codes. This guide walks an administrator through that preparation in the order it is done, then covers mapping effort, published pricing and the errors that most often stop an inbound order.

Before you start

  • Release and database. Note your SAP Business One version and whether you run SAP HANA or SQL Server, then confirm the provider supports that combination and tells you whether it connects through the DI API or the Service Layer.
  • A dedicated integration user and the right license. Sana Commerce, which sells an SAP Business One add-on, documents that its integration user must be a superuser with an Indirect Access User license, with an Indirect Access Instance license on the application server for Service Layer traffic (Sana Commerce, updated September 2020). Confirm the license type with your SAP partner.
  • Each trading partner’s implementation guide, with its required documents, store and DC identifiers, and label specification.

The SAP menu paths below come from SAP’s public help pages for release 9.x. Confirm each path in your own client before you start.

How the integration fits together

The trading partner sends a document over a VAN or AS2, the provider’s translator converts it, and a connector creates or reads the SAP document, such as a sales order from an inbound 850. TrueCommerce describes this as its Transaction Manager connecting to SAP through a Business System Plug-In, running either on premises or as SaaS, with connectivity over AS1, AS2, AS3, FTP and VAN interconnects (TrueCommerce datasheet, no date shown).

The translator can only post a document if every code in it resolves to a record in SAP Business One, so most setup effort goes into master data.

Step 1: Create the integration user and assign its license

Create a named user for the EDI connector at Administration > Setup > General > Users (SAP Help, no date shown). Do not reuse a person’s login, or you lose the audit trail.

Assign the license at Administration > License > License Administration, on the Assignment tab (SAP Community blog by SAP, no date shown). SAP’s help notes that you cannot import a new license file while the DI Server service is running, so schedule license changes outside EDI processing windows (SAP Help, License Administration Window, no date shown).

Step 2: Set up business partners and ship-to address IDs

Open Business Partners > Business Partner Master Data and confirm one customer card for each trading partner. The card’s BP code (CardCode) is the value your EDI tool uses to link the trading partner to that customer (TrueCommerce Help Center, June 25, 2024).

Next, open the Addresses tab and create one Ship To address for each store or distribution center the partner ships to. SAP requires you to enter the Address ID first, and customers can hold multiple Bill To and Ship To addresses. The same tab has a GLN field of up to 50 characters, which is useful when a partner identifies locations by Global Location Number (SAP Help, Addresses Tab, no date shown). Using the partner’s store number as the Address ID keeps the Step 6 cross-reference simple.

Step 3: Set up units of measure and bar codes on items

Retail partners order in cases or inner packs, while you may stock in eaches. Define the conversion at Administration > Setup > Inventory > Unit of Measure Groups. SAP applies the conversion automatically in sales, purchasing and inventory, but a UoM group cannot be removed from an item once assigned (SAP Help, Setting Up Unit of Measure Groups, no date shown).

Then add UPC or GTIN codes in the item’s Bar Codes window, opened with the Browse button beside the Bar Code field in Inventory > Item Master Data. You can assign several bar codes to each unit of measure, so the case GTIN and the each UPC can both point to the same item (SAP Help, Bar Codes, no date shown; SAP Help, Item Master Data: General Area, no date shown).

Step 4: Record the partner’s item numbers

Many buyers send their own item number on the 850 instead of your item code. Record these at Inventory > Item Management > Business Partner Catalog Numbers, either per business partner for a list of items or per item for a list of partners. If you tick Use BP Catalog Number in Documents, the BP Catalog No. column appears on documents for that partner (SAP Help, Defining Business Partner Catalog Numbers, no date shown). Some EDI tools keep their own item cross-reference instead, so ask your provider which table it reads.

Step 5: Add user-defined fields for EDI data with no native home

EDI orders carry values SAP Business One has no standard field for, such as the partner’s department number, promotion code or ship-not-before date. Create these at Tools > Customization Tools > User-Defined Fields – Management (SAP Help, User-Defined Fields – Management, no date shown). If a partner requires these values back on the 856 or 810, a field that is not stored on the order cannot be returned later.

Step 6: Build the cross-references in the EDI tool

Each provider has its own screens. As one documented example, TrueCommerce has administrators work under Trading Partners > (partner) > Translations:

  1. Partner List: sync or add the SAP BP code for each customer (TrueCommerce, June 25, 2024).
  2. Address List: enter the partner’s store or ship-to code as the EDI Code, the SAP Address ID as the Bus Sys Code, and set Type to Store, or to DC when the partner sends a distribution center code (TrueCommerce, June 26, 2024).
  3. Item Catalog: set the Primary Item code for each document type under Preferences, then sync or add each partner item against the SAP item number (TrueCommerce, June 26, 2024).

Other providers use different names for the same three cross-references. Ask any provider to show you where they live before you sign.

Step 7: Prepare fulfillment for the ASN and labels

The 856 must describe each carton or pallet as it was packed. In SAP Business One, picking runs through Inventory > Pick and Pack > Pick and Pack Manager, which releases open sales orders to pick lists and creates deliveries (SAP Help, Pick and Pack Manager, no date shown). Each carton on the ASN carries an SSCC, an 18-digit number encoded in a GS1-128 bar code with Application Identifier 00 (GS1 UK, no date shown). SAP’s item help names EAN-13 and Code 39 as supported bar code formats, and TrueCommerce sells an EDI Labeling add-on that prints UCC-128 labels directly from SAP, plus auto-pack options for the delivery packing slip (SAP Help, Item Master Data: General Area, no date shown; TrueCommerce datasheet, no date shown). Our guide to the EDI 856 advance ship notice covers the hierarchy partners expect.

Step 8: Test each document with each partner, then schedule

Run test files for each document and partner before going live: the inbound EDI 850 purchase order, the 855 acknowledgment if required, the 856 and the EDI 810 invoice. If you ship through a 3PL, add the EDI 940 and 945. Once every test passes, set the import and export schedule so orders arrive before your picking waves begin.

Mapping effort: what to plan for

Mapping effort scales with trading partners multiplied by documents, because each partner’s guide differs. The illustration below is ours, not a vendor quote.

Illustration Partners Documents each Partner-document maps to test
Small distributor 2 850, 856, 810 6
Manufacturer selling to big-box retail 5 850, 855, 856, 810 20
Distributor using a 3PL 5 customers plus 1 3PL Customer docs plus 940, 945 17 (15 plus 2)

A missing ship-to or catalog number blocks every order for that store or item, so budget time for the master data in Steps 2 to 5 as well as the maps.

Providers and published pricing

Several EDI providers sell integrations for SAP Business One. TrueCommerce publishes starting prices: its Mid-Market plan, which lists SAP Business One among its integrations, is shown from $499 per month with 5 trading partner connections and 3 integrated documents, although each plan on the same page also shows a second “from $99 per month” figure that the page does not explain (TrueCommerce pricing page, no date shown). SAP’s partner listing for the TrueCommerce integration says pricing combines an up-front cost and a monthly subscription with a one-year minimum (SAP partner listing, no date shown). SPS Commerce offers a full-service integration in which its team maintains maps and handles spec changes, but publishes no price (SPS Commerce, modified January 13, 2026). Codeless Platforms sells BPA Platform, a drag-and-drop integration tool, and its subscription pricing section shows a figure of “from 4200” without stating the currency or billing period (Codeless Platforms, no date shown), and TIE Kinetix offers its cloud EDI-2-FLOW product for SAP Business One, also without published pricing (TIE Kinetix, no date shown). Every vendor named here sells the product it describes.

Common mistakes and how to fix them

  • “Invalid value [ORDR.ShipToCode]” on an inbound 850. The partner’s ship-to code has no matching SAP Address ID. Add the Ship To address in SAP, then add the Address List translation (TrueCommerce, June 26, 2024).
  • “CardCode cannot be null.” The EDI tool cannot match the order to a business partner, most often after a new customer or ship-to appears. Add the correct CardCode to the Partner List (TrueCommerce, September 4, 2026).
  • Orders fail on item lookup. If the Primary Item field is empty on an 850, the export fails (TrueCommerce, June 26, 2024). Add the partner item number before the partner starts ordering it.
  • Quantities off by a pack factor. The partner ordered cases and SAP booked eaches. Check the UoM group and the bar code on each unit.
  • ASN rejected for missing order data. A value such as the department number was never stored on the sales order. Add a user-defined field and map it inbound.

Limitations of SAP Business One’s native features

SAP Business One stores the data EDI needs. Its Integration Framework EDI scenario sends marketing documents to trading partners, but SAP’s help page for it does not mention X12, VAN or AS2 connectivity (SAP Help, Electronic Data Interchange, no date shown). Its item bar code help names EAN-13 and Code 39 as supported formats and says other bar code types can be printed, so confirm how your SSCC carton labels will be produced before go-live (SAP Help, no date shown). An item’s UoM group also cannot be removed once assigned, so pack-size errors are hard to correct later (SAP Help, Setting Up Unit of Measure Groups, no date shown).

When companies add a third-party tool

A web EDI portal with no integration can work for one low-volume partner, but staff re-key every order. Companies move to an integrated connector once order volume or chargebacks make re-keying costly, and add label printing, auto-pack or 940 and 945 support as retail and 3PL requirements grow. A general integration platform such as BPA Platform can also cover ecommerce and other flows, but you or your partner then build and maintain the maps.

How we researched this

We reviewed SAP’s public help pages for each menu path, provider documentation and pricing pages, and GS1 guidance on SSCC labels between November 4 and 6, 2026. We also read the pages ranking for this search, which are mostly vendor product pages. None of the vendors named here paid for inclusion, and we did not estimate prices that vendors do not publish.

Related guides

Frequently asked questions

Does SAP Business One have built-in EDI?

Only in a limited form. SAP Business One’s Integration Framework includes an EDI scenario for sending marketing documents to trading partners, but SAP’s help page for it does not mention X12, AS2 or VAN connectivity. This guide covers the route through a third-party provider that posts documents into SAP Business One.

How much does EDI for SAP Business One cost?

TrueCommerce lists a Mid-Market plan that includes SAP Business One from $499 per month for 5 trading partners and 3 documents, plus an up-front cost and a one-year minimum. SPS Commerce and TIE Kinetix do not publish prices, and Codeless Platforms shows only a starting figure without a currency or billing period, so request quotes based on your partner and document count.

Do I need a separate SAP license for the EDI integration user?

Usually. Integration vendors commonly document an Indirect Access User license for the connector’s login, but requirements vary, so confirm with your SAP partner.

Where do I store a customer’s item numbers in SAP Business One?

Use Business Partner Catalog Numbers under Inventory > Item Management. Some EDI tools keep their own item cross-reference instead, so check which one your provider reads.

Why are my EDI orders failing with a ShipToCode error?

The ship-to or store code in the 850 does not match an Address ID on the customer’s Addresses tab. Create the Ship To address and add the matching translation in your EDI tool.

Sources

Sherman Hsieh

CEO & Editor-in-Chief, Business-Software.com
Independent analysis of enterprise software — ERP, CRM and more
Sherman Hsieh is the founder, CEO, and editor-in-chief of Business-Software.com. He leads the site's independent, buyer-focused coverage of ERP, CRM, and other business systems, including vendor-neutral comparisons, pricing analysis, and implementation guidance. Before founding Business-Software.com, Sherman was an executive at Siebel ...

Users Who Read This Article Also Read