Fieldnotesby Arjun Sai
SAP EWMArchitecture · 2 min read

Embedded or decentralised EWM: how to choose

Both run the same EWM code. The decision is about risk, volume and landscape — not features.

The two options

Embedded EWM runs inside SAP S/4HANA and shares master data and the database. Decentralised EWM runs on its own S/4HANA instance and communicates with one or more ERP systems through queued interfaces.

When embedded fits

  • Plant warehouses and medium-volume DCs.
  • Close integration with production, QM and inventory.
  • Teams that want one system, one upgrade and no master-data replication.

When decentralised fits

  • 24×7 operations that must keep shipping during ERP downtime or upgrades.
  • Very high volumes or heavy automation (MFS) where performance isolation matters.
  • One warehouse serving several ERP systems or company landscapes.

Questions to ask the business

  1. What does one hour of warehouse downtime cost?
  2. How often will ERP be upgraded or patched?
  3. How many ERP systems will feed this warehouse in five years?

Takeaway

Start from operational risk. If the answer to question 1 is 'a lot', decentralised is usually worth the extra landscape.

A concept overview with illustrative examples. Exact steps and available functions depend on your SAP release and configuration.

Keep reading

More field notes

SAP MM

Procure-to-pay: see the whole process

Five documents, two departments and one supplier payment. Seeing P2P end-to-end is the fastest way to understand SAP MM.

Business process2 min readSAP MM

Invoice verification: what are you really checking?

Three-way match sounds simple. The detail — GR-based IV, tolerances and blocks — is where support tickets come from.

Procurement fundamentals2 min readSAP MM

Why the GR/IR account never seems to clear

GR/IR is where logistics and Finance meet every month-end. Here is how to read it and keep it clean.

Valuation2 min read