Help · Connectors and write-back
Read from your ERP. Write back only when you say.
Under Connectors an owner points the product at SAP, SAP Business One, Oracle, Dynamics, Zoho, a WMS or TMS, a SQL data lake, or any REST endpoint. Every connection is read-only unless write-back is switched on for it, and then only three approved actions ever leave.
Setting one up
A base URL, a sign-in, and the entity paths.
The named ERPs come with their published entity paths pre-filled — the standard services for S/4HANA, the Service Layer collections for Business One, the REST resources for Fusion. Every path is editable, because every installation differs, and confirming them against your gateway is the first task of any deployment. Test the connection reads one row from the cheapest entity rather than the service document, so a green result proves the sign-in, the authorisation and the path together.
Credentials are encrypted at rest and never shown back. An empty password field on a later edit means "leave it alone", not "delete it".
The scheduled sync
The same pipeline an upload goes through.
A sync pulls each entity on the schedule you set and runs the rows through the same mapping, validation and quality score an upload gets. It uses the mapping you confirmed; it never asks a model to guess one at three in the morning. A pull that scores below your threshold writes nothing, exactly as an upload would. The health job probes every connection on its own schedule and marks one that has stopped answering.
Write-back
Three actions, each already approved, per connection.
| ERP | Expedite | Cancel | Requisition |
|---|---|---|---|
| SAP Business One | Delivery date on the order | SAP's own Cancel action | A purchase request with one line |
| Zoho Inventory / Books | Delivery date on the order | Marked cancelled | Refused by name — Zoho has no purchase request, and a draft order needs a vendor a requisition does not name |
| SAP S/4HANA, Oracle, Dynamics, WMS, TMS | Read-only in this release | ||
The switch is on the connection's own form, off by default. With it on, an approved expedite, cancel or requisition is written to the ERP after it succeeds here. The order is found by the number you use — the PO number — not by an internal id, so an order that arrived by spreadsheet is found too. The approval card shows the ERP's reference on success; on a refusal it shows the ERP's own words and a Try the ERP again control. A temporary failure retries on its own; a final one — no such order, order closed — does not, and is listed for an owner to see. Your records here stand either way.
Safety stock, reallocation, rescheduling and promise dates are SIAARU's own planning parameters and are never written to an ERP.