Integration
SAP RFID integration
Our RFID readers talk to SAP directly over SAP IoT, or through Engine when a read needs checking first. S/4HANA, ECC and Business One.
Overview
The RFID layer for SAP.
SAP knows what you bought. It finds out what arrived when somebody types the GRN, which at a busy plant is the next morning. A cement plant we work with carries 30,000+ material codes in SAP, and its stores were running at 85% inventory accuracy because of that gap.
We close it at the gate. With Engine in the path, a truck with an RFID tag on the windscreen is identified by the reader as it rolls in, matched to the purchase order, weighed on the scale, and the GRN posts to SAP when QC approves. Nobody retypes anything.
How RFID and SAP fit together
Our RFID reader is a UHF Gen2 unit with an Impinj E710 module. It reads up to 700 tags a second and about 15 metres at a dock door. There are two ways to get a read into SAP, and only one of them involves Engine.
Straight to SAP IoT. The reader talks directly to SAP over SAP IoT. No IoTReady software sits in the path, so there’s nothing extra to host or license. If all you want is tag reads inside SAP, this is the short route.
Through IoTReady Engine. Engine is optional. Add it when SAP shouldn’t hear about every read as it comes: when a tag read has to be matched to a PO, a weight checked on the scale, or a QC approval waited for before a GRN posts. Readers, scanners, scales and sensors all write the same kind of event into Engine, and one connection carries the checked result to SAP.
Plenty of sites start direct and add Engine for the flows that need rules. The reader doesn’t change.
- Goods receipt. Tag read, PO matched, weight checked, GRN posted.
- Material tagging and binning. Each tagged item is put away to a bin and the bin is in SAP.
- PI/PV. A physical inventory is a walk with a handheld reader. It drops from weeks to days.
- Material issue. Whatever leaves the store is read on the way out and the reservation closes itself.
The IoT side
Readers aren’t the only source. With Engine in the path, a weighbridge, a bin scale, a temperature probe on a cold store: each one is a device that reports into the workspace, and a rule in Engine turns a reading into a SAP document. One mistyped weight is cheaper to stop at the scale than to find in the ledger.
The AI side
If you use Engine, it has an AI builder called the Engineer. Describe the flow you want in plain language (“when a GRN is approved, post it to SAP and flag any weight over 2% off the PO”) and it sets up the rule. You review it before it runs.
You can also connect Claude or ChatGPT to your workspace and ask it which purchase orders are late or what’s sitting in the receiving bay. It answers from live data, as you. See AI connectors.
What the Engine connection needs
The direct route to SAP IoT is configured on the reader. The rest of this section is for the Engine route.
- The base URL of your OData or REST service
- A service user and password
- The SAP client number
SAP usually sits behind a firewall, so the connection goes through a tunnel that we set up with you. Write to us and we’ll do it together. The full steps are in Connect your ERP.
Read next
Next step
Tell us what you are trying to trace.
Describe the flow: what arrives, what happens to it and what leaves. We will tell you what it takes to capture it.
or write to [email protected]