GS1 EPCIS 2.0 & SAP S/4HANA Certified Architecture

Enterprise SAP RFID Integration for S/4HANA & Business One

Bridge physical dock door portals and industrial conveyor readers directly into SAP S/4HANA, EWM, and Business One. Decompose 96-bit GS1 SGTIN EPC tags into validated material documents, automated Goods Movement 101 postings, and serialized audit trails.

EPCIS 2.0
GS1 Standard Events
BAPI / OData
Native SAP Protocols
SGTIN-96
Silicon Decomposition
<250ms
Material Doc Commit
SAP RFID integration solution for seamless automation
Silicon to SAP Master Resolution

How RFID EPC Tags Map to SAP Materials (MATNR)

Physical RFID chips do not store verbose descriptions. They encode a binary 96-bit SGTIN identifier. Our edge gateway decomposes the binary stream into enterprise GS1 and SAP entities:

Header (8b)
Filter (3b)
Partition (3b)
Company Prefix (24b)
Item Reference (20b)
Serial Number (38b)
00110000
001
101
8901234
56789
100045892
SGTIN-96 Standard
Point of Sale Item
Partition Config
Enterprise GS1 ID
SAP Material # (MATNR)
Unique Unit Serial
Industrial Gate Physics

Rejecting Adjacent Dock Door Cross-Reads

In enterprise distribution centers, dock doors are spaced only 3–4 meters apart. Without edge filtering, an RFID portal at Dock Door 3 will accidentally capture tags passing through Dock Door 4. OpenRFID applies multi-variable physics filtering:

1

RSSI Signal Gradient

Tags in the active portal exhibit a steep Bell-curve signal trajectory exceeding -55 dBm. Crosstalk from neighboring doors remains diffuse below -72 dBm and is stripped at the hardware buffer.

2

Phase Angle Delta (Δθ)

As a forklift transits through the portal, the radio wave phase angle rotates predictably (Δθ = 2π × 2d / λ). Tags on stationary pallets or adjacent doors produce zero phase rotation and are suppressed.

3

Beam-Break Interlock

Industrial retro-reflective photo-eye sensors mounted on the dock frame trigger RF transmission only when the vehicle body enters the portal, eliminating continuous RF pollution.

Global Supply Chain Compliance

GS1 EPCIS 2.0 JSON-LD Supply Chain Event Schema

Our gateway serializes pallet transactions into W3C JSON-LD EPCIS 2.0 events for SAP Advanced Track and Trace (ATTP) and global regulatory compliance:

epcis_pallet_aggregation_event.jsonld application/ld+json (EPCIS 2.0)
{
  "@context": ["https://ref.gs1.org/standards/epcis/2.0.0/epcis-context.jsonld"],
  "type": "EPCISDocument",
  "schemaVersion": "2.0",
  "creationDate": "2026-09-12T11:45:00.000Z",
  "epcisBody": {
    "eventList": [
      {
        "type": "AggregationEvent",
        "eventTime": "2026-09-12T11:44:32.410Z",
        "eventTimeZoneOffset": "+05:30",
        "parentID": "urn:epc:id:sscc:8901234.0001847291",
        "childEPCs": [
          "urn:epc:id:sgtin:8901234.056789.100045892",
          "urn:epc:id:sgtin:8901234.056789.100045893"
        ],
        "action": "ADD",
        "bizStep": "urn:epcglobal:cbv:bizstep:packing",
        "disposition": "urn:epcglobal:cbv:disp:in_progress",
        "readPoint": { "id": "urn:epc:id:sgln:8901234.00001.DOCK_04" },
        "bizLocation": { "id": "urn:epc:id:sgln:8901234.00001.0" },
        "bizTransactionList": [
          { "type": "urn:epcglobal:cbv:btt:po", "bizTransaction": "PO-992014" }
        ]
      }
    ]
  }
}
          
Enterprise Connectors

SAP S/4HANA (BAPI RFC) & Business One (Service Layer) Connectors

Depending on your SAP platform, our gateway executes the appropriate native transaction interface:

SAP S/4HANA & ECC 6.0 RFC BAPI / OData

BAPI_GOODSMVT_CREATE

Executes Goods Movement 101 (Receipt against Purchase Order) or 311 (Plant-to-Plant Transfer) with handling units and serial number assignments directly in SAP core.

GOODSMVT_CODE = '01'
GOODSMVT_HEADER-PSTNG_DATE = '20260912'
GOODSMVT_ITEM-MOVE_TYPE = '101'
GOODSMVT_ITEM-MATERIAL = 'MAT-8901234'
GOODSMVT_ITEM-ENTRY_QTY = 50
GOODSMVT_SERIALNUMBER = ['SN1001', 'SN1002']
SAP Business One Service Layer REST

POST /b1s/v2/InventoryGenEntries

Connects via HTTPS REST with B1SESSION cookie auth. Automatically converts dock door scan bursts into Goods Receipts with serialized lot allocation.

