The status tables are gone

S/4 moved order and delivery status onto the documents themselves. The old status pair still answers through views, which is exactly the problem: feeds watching those tables for changes see none, forever, without erroring once.

RuleRebuild status-driven extraction on the document tables, because the status tables are gone and the compatibility views hide the funeral.

Neverkeep delta logic keyed on status-table changes. The tables it watches no longer receive writes; the view answers and the deltas quietly starve.

S/4 moved status onto the documents themselves. Old reads still answer; old change-detection quietly starves.

◆ What moved wherethe status fields, relocated.

You knew it as	Now lives on	What changed
Header status, the VBUK row	The order, delivery, and billing headers	One join disappeared; every header carries its own status fields.
Item status, the VBUP row	The order and delivery items	Line status sits on the line; the fan-out join is gone.
Status-change delta extraction	Nothing, by default	The common ECC pattern watched these tables for writes; the writes stopped.
Document flow lookups	A reshaped flow table	Flow records simplified; chains that assumed the old shape need a retest.

The practical rule: extract status with the documents, from the document tables, and retire the status-table names on a date someone owns. The materials module tells the same story for movements; this is the order-to-cash edition.

◆ Where the deltas starveworking views, dead triggers.

Compatibility views make the old names answer queries, but nothing writes to the old tables anymore, so extraction keyed on their change images returns silence and looks healthy doing it. Practitioners report status feeds dying this way after conversion: no error, no rows, no alarm.

Use case

Problem

Status-driven feeds built on the old pair survived conversion as empty pipes: the views answer, the deltas never arrive, and downstream dashboards age quietly.

What we build

Status extracted with the documents from the document tables, delta logic rebuilt on their change data, and the old names retired deliberately.

What you get

Order and delivery status that actually updates: deltas from tables that receive writes, one less join everywhere, and no silent starvation.

Did your status feed survive the S/4 conversion, or just stop erroring?

We retest the pipe and repoint it.

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.
SD: Sales and Distribution, the order-to-cash module.
VBUK: The old header status table; a view now, written never.
VBUP: The old item status table; same fate.
delta extraction: Pulling only what changed; starves when writes move elsewhere.
document flow: The order-to-delivery-to-billing chain records.