ERP
SAP Business One
SAP Business One is connected on SAP HANA as well as on Microsoft SQL Server, through SAP's Service Layer. Items come out as Commerce Bundle products — with description, barcode, item group, unit, the price of a price list and stock.
In the other direction, orders are created as sales orders; sales orders and deliveries come back with processing state and tracking number.
An order Business One already knows by its number is skipped.
- SAP Business OneERP
- ConFlowIOintegration platformRun active
- Shopware 6
- Shopify
- WooCommerce
- 7ready-made building blocks
- 21data models in the Commerce Bundle, one mapping for every target
Building blocks
Seven building blocks for SAP Business One
- Read itemsRead
Reads items as Commerce Bundle products, in full or only those changed since the last run, with the price of a price list and stock — in total or per warehouse.
- Read stockRead
Reads stock as lean records. An item without a stock figure is skipped rather than reported as zero.
- Hand over ordersWrite
Creates orders as sales orders — with billing and delivery address, with the prices paid and shipping costs if needed. Known orders are skipped.
- Read sales ordersRead
Reads sales orders and deliveries back with processing state and tracking number.
- Cancel sales ordersWrite
Cancels the sales order when the order was cancelled in the shop — as long as nothing of it has been delivered.
- Read master data and documentsRead
Reads, with Business One's field names, business partners, quotations, deliveries, invoices, credit memos, returns, incoming payments and value lists.
- Free request
For everything there is no ready-made building block for: a request to the API, with the stored credentials.
In practice
Two workflows with SAP Business One
Items with price and stock into the shop
SAP Business One holds items, price lists and stock; the shop should show the same state.
- Triggerschedule
- Readitems from Business One, with the price of a price list
- Change detectiononly what changed goes on
- WriteShopware 6, Shopify or WooCommerce
One mapping onto the Commerce Bundle, and the last building block decides which shop is written.
Orders into the ERP — and back
Orders from the shop and marketplaces should end up as sales orders in Business One without manual work, with the shipment report to follow.
- Triggerthe shop's webhook or a schedule for the marketplaces
- Hand overas a sales order — for a collective customer, an existing customer with the order's e-mail address or an assigned customer number
- Read backdeliveries with tracking number
- Reportthe shipment to shop and marketplace
No order is re-entered by hand, none is created twice. An order cancelled in the shop cancels the sales order, as long as nothing of it has been delivered.
Good to know
What to know about SAP Business One
- PrerequisitesWhat has to be set up on your side.
- A reachable Service Layer
- A user of the company database
- SAP Business One on SAP HANA or on Microsoft SQL Server
- Not coveredWhat ConFlowIO does not write to SAP Business One.
- Items and prices are read but not written to Business One
- The same goes for stock — it comes out of Business One, not in
- Business partners are not created; the customer is an existing customer or a collective customer
- DurabilityApplies to this integration as to every workflow in ConFlowIO.
- Failed steps retry themselves
- Large reads are processed page by page, each page a step of its own
- A failed run is continued rather than started over
- Live logs per step, with credentials removed
Works well with
What works with SAP Business One
Frequent partners
Items, prices and stock out, orders in.
Contact
See SAP Business One on your own data
We are glad to show ConFlowIO on your own data. Bring a real slice of your items or orders.
The difference shows at real volumes — not at five sample records.
Would you like to read our whitepaper? Just say so in your enquiry and we will send it to you.
Rather write directly?info@conflowio.com