The short answer
SAP Business One does not translate EDI itself. An integration layer converts partner documents and creates Business One sales orders through the Service Layer, a REST-style interface, or the older DI API. Deliveries and A/R invoices then drive outbound ship notices and invoices. Business partner catalog numbers translate customer item numbers, and user-defined fields keep partner references.
Read the diagram from top to bottom. SAP Business One does not exchange X12 itself in this design: the integration layer handles the partner connection and translation, and SAP Business One creates and posts the business records. Outbound documents are built from what SAP Business One actually recorded.
How EDI connects to SAP Business One
SAP Business One serves small and midsize distributors, manufacturers and brands that often face the same EDI requirements as large enterprises when they sell to major retailers. An integration layer handles partner connectivity and translation and exchanges documents with Business One. Larger SAP environments work differently; see the SAP S/4HANA and ECC guide.
Document mapping
| EDI document | Direction | Business One document |
|---|---|---|
| 850 purchase order | Inbound | Sales order |
| 855 acknowledgment | Outbound | Sales order status and lines |
| 856 ship notice | Outbound | Delivery |
| 810 invoice | Outbound | A/R invoice |
| 846 inventory | Outbound | Item availability by warehouse |
Integration options
- Service Layer: a web-based, OData-style interface for creating and reading Business One documents. It suits new integrations and cloud-hosted environments.
- DI API: a long-standing programming interface used by many add-ons. Common in existing on-premises integrations.
- Data import tools: file-based loading for initial data and simple scenarios.
Partner data
- Business partner catalog numbers map customer item numbers to your items.
- Ship-to addresses on the business partner hold retailer store and distribution center codes.
- User-defined fields (UDFs) store EDI identifiers and the partner’s original purchase order line numbers, which acknowledgments and invoices must echo.
Shipping data
Retail ship notices need carton-level detail and GS1-128 labels. Business One deliveries hold items and quantities but not carton contents by default, so packing data usually comes from a packing add-on, a WMS or the EDI solution itself. Decide this before go-live, because it affects warehouse workflows.
Starting small
Companies with only a few partners often start with web EDI and integrate Business One as volume grows. See web EDI vs integrated EDI.
Best practices
- Validate business partners, items and prices before creating sales orders.
- Keep partner-specific rules in the integration layer rather than in Business One.
- Create deliveries from actual picking so ship notices reflect what shipped.
- Monitor each order through acknowledgment, delivery and invoice.
- Test integrations after Business One version upgrades.