Two facts: what moved, what was promised

S/4 already made the modeling decision: it deleted the stock-total tables and derives everything from the movement history. This star applies the same rule in your warehouse: two facts, five dimensions, every state a query.

RuleModel the module as two facts: movements at MATDOC line grain and order lines from EKPO, with stock states derived, never maintained.

Neverland aggregated stock tables as facts. S/4 itself derives on-hand from movement history; a warehouse that stores totals is arguing with the source’s own design.

Two red facts, five teal dimensions. Movements at MATDOC grain, orders at line grain, and every page in the module a grouping over them.

◆ The two factswhat moved and what was promised.

Fact	Grain	Carries
fct_material_movement	one row per MATDOC line	Material, plant, location, movement type, quantity, value, and the three dates of a movement.
fct_po_line	one row per EKPO line	Vendor, material, ordered quantity and price, received-so-far, and the open flag derived against receipts.

On-hand is a running sum, the roll-forward a monthly fold, the open book a join between the two facts, and the clearing roll the value lens over the same lines.

◆ Derived, not maintainedthe S/4 lesson, applied to the warehouse.

S/4 deleted the old stock-total tables and derives on-hand from MATDOC; the owned model keeps that discipline. Store movements and orders, derive states daily, and the as-of question becomes a filter instead of a reconstruction.

Use case

Problem

Warehouse models mirror the old totals tables, stock states drift from movement history, and every as-of question triggers a rebuild.

What we build

Two facts on shared dimensions: movements at line grain and order lines with receipts joined, every stock state derived daily from history.

What you get

A materials model that cannot disagree with itself: one grain for movements, states that recompute, and the whole module as groupings.

Want materials analytics on the real grain?

We build the two-fact star that derives every state.

Talk to us

Terms on this page

SAP: The vendor. Systems, Applications, and Products in data processing.
HANA: SAP’s in-memory database, the platform S/4 runs on.
MM: Materials Management, the purchasing and inventory module.
MATDOC: The S/4 material document table, the movement fact’s source.
EKPO: The purchase order line table, the order fact’s source.
derived state: On-hand computed from history, never stored as a total.
versioned: Old attribute values kept with their dates when masters change.