ERP integration
Connect V5 to your ERP when you're ready.
Pick your ERP and follow six steps. SAP, NetSuite, Sage, Dynamics, Odoo and QuickBooks, plus a custom adapter.
ERP is optional and sits outside the trial. Run V5 on its own first, then connect.
Your ERP
Finance and planning
Items, BOMs, suppliers, orders
Receipts, movements, confirmations, quality results
V5
The shop floor
Which ERP do you run?
Pick your ERP adapter
Exact setup and credentials for each. The rest of the page updates to match.
Also supported via the custom adapter (14)
Epicor Kinetic · Infor CSI / LN / M3 · Acumatica · Workday · Xero · Oracle Fusion · Deltek Costpoint · Priority · Ramco · Unit4 · Made2Manage · ProcessPro · BatchMaster · Sage 50 / 100
Anything with REST, SOAP, ODBC or SFTP — pick "Custom / Other" and we scope it.
SAP · S/4HANA · ECC · connects via OData · RFC · CPI
How do we connect SAP?
Six steps, same shape every time
- 1
Pick your ERP adapter
You
Choose below; only step 2 changes per ERP. - 2
Set up a service user or app in SAP
Your IT / ERP admin
A service identity in SAP that V5 can authenticate as. - 3
Enter the credentials in V5
You + V5
V5 tests the connection and logs exactly what it can read and write. Nothing posted yet. - 4
Map your master data
You + V5
Items, BOMs, UoM, customers, suppliers, locations. V5 auto-matches keys; you approve crosswalks where codes differ. - 5
Dry-run sync (read-only)
V5 (you review)
V5 pulls masters into staging and validates missing UoM, duplicate SKUs, inactive vendors, invalid BOMs and code-length issues. Nothing reaches SAP. - 6
Go live — turn on write-backs
You sign off · V5 posts
Enable the flows you approve: POs and receipts, production confirmations, backflush, inventory moves, lot status, invoices.
Step 2 in SAP
- Pick the path with your Basis team: OData (S/4), RFC/BAPI (on‑prem ECC) or via PI/PO/CPI.
- Create a communication user (OAuth2 client for S/4 Cloud, basic auth for on‑prem) or a technical RFC user.
- Activate the services we need (e.g. API_PRODUCT_SRV, API_PURCHASEORDER_PROCESS_SRV, API_PROD_ORDER_CONFIRMATION) and transport if required.
- Open firewall/allowlist our IP range.
Sandbox first. Any new service exposure needs a transport.
What you'll need ready (step 3)
- Base URL or app/message server + system number + client
- Communication user / RFC user credentials (or OAuth client ID/secret)
- List of activated services or exposed BAPIs
Optional master data (step 4)
What flows which way?
ERP stays the book of record. V5 runs the floor.
From SAP → V5
Authoritative in ERP. Pulled into V5.
- Items & material masters
- Units of Measure + conversions
- BOMs (and routings, if ERP is master)
- Vendors / Suppliers and Customers
- Sites / Plants / Warehouses / Locations
- Purchase Orders & Sales Orders
From V5 → SAP
Captured on the floor. Posted to ERP.
- Goods receipts (GRN) against POs — lot/serial tagged
- Inventory movements, issues, adjustments with reason
- Production order confirmations: yield, scrap, time
- Backflush consumption of components
- Finished goods receipt + lot/serial creation
- Quality results driving release / hold / block
Bidirectional flows are possible by agreement — one master per object, always, to avoid loops.
What trips integration projects up?
Six things to settle before you start
- UoM Mismatches
- ‘EA' vs ‘Each' or missing conversions will block postings. Clean up before go‑live.
- Lot / Serial Formats
- ERPs often enforce length and pattern. Agree the generator and where it lives.
- Code Lengths & Special Chars
- Many ERPs cap to 20–40 chars and reject ‘/' or spaces. Tidy the keys first.
- Period locks & time zones
- Back‑dated movements may violate period locks. Align server time and fiscal calendar.
- Number Ranges
- Don't let V5 and ERP both mint the same document numbers. Pick one master.
- API Limits
- NetSuite governance, QuickBooks rate limits, BC requests/min. We throttle — but plan waves.
Scope your SAP connection
ERP is optional and sits outside the trial. Send your environment details when you're ready.