One Inbound Delivery, End to End: YARDtwin on a Live SAP EWM System

In August we published a video that replayed the five sync points between SAP and YARDtwin, message by message. It was honest about what it was: a live run, with the SAP screens illustrated. The obvious follow-up question was what the same flow looks like on a real SAP system, in the hands of an SAP consultant. This film is the answer. It was made by YUS Partners, our implementation partner, on their own SAP S/4HANA and SAP EWM landscape, with YARDtwin running on a standard demo site.

It follows one inbound delivery for a little over three minutes: created in SAP, distributed to EWM, booked, checked in, weighed, unloaded and signed out in YARDtwin, then received in EWM. Each hand-off is shown on the screen where it happens, and the same delivery number is visible in both systems from the first minute to the last.

The scenario, stated up front

The film opens with the configuration it demonstrates, because the integration is a set of per-site switches rather than one fixed product. In this scenario SAP EWM owns warehouse execution and inventory posting. YARDtwin owns the yard: appointment, gate, weighbridge, dock and departure. Weighbridge processing is part of the inbound flow. Another site would pick a different mix; this is one of them, and the film says so before it starts.

Steps 1 and 2: one delivery, two systems, nothing typed twice

An inbound delivery is created in SAP S/4HANA against a purchase order: one line, a small fast-moving part, 1,000 kg. On save, two things happen in parallel. Standard SAP distribution creates the corresponding inbound delivery in EWM, and the integration creates the appointment in YARDtwin. The SAP delivery number travels with it, so the planner looking at the appointment on the YARDtwin schedule and the EWM user looking at the warehouse monitor are looking at the same reference.

That reference is the thread through the whole film. Every later event, from the gate to the goods receipt, is tied back to it without anyone typing it a second time.

Step 3: the gate check-in becomes a transportation unit in EWM

The truck arrives and is checked in at the YARDtwin gate: paperwork checklist, seal check, and the gross weight from the weighbridge, read automatically from the bridge or keyed by the operator. The gate records the gross; the net is verified at gate-out. Entry is authorised and the driver is sent to a dock.

At that moment YARDtwin sends the check-in event to SAP EWM. EWM creates the transportation unit, assigns the inbound delivery to it and records arrival at the checkpoint. The film shows the EWM delivery with its transportation unit attached a few seconds later, created by the integration user, not by a person at a desk. That checkpoint arrival is what allows the goods receipt to be processed downstream.

Step 4: the yard work stays in YARDtwin

From the gate the truck is directed to its dock. The dock board, the unloading screen and the close-out all run in YARDtwin: appointment status, dock activity and unloading progress on one workflow, with the pallet scans and the evidence captured at the dock. SAP EWM is not involved in any of it, and that is the point of the split. As the film puts it, no SAP transaction is required for a yard-internal activity.

Steps 5 and 6: departure releases the goods receipt

Unloading is completed in YARDtwin and the truck moves to the departure gate. There it is weighed out: 15,000 kg in, 14,000 kg out, 1,000 kg delivered, matching the delivery line to the kilo. The driver signs on screen, the departure is cleared, and a SHA-256 hash of the record is kept for the audit trail.

Only then does YARDtwin send the goods receipt event to SAP EWM. EWM resolves it to its own inbound delivery and runs goods-receipt processing. The last SAP screen in the film shows that delivery with goods receipt status Completed. One delivery, one flow, two systems, and SAP still the system of record for the stock.

What this is worth

• The SAP side is real. The transportation unit, the delivery assignment and the goods receipt status are standard EWM objects on a standard system, created by messages from the yard. No custom transaction, no re-keying.
• The split is clean. EWM keeps warehouse execution and inventory. YARDtwin keeps the physical truck: appointment, gate, weighbridge, dock, departure. Nobody reconciles the two with a spreadsheet.
• The weighed quantity is the received quantity. The goods receipt is released after the weigh-out, so the net from your own bridge is the figure that reaches SAP, signed before the truck leaves.
• The evidence rides along. Checklist, seal, weights, pallet scans, driver signature and hash exist in YARDtwin for every receipt, and the SAP delivery number ties them to the document SAP already owns.
• Your integration partner can run it. The film was built and narrated by an SAP consultant on their own system, against YARDtwin's published webhook messages. For an integration, that is the test that counts.

Where this sits in the integration

In the language of our earlier post, the film shows three of the five sync points crossing the boundary: the inbound delivery coming down, the transportation-unit registration at check-in, and the goods receipt going back after the weigh-out. The warehouse-task confirmation at unload and the yard-exit message are left out of this scenario. Every one of the five is a per-site switch, so the same connection can run the lighter three-message shape or the full five without a new project.

The message catalogue and the architecture are on our SAP integration page. The message-by-message replay is in One Integration, Five Sync Points.