What SAP and Vikbot each do
SAP holds the orders. Vikbot's cameras and scanning check what physically happens on the floor: what was picked, packed and loaded. The integration joins the two, so the floor is checked against what SAP expects and SAP learns what was actually verified.
- SAP stays in place. Fusion Insight and Vikbot WMS integrate with the ERP without replacing it.
- Vikbot does the checking. Dispatch Tracker, DockBot, ScanBot and the other Vikbot systems verify items against the order and record the result.
What flows in each direction
From SAP to Vikbot
- The pick list or dispatch order. It says which items, and how many, should go out on a job. Vikbot checks every scanned or camera-identified item against it.
From Vikbot back to SAP
- Verified counts: what was actually checked and approved against the order.
- Exceptions: the wrong, short or excess items that were flagged.
- Photo proof: the photo and timestamp saved for each dispatch.
Which SAP documents and fields are used is agreed per project with the customer's SAP team, so this guide does not list SAP modules, objects or transactions.
How the connection is made
Vikbot connects to SAP over SAP APIs: OData services and BAPI/RFC calls. Which of them a project uses depends on the customer's SAP landscape and is decided with their SAP team. The AI checks run on a Vikbot-supplied edge computer on the customer's LAN, so the cameras and scanning do not depend on a cloud service.
Setup, step by step
- Site survey. The Vikbot team sees how orders and dispatches are handled today and where the checks will run.
- Agree the data exchange. With the customer's SAP team, agree which orders come into Vikbot, which results go back and whether OData or BAPI/RFC is used for each.
- Do the SAP-side work together. The Vikbot team and the customer's SAP team set up and connect their sides of the interface.
- Install and train. The cameras and the edge computer are installed, and the models are trained on the customer's items.
- Parallel run. Orders from SAP and results sent back are checked alongside the existing process before anything relies on them.
- Go-live. The timeline for these steps is set after the site survey.
Known limits
- It is not off the shelf. The SAP side is agreed per project, so it needs time from the customer's SAP team.
- The order must be right. Vikbot checks goods against the order SAP sends; an error in the order itself is not caught on the floor.
- No module list here. Specific SAP modules, objects and transactions depend on the project and are confirmed during setup, not in this guide.
Without an ERP link
An ERP link is not required to start. DockBot can run standalone from a spreadsheet of dispatch orders instead of an ERP link. For how the checks themselves work, see how QR scanning and dispatch verification work and how camera-based inventory counting works; for other guides, see all implementation guides.