ERP and distribution
SalesPro Hub has an SAP Business One Service Layer adapter in controlled preview, disabled by default and available only through an approved Enterprise implementation. It can read business partners, items and orders and contains a retry-safe order-posting path, but automatic Hub-to-SAP order publication is not enabled as a general production feature. Public support requires representative SAP company-database acceptance, mapping sign-off and reconciled release evidence.
Test the field workflow firstSupport level: Enterprise controlled preview — activation and acceptance approval required. The workflow below separates shipped SalesPro Hub capabilities from connector work your implementation must provide.
What this solves
The intended South African distribution pattern places the managed connector where it can reach the customer’s SAP Business One Service Layer over HTTPS while continuing to call SalesPro Hub outbound. The adapter establishes a company-database session, follows paged Service Layer responses and maps stable customer, item and order identities into the hub. A controlled order path preserves the SalesPro Hub order number as the correlation reference before accepting an SAP document result. The page distinguishes that implemented preview capability from an activated production integration: company database, warehouse, tax, price-list, user-defined field and approval behaviour still need proof against the buyer’s real SAP Business One edition and operating rules.
SAP Business One integration evidence
A useful SAP Business One connection needs stable identities, explicit ownership and a visible exception path. These are the SalesPro Hub records the implementation must map and reconcile.
Written and maintained by Paul · Updated 7 August 2026
The managed service calls SalesPro Hub outbound while reaching the approved SAP Business One Service Layer endpoint inside the customer network.
Only submitted and approved field orders should enter the controlled posting path, retain one source reference and receive a durable SAP result.
Business-partner, item, warehouse, price-list, tax, address and user-defined-field decisions need buyer approval before a preview becomes supportable.
A lost response after commit must lead to an external lookup using the stable source identity, not an unsafe second sales-order request.
Authentication expiry, version drift, retries and permanent mapping failures need distinct states and owners instead of an invisible background task.
The controlled preview should remain disabled until stakeholders reconcile counts, quantities, values, tax, identities, replay behaviour and exception ownership.
Architecture and ownership
The controlled-preview pattern uses SAP Business One Service Layer over HTTPS from a customer-approved connector host. The connector authenticates to one company database, reads paged business-partner, item and order data, and keeps the session cookies out of ordinary logs. SalesPro Hub remains the field workflow. A bounded order-posting path may use the field order number as an approved SAP source reference, but automatic production publication stays disabled until the Hub producer, customer mapping and representative acceptance gate are complete.
SAP Business One normally owns the official business-partner code, item code, warehouse and accounting document identity after the external transaction is committed.
SalesPro Hub owns mobile drafts, visit context, the submitted field order and the stable source operation before an SAP hand-off.
The buyer must assign one owner for price lists, discounts, VAT, available stock, ship-to addresses and fulfilment status instead of enabling implicit two-way updates.
User-defined fields, approval procedures and partner extensions are customer-specific contract items and cannot be inferred from a generic Service Layer schema.
Use a dedicated least-privilege SAP Business One service user restricted to the approved company database and operations. Protect the Service Layer password as a write-only managed secret, keep session cookies in memory, verify HTTPS certificates and record proxy or TLS-inspection behaviour. The Windows service should initiate hub traffic outbound and expose no arbitrary remote command path. Review SAP licensing, partner requirements, audit retention, secret rotation and the local break-glass owner before activation.
Failure recovery
A useful SAP Business One integration is not defined by one successful demo. It is defined by what remains durable, what can be replayed safely, what must stop, who sees the exception and how both systems are reconciled.
| Failure or conflict | Required response |
|---|---|
| Service Layer session expires | Perform one controlled re-login, replay the same read or idempotent operation and stop visibly if authentication still fails. |
| Unknown item, warehouse or tax code | Quarantine the permanent mapping error with the exact external identity; never guess a similar code. |
| Response lost after SAP commit | Query by the approved stable source reference and reconcile the existing DocEntry or DocNum before another create request. |
| Service Layer or network unavailable | Keep the operation durable, apply bounded retry and retain its identity across connector and machine restarts. |
| Company configuration changes | Validate a versioned candidate setting locally and preserve the previous known-good configuration for controlled rollback. |
Acceptance plan
A sandbox proves API syntax. Production readiness requires representative identities, accounting or CRM rules, failures and reconciliation. Record the result against the exact product edition and adapter release; do not transfer evidence from a different vendor version by assumption.
Delivery lifecycle
Treat the connection as a small operational product with owners, release evidence and a lifecycle. These phases stop a promising prototype from becoming an invisible production dependency that only one developer understands.
Name the exact SAP Business One product, edition, company or tenant, licensed interface and deployment. Follow one representative customer and order from field capture to its final external state. Record current manual checks, approval points, cut-off times, volumes and the people who resolve errors. Brand-level assumptions are not a technical scope.
List required and optional fields, types, formats, allowed values and stable identities. Declare a source of truth for customers, outlets, products, prices, tax, stock, documents and status. Define create, update, deactivate and delete behaviour separately. Include the idempotency key, cursor or event identity and the external reference returned after a successful commit.
Classify authentication, rate-limit, connectivity, validation, mapping, conflict and external-service errors. Decide which faults retry, how often and with what backoff; which stop immediately; and where exhausted work becomes visible. Assign a named business or technical owner and define the evidence needed to replay, correct, reject or manually reconcile an operation.
Use representative South African customers, addresses, SKUs, rand values, VAT rules, discounts, warehouses and approval cases. Include duplicates, missing mappings, offline or network loss, service restart, expired credentials and a lost response after external commit. Reconcile counts and commercial totals in both systems; a green API response alone is not acceptance.
Version the mapping, adapter and configuration together. Record the approved package, supported architectures, required runtime, database or API prerequisites and the previous known-good state. Start with a bounded customer or order cohort, monitor exceptions and keep a tested way to pause new work without deleting the durable queue or losing reconciliation evidence.
Monitor reachability, authentication, latency, retry and dead-letter trends, external rate limits, installed version and reconciliation differences. Rotate credentials and exercise recovery before an emergency. Review vendor API or SDK changes and the adapter support matrix before upgrades. Retire obsolete credentials, mappings and data under the agreed security and POPIA operating process.
Decision-maker intent
SAP partner and ERP owner
No public support claim is made. The adapter is a controlled preview using Service Layer and stays disabled until the exact company environment and reconciled acceptance evidence are approved.
Finance and operations
Not as a generally enabled feature today. The preview contains an external order path, but the Hub producer, mapping, approval and end-to-end acceptance gate must be completed first.
CTO, CIO and security
The managed service calls the hub outbound and reaches the approved Service Layer endpoint. The review should verify service-user permissions, secret protection, certificates, destinations, logs, session behaviour and local recovery ownership.
Development and support
The design keeps a stable order identity, reconciles after a lost response and permits only one controlled re-authentication before raising a visible exception.
Professional includes scoped APIs and signed webhooks for custom, customer-operated middleware. A managed Windows connector, remote configuration, heartbeat/version monitoring and managed recovery require Enterprise—and only become available for this named system after its real adapter passes the published release boundary.
Buyer decision guide
A good trial should prove the workflow with your data—not rely on a sales promise.
Implementation flow
Record the SAP Business One version, platform, company database, Service Layer endpoint, licensed access, certificates, service user and relevant partner or change-control requirements.
Assign ownership for business partners, ship-to addresses, item codes, warehouses, prices, VAT, available stock, field orders, SAP documents and fulfilment status.
Exercise active and inactive customers, items, warehouse codes, price lists, tax treatment, discounts, currencies, user-defined fields and approvals before enabling transaction work.
Read approved master data and orders, then post only a bounded set of authorised field orders using the stable source reference and a visible exception path.
Expire the Service Layer session, interrupt the network, restart the connector and lose a response after commit; confirm that work recovers without creating a second SAP order.
Finance, operations, SAP administration and IT compare source and external counts, quantities, values, tax, references and exceptions before the adapter is activated for the tenant.
| SalesPro Hub field/event | SAP Business One equivalent | Implementation note |
|---|---|---|
| customer.external_id | BusinessPartners.CardCode | Use the immutable SAP business-partner code, not the display name. |
| items[].sku | Items.ItemCode | Validate inactive items, units and warehouse availability before order release. |
| order_number | Orders.NumAtCard or approved source field | Preserve one stable source reference for replay lookup and reconciliation. |
| external_reference | Orders.DocEntry and DocNum | Return the durable SAP identity only after the external commit can be reconciled. |
| items[].quantity | DocumentLines.Quantity | Reconcile unit-of-measure conversion and partial fulfilment rules. |
| outlet.address | Approved ship-to address code | Do not infer a ship-to location from free-text address similarity. |
| stock_qty | Agreed warehouse available quantity | Define the warehouse set, refresh timing and owner of stock deductions. |
There is a Service Layer adapter in controlled preview, disabled by default. It is not advertised as generally supported until a representative SAP environment, customer mappings and the full reconciled acceptance suite pass for an approved Enterprise release.
The preview adapter contains a retry-safe external order path, but automatic Hub-to-SAP publication is not enabled as a general production feature. The producer, tenant approval, mapping and acceptance gate must be completed before activation.
The managed runtime calls SalesPro Hub outbound. It still needs customer-network access to the approved SAP Business One Service Layer endpoint, with the customer’s certificate, proxy and firewall policy applied.
The preview client keeps the Service Layer session cookies in memory and permits one controlled re-login after an unauthorised response. Repeated authentication failure stops and becomes an operational exception.
The design retains the SalesPro Hub order number as a stable source reference, persists the operation identity through retries and reconciles an existing external result before another create attempt. The exact SAP field and uniqueness checks are approved in the pilot.
Validate the Service Layer endpoint, company database, service-user permissions, outbound destinations, credential storage, logging, UDF and approval mappings, idempotency lookup, support ownership, upgrade path and reconciled evidence for the intended SAP version.
Connected buying journey
Review the managed runtime, ERP, accounting, CRM and automation options before choosing a delivery model. Every page publishes its current support boundary, required custom work and Enterprise plan status.
Import real products and customers, capture a representative order, then scope the integration against evidence instead of assumptions.