Skip to main content
Owlery retrieves SAP Business One orders through the Service Layer, follows related partners and warehouses, and converts the results into Owlery freight orders.

​
Synchronized records

Mapped data can include document numbers and identities, open or closed status, timestamps, customer or supplier details, warehouses, addresses, dates, item codes, descriptions, quantities, line numbers, prices, totals, units, notes, purchase-order references, bill of lading, tracking, PRO, and carrier values.

​
Delivery-note enrichment

SAP Business One may add shipment information to a Delivery Note without updating the source Sales Order. Owlery handles both paths:
  • During sales-order processing, Owlery queries linked delivery lines and applies available references.
  • After the main incremental sync, Owlery scans recently changed delivery notes and refreshes affected sales orders.
Large lookups are chunked to stay within Service Layer URL limits. Explicit page sizes prevent matching delivery records from being omitted by default API limits.

​
Synchronization and reliability

  • Pagination processes large order sets in bounded pages.
  • Incremental watermarks order changed transactions by SAP update date.
  • Delivery lookback includes a buffer around date-only delivery updates.
  • Reference caching avoids repeatedly requesting the same partner or warehouse.
  • Targeted retries retry selected supporting-record lookups after temporary failures.
  • Chunked enrichment keeps delivery and order lookups within request limits.
  • Exact refresh retrieves the current source record for reconciliation.
  • Shipment-reference lookup can find a linked sales order by delivery tracking or bill of lading.
The current connector reads SAP Business One data into Owlery. It does not write fulfillment, receipt, quote, or shipment updates back.