Skip to content

Playbook

Warehouse and material flow

Inbound to goods issue, including the handover to automation. SAP EWM with Material Flow System removes a layer most warehouses do not realise they are paying for twice.

  • SAP EWM
  • SAP MFS
  • Odoo Inventory

The process

What the standard flow looks like.

  1. 01

    Inbound

    Advance notification, unloading, counting against expectation. Discrepancies are recorded here or they are argued about later.

  2. 02

    Putaway

    Storage control decides where stock goes, by product characteristics, velocity and the constraints of the physical building.

  3. 03

    Storage and slotting

    Fast movers near despatch, slow movers out of the way. Slotting is not a one-off exercise; demand moves and the layout should follow.

  4. 04

    Replenishment

    Pick faces are topped up from reserve before they run dry, triggered by thresholds rather than by someone noticing.

  5. 05

    Pick and pack

    Waves group work so a picker walks once for several orders. Two-step picking separates bulk retrieval from order sortation where volume justifies it.

  6. 06

    Despatch

    Staging, loading and goods issue. Stock leaves the books at the moment it leaves the building, not the next morning.

Failure modes

Where we expect to find it broken.

A separate WCS means two sets of master data
The warehouse system and the automation controller each hold a model of the building. They drift, and every bin change becomes two changes — or one change and a bug.
Exceptions at the automation boundary have no owner
A tote jams or a telegram is rejected. The warehouse system believes the move succeeded, the conveyor knows it did not, and reconciliation is somebody walking the aisle.
Slotting was set at go-live and never revisited
The product mix that justified the layout is three years old. Travel distance climbs gradually enough that nobody attributes it to anything.
Wave planning is a person with a view of the day
It works, and it depends entirely on that person. Their holiday is visible in the despatch numbers.

Scope

What is standard, and what is the actual work.

The distinction matters commercially. Paying to build what the platform already does is the most common way an ERP budget is wasted.

Out of the box

  • Inbound, putaway, picking, packing and goods issue process types
  • Storage control, both process-oriented and layout-oriented
  • RF transactions for every physical step
  • Wave management, replenishment and physical inventory
  • MFS communication with PLC-controlled equipment via telegrams
  • Resource and queue management for labour and equipment

Configured or built

  • The warehouse structure itself — storage types, sections, bins, activity areas
  • Putaway and removal strategies, which are where most of the throughput lives
  • Wave templates and how work is released to the floor
  • MFS communication points, channels and telegram structures per piece of equipment
  • Exception handling at the automation boundary, including what a person sees and when
  • Packing specifications and handling-unit management

The agent layer

Where an agent earns its place.

At the edges, where documents arrive unstructured and matching needs judgement. The transaction flow itself stays deterministic.

Slotting review
Looks at movement history against the current layout and proposes re-slotting, with the travel saved for each move, so the change can be argued for rather than asserted.
Telegram exception triage
Classifies MFS communication failures by cause — equipment, data, or sequence — and routes them, instead of presenting an undifferentiated error log.
Wave shaping
Proposes wave composition against carrier cut-offs, pick-face stock and available labour. A planner approves; the agent does not release work by itself.

Outcomes

What changes.

  • Before

    The WMS and the automation controller hold separate models of the building.

    After

    MFS drives the equipment directly from SAP, so there is one model and one master.

  • Before

    Automation exceptions are found by walking the aisle.

    After

    They are classified and queued with their cause attached.

  • Before

    Slotting is revisited when someone notices picking has got slower.

    After

    Re-slotting is proposed continuously against actual movement, with the saving stated.

Questions

What people ask.

Do we need MFS, or will a WCS do?
A WCS works. The question is whether you want two systems holding a model of the same building. MFS earns its place when the automation is substantial enough that the drift between the two becomes a running cost.
Can EWM run without automation?
Yes, and often should. EWM's storage control, slotting and wave management are worth having in a manual warehouse. MFS is the layer you add when there is equipment to drive.
What does the AI not do here?
It does not drive equipment. Physical movement stays deterministic, in the system that is accountable for it. The agents work on planning and on triage, where judgement is involved and a wrong answer is cheap to correct.

Recognise any of this in your own process?

Book a call