Eshop integration with SAP Business One: workflows, prerequisites and testing

Integrate the store with SAP Business One around a defined workflow and the installation's available interface. In SAP Business One, an order must connect to a Business Partner, Item and the agreed commercial document lifecycle. The store should not treat delivery, invoicing and cancellation as simple changes to one generic status.

In SAP Business One, an order must connect to a Business Partner, Item and the agreed commercial document lifecycle. The store should not treat delivery, invoicing and cancellation as simple changes to one generic status. Use the available Service Layer business operations and retain the relationship between the external event and SAP documents. The SAP administrator defines series, warehouses, required fields and when a process is considered complete in business terms.

Service Layer provides an interface to Business One data and services. The official reference recommends OData v4 as the primary protocol from FP2405 and deprecates v3 while retaining it for compatibility. Business One is not S/4HANA. Endpoints, objects, configuration, and business workflows differ. Service Layer is not functionally identical to DI API either.

A spare-parts distributor records a B2B purchase as a sales order. Map products to the Item master and the buyer to the correct Business Partner. If only part of the quantity is delivered, update the store from confirmed documents rather than assigning an arbitrary whole-order dispatch status. A cancellation request is evaluated at the current order stage and executed only through a permitted operation. Retain links between the order and subsequent documents for reconciliation and support.

An important failure scenario occurs when a cancellation is attempted as a simple field update instead of the appropriate business operation. Keep the external reference and confirmed destination ID before retrying. Separate access failure, business rejection and an unknown outcome. An operator must be able to inspect the relevant record and resolve its status without replaying completed steps. Agree which fields may appear in logs and who handles unresolved cases.

Test order creation, a supported cancellation, and correctly linking a subsequent document. For each case record the expected source data, destination record and customer-visible state. Include one denied-permission case and one interrupted response. Re-run a previously confirmed event and check that its business effect is unchanged. The acceptance record should identify the responsible team and the evidence required to close any discrepancy.

The initial discovery should confirm: Enabled and reachable Service Layer; Agreed OData version and authorised user; SAP administrator for objects and commercial rules. Before launch, document the mapping for SAP items/customers → store mapping → Checkout → SAP sales order → Confirmation → agreed delivery/status flow. Assign responsibility for access renewal, monitoring and correction. A change to product configuration or the agreed business rule should trigger targeted regression checks. Begin with this defined workflow; add another channel only after its ownership and acceptance cases are clear.