RFID + SAP Integration: The Patterns That Work
RFID is generating thousands of events per minute on a busy dock. SAP is not designed to be hit thousands of times per minute. The integration architecture between the two is the most under-engineered part of most RFID rollouts.
The Settlement Model
Raw reads do not become SAP postings. Movement events become SAP postings. A movement event is a deduplicated, business-meaningful action like "Pallet X moved from Zone A to Outbound Dock 3 at 14:32 IST". The middleware’s job is to turn 50 reads into 1 movement event.
The Three Integration Patterns
- Outbound dispatch — RFID confirms the load against the delivery, settles, then posts goods issue via IDoc.
- Inbound receipt — RFID confirms the truck against the inbound delivery, settles, posts goods receipt via BAPI.
- Cycle count — RFID handheld scans the zone, differences are posted as physical inventory documents via OData.
Failure Handling
Every integration must survive three failure modes:
- Reader fails — system rolls over to barcode + handheld with audit trail.
- SAP unavailable — movement events queue for up to 72 hours, settle when SAP returns.
- Network partition — edge node continues to capture, dashboards continue to read, ERP catches up on heal.
Practitioner note
A well-architected RFID-SAP integration runs at 99.95% availability with two-nines accuracy. A naive integration breaks during the first warehouse busy hour and never recovers trust.
Frequently asked
IDoc, BAPI or OData — which is right?
For inventory postings, IDocs with retry queues. For master data sync, OData. For complex transactional flows, BAPIs wrapped in a service layer.
Amey Kadle
Founder & CEO, Ajinkya Technologies. 20+ years of building MES, ERP and AI systems for India’s most demanding manufacturing plants.