Three tables became one

S/4 collapsed the movement header and item pair into one table. MATDOC carries every movement line with its own document identity, old reads survive through redirects, and the only safe long-term read is the new table itself.

RuleExtract material movements from MATDOC, the one S/4 table, and treat MKPF and MSEG as the compatibility views they now are.

Neverpoint new pipelines at MKPF and MSEG. Reads still work through redirect views, and every one of them is technical debt with a decommission date.

Three tables became one. Old code keeps working through redirects, which is exactly why migrations forget to stop using them.

◆ What moved wherethe fields, mapped.

You knew it as	In MATDOC	What it is
MKPF header: document, year, posting date	The same fields, on every line	The header dissolved; each line now carries its own document identity.
MSEG item: material, plant, movement type, quantity	The same fields, same names mostly	Line grain survives intact; the join to the header is gone because there is no header.
Stock quantity tables by location and type	Derived on read	On-hand is computed from MATDOC history, not maintained as separate totals tables.
Your old extractors and queries	Compatibility views	Reads against the old names redirect; writes do not exist for them anymore.

The practical rule for a warehouse: land MATDOC once at line grain and derive everything the old stock tables used to hold. The as-of problem and the stock overview both fall out of that one landed table.

◆ Why the redirect is a trapworking code with an expiry date.

Compatibility views make migration painless and abandonment invisible: the old query still answers, so nobody rewrites it. The debt surfaces when performance notes or a release change the view behavior. New extraction should name MATDOC directly and let the old names retire.

Use case

Problem

Pipelines built on MKPF and MSEG kept working after the S/4 move, so nobody rewrote them, and now every read rides a compatibility view nobody owns.

What we build

Extraction pointed at MATDOC at line grain, the old names retired deliberately, and stock states derived from the one landed history.

What you get

A movement pipeline on the real table: no redirect risk, one grain to reason about, and the stock questions answered from history you own.

Are your extractors still reading MSEG?

We repoint the pipeline at MATDOC and retire the redirects.

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, one row per movement line.
MKPF: The old movement header table; now a compatibility view.
MSEG: The old movement item table; now a compatibility view.
compatibility view: A redirect that lets old reads keep working against the new table.