Skip to content

Accounting & ERP

SAP Business One.
Keep your ledger. Connect the floor.

Keep SAP Business One as your financial system and connect the warehouse records your team needs.

Responsibilities

Agree where each record belongs.

Conceptual illustration: An accounts desk and warehouse shelf linked by a narrow channel carrying record tabs.

Agree which system owns each record. A two-way integration does not mean every record can be edited in both places.

What flows where

Scope the records in each direction.

These are proposed flows for scoping, not a promise that every object or event is already supported.

Conceptual illustration: An active record tray, storage cartridge and archive drawer with a shared record marker.
SAP Business One: records, direction and setup requirements
RecordFrom → toTriggerScope note
Business partners (customers + suppliers)SAP Business One → OpsUIAgreed during scopingProposed flow. Account-level support must be confirmed.
Item master recordsSAP Business One → OpsUIAgreed during scopingProposed flow. Account-level support must be confirmed.
Chart of accounts (read-only)SAP Business One → OpsUIAgreed during scopingProposed flow. Account-level support must be confirmed.
Purchase orders and goods receiptsSAP Business One → OpsUIAgreed during scopingProposed flow. Account-level support must be confirmed.
Sales orders and deliveriesOpsUI → SAP Business OneAgreed during scopingProposed flow. Account-level support must be confirmed.
A/R invoices and payment eventsOpsUI → SAP Business OneAgreed during scopingProposed flow. Account-level support must be confirmed.
Inventory movements and adjustmentsOpsUI → SAP Business OneAgreed during scopingProposed flow. Account-level support must be confirmed.
Fulfilment and dispatch eventsOpsUI → SAP Business OneAgreed during scopingProposed flow. Account-level support must be confirmed.

Set up the connection around your operation.

Conceptual illustration: A disconnected storage module, a second available module and records waiting for review.
  1. Confirm access

    Confirm your SAP Business One product, version and account access.

  2. Agree the mapping

    Agree record ownership, field mapping and the initial data load.

  3. Test the handoff

    Test successful updates, rejected records, duplicates and recovery before enabling production.

Questions about SAP Business One.

Do I have to replace SAP Business One?

No. SAP Business One stays your system of record for finance and accounting. OpsUI adds the warehouse, picking, packing, and dispatch layer on top and syncs back to B1, so you avoid an SAP EWM add-on project or a risky migration.

Is the SAP Business One connector live and self-serve today?

It is delivered during your rollout rather than as a self-serve download, because B1 deployments and add-ons differ and the sync is scoped to yours. The rest of OpsUI runs in production today and can run standalone alongside SAP Business One in the meantime.

Is OpsUI an SAP partner or reseller?

No. OpsUI is an independent ANZ product, not an SAP partner or reseller. The connector lets you keep your existing SAP Business One licence and partner relationship while adding OpsUI as the operations layer on top.

Your next step

Bring your system. Map the connection.

Share the account or version you use, the records that matter and the exceptions your team needs to handle.

Back to all integrations