YARDtwin uses essential cookies for authentication and session management. We don’t currently set analytics or marketing cookies, but our cookie policy categorises them ahead of any future change. Read our Privacy Policy, GDPR Policy, and Cookie Policy.
SAP sends the delivery. YARDtwin books it, runs the gate, the dock and the digital twin — and posts the goods movement straight back with the material document number. Pre-configured, bi-directional, and switched on per site in about ten minutes.
Works with: SAP S/4HANA · SAP ECC · SAP EWM · SAP Integration Suite (CPI) · IDoc · BAPI · OData
SAP knows a truck is coming. It doesn't know the truck arrived late, sat 40 minutes at the gate, or left unloaded. YARDtwin closes that gap — and keeps SAP perfectly informed while it does.
Purchase orders, deliveries, stock and financials. SAP remains the single source of truth for the business — YARDtwin never duplicates the master data, it consumes the delivery and returns the goods movement.
Everything between the gate and the warehouse door: appointment scheduling, gate check-in with seal and cold-chain verification, a live digital twin of the yard, dock execution, and a GMP-grade audit trail.
Re-keying deliveries into spreadsheets, phoning the warehouse to ask if a truck arrived, and goods receipts posted hours after the physical unload. The loop closes automatically, in minutes.
This is not a mock-up. In five minutes you'll watch the 3-sync configuration switched on live in Site Admin, then two real journeys: SAP sends an inbound delivery, YARDtwin books it onto the schedule, the gate verifies the SAP-expected seal by photo, the digital twin tracks the truck to the dock, every handling unit is scanned and reconciled — and the goods receipt posts back to SAP with the material document number.
Then the other direction: SAP sends an outbound delivery for finished product, the trailer is loaded and sealed with a recorded chain of custody, the goods issue posts back, and the driver signs the departure on glass — 21 CFR Part 11 style.
Recorded against a live YARDtwin instance and a conformant SAP-side test endpoint. Every SAP message shown is genuinely sent, signed and acknowledged.
How much SAP sees of your yard is a one-click preset, not an integration project. Start light, mirror everything later — or the other way around. Changing mode is a configuration change, tracked in the audit trail.
SAP EWM Yard Management stays off. YARDtwin owns the whole yard, and only two things cross the boundary: the delivery coming down, and the goods movement going back.
Everything in 3-sync, plus YARDtwin mirrors yard execution into SAP EWM: check-ins register transport units, unloads confirm warehouse tasks, departures post yard exits.
Every sync point is also an individual per-site switch — default off, nothing crosses to SAP until you opt in.
Five sync points cover the inbound and outbound lifecycle. Each one speaks SAP's language on the SAP side and clean JSON on the wire — mapped, signed, retried and logged for you.
| Sync point | Direction | SAP object | Event |
|---|---|---|---|
| S1Delivery → booking | ↓ | Inbound / outbound delivery (VBELN) | sap_inbound_delivery |
| S2Check-in → transport unit | ↑ | Transportation unit (TU) | tu_register |
| S3Unload → warehouse task | ↑ | Warehouse task confirmation | wt_confirm |
| S4Goods receipt / goods issue | ⇅ | Goods movement (MBLNR) | goods_receipt · goods_issue |
| S5Departure → yard exit | ↑ | Yard exit | yard_exit |
Direction arrows: ↓ SAP → YARDtwin · ↑ YARDtwin → SAP · ⇅ bi-directional. Every row is an independent per-site switch, default off.
sap_inbound_deliveryInbound or outbound delivery — creates or updates the booking, keyed on the SAP delivery numbergr_statusSAP's goods-receipt acknowledgement, incl. the material document numbergi_statusSAP's goods-issue acknowledgement for outbound shipmentstu_registeredSAP's transport-unit reference written back to the bookingtu_registerTruck checked in at the gate — register the transport unitwt_confirmUnload complete — confirm the warehouse task with scanned handling unitsgoods_receiptGoods receipt with handling-unit reconciliation (matched / missing / extra)goods_issueGoods issue for finished-product shipments, with the applied sealyard_exitTruck departed — carries the Part-11 signature hashField mapping is built in — SAP identifiers are understood natively: VBELN · EBELN · LIFNR · MATNR · WERKS · NTGEW · MBLNR · HU / SSCC
YARDtwin does the work at the edge and exchanges signed JSON with the middleware you already run. Your SAP system needs no add-on, no ABAP, and no new infrastructure.
The same integration that moves your deliveries is engineered for pharma-grade scrutiny — because that's who it was built for.
Hand your SAP or CPI team a complete kit — not a discovery project. The wire contract is documented end to end.
Bring your SAP team. In a 30-minute demo we'll connect a test tenant live, run a delivery end to end, and walk through the wire contract together.