Fast WMS integrates two-way with SAP and Oracle so your ERP stays the system of record for finance and planning, while Fast WMS runs bin-level execution on the floor. Masters and orders can flow in from the ERP; goods receipts, transfers, and dispatches flow back out. This article outlines how a connection is set up and, importantly, how to test it safely before going live.
Because every environment differs, the connection details are configured with our team during onboarding. The steps below show what to prepare and the order to work in so the first sync goes smoothly.
Set up the connection
- Gather connection details. The ERP endpoint or interface (for example an SAP RFC/IDoc or web-service endpoint, or an Oracle interface), plus a service account with the right permissions.
- Map your masters. Align items, parties/customers, and — crucially — map each Fast WMS store and bin structure to the corresponding ERP plant, storage location, or warehouse.
- Choose the documents to exchange. Decide the direction of each: orders in from the ERP; goods receipt, stock transfer, and dispatch out from Fast WMS.
- Set posting rules. Confirm which ERP movement type or document each warehouse event should create, so a Fast WMS dispatch lands as the right delivery or billing document.
- Test in staging. Sync a handful of masters, then push one test goods receipt end to end and verify it in the ERP.
- Go live. Once a full cycle validates, enable live two-way posting for all transaction types.
See the full picture on SAP & Oracle integration. If you also run Tally for a group company, the same mapping discipline applies — see Tally integration and the troubleshooting guide on fixing Tally sync errors.
Planning an SAP or Oracle rollout?
Our integration team will scope the connection and mapping with you.
Get a demo