POST /b1s/v2/InventoryGenEntries
{
  "DocDate": "2026-09-12",
  "DocumentLines": [{
    "ItemCode": "ITEM-001",
    "Quantity": 20,
    "WarehouseCode": "WH01"
  }]
}
sap_b1_service_layer_gateway.py
Python 3.10+ / requests & session pooling
import requests
from typing import List, Dict, Any

class SapB1ServiceLayerClient:
    """
    Connects to SAP Business One Service Layer via HTTPS.
    Maintains session state and executes automated Inventory Goods Receipts from RFID bursts.
    """
    def __init__(self, base_url: str, company_db: str, username: str, password: str):
        self.base_url = base_url.rstrip('/')
        self.company_db = company_db
        self.username = username
        self.password = password
        self.session = requests.Session()
        self.session.verify = True

    def login(self) -> bool:
        login_url = f"{self.base_url}/b1s/v2/Login"
        payload = {
            "CompanyDB": self.company_db,
            "UserName": self.username,
            "Password": self.password
        }
        res = self.session.post(login_url, json=payload, timeout=10)
        return res.status_code == 200

    def post_goods_receipt(self, warehouse_code: str, items: List[Dict[str, Any]]) -> Dict[str, Any]:
        endpoint = f"{self.base_url}/b1s/v2/InventoryGenEntries"
        doc_lines = []
        for it in items:
            line = {
                "ItemCode": it["item_code"],
                "Quantity": it["quantity"],
                "WarehouseCode": warehouse_code,
                "SerialNumbers": [{"InternalSerialNumber": sn} for sn in it.get("serials", [])]
            }
            doc_lines.append(line)

        payload = {"DocumentLines": doc_lines}
        res = self.session.post(endpoint, json=payload, timeout=15)
        if res.status_code in [200, 201]:
            return {"success": True, "doc_entry": res.json().get("DocEntry")}
        return {"success": False, "error": res.text}
          

Frequently Asked Questions: SAP RFID Integration

Technical guidance for SAP solution architects, ABAP developers, and supply chain directors.

How does physical RFID tag data map into SAP Material Masters?
UHF RFID chips store standardized GS1 binary identifiers (such as SGTIN-96). Our OpenRFID edge gateway parses the 96-bit binary payload, extracting the GS1 Company Prefix, Item Reference (GTIN/SKU), and unique 38-bit item Serial Number, resolving it instantly to your internal SAP Material Number (MATNR).
How does RFID integrate with SAP Extended Warehouse Management (EWM) and Handling Units?
OpenRFID connects to SAP EWM via native RFC function modules or OData v4 REST APIs. Fixed dock portals scan incoming or outgoing pallets, automatically verifying EPC Gen2 tags against Handling Units (HUs), Inbound Deliveries, and Warehouse Orders, triggering automated BAPI_GOODSMVT_CREATE postings without manual barcode scanning.
Does integrating RFID require modifying standard SAP ABAP tables?
No. The middleware communicates via standard SAP BAPIs (such as BAPI_GOODSMVT_CREATE) and the SAP Business One Service Layer. All physical EPC-to-Material mappings occur at the OpenRFID middleware edge, meaning zero invasive ABAP table modifications, no core modifications, and complete compatibility with standard SAP upgrades.
What is the difference between integrating SAP S/4HANA vs. SAP Business One?
For SAP S/4HANA and ECC 6.0, the middleware connects via native RFC function modules (BAPI_GOODSMVT_CREATE) or OData v4 REST (API_MATERIAL_DOCUMENT_SRV) with support for Handling Units (HU). For SAP Business One, the connector communicates via the high-speed SAP Service Layer REST API (POST /b1s/v2/InventoryGenEntries).
Does the gateway support GS1 EPCIS 2.0 event standards?
Yes. For global supply chains and regulatory compliance (pharma DSCSA and automotive VDA), our middleware models dock door reads as EPCIS 2.0 JSON-LD ObjectEvents and AggregationEvents, recording what, when, where, and why (bizStep: receiving/shipping).
How do you prevent SAP from crashing when scanning 1,000+ tags per second at dock doors?
High-speed dock doors generate intense burst traffic. The gateway implements an edge Disruptor ring-buffer with a 3-second debounce filter. Duplicate tag reads are filtered at the edge, and only validated, deduplicated SKU batches are dispatched to SAP in throttled, idempotent transactions.
Can RFID automate SAP Goods Movement 101 and 311 postings?
Yes. Upon pallet transit through an RFID dock portal, the middleware validates the EPC tags against the Advanced Shipping Notice (ASN) or Inbound Delivery, executing BAPI_GOODSMVT_CREATE with GM_Code 01 (Mvt 101 Receipt) or GM_Code 04 (Mvt 311 Transfer) automatically.
How do you prevent cross-reads between adjacent dock doors?
Our edge gateway analyzes multi-antenna phase angle progression (Delta theta) and RSSI thresholds. Tags passing through the primary dock portal exhibit characteristic Doppler and phase transitions, while reflections from adjacent doors remain static and are rejected by the directional filter.

Deploy Enterprise SAP RFID Architecture

Our certified integration team provides complete end-to-end implementation for SAP S/4HANA, EWM, and Business One. Includes fixed portal installation, high-speed LLRP daemons, and custom ABAP/BAPI connectors.