One batch, found everywhere

A recall is a where-used query with a clock on it. Batch B-7741 proves the chain: sixty units received, sixty consumed, 58 shipped to three customers, two on the shelf, every hop reconciling before anyone picks up a phone.

RuleLand the batch genealogy as rows, because a recall is a query you must answer in hours, against a chain the delivered trace drops at every repack.

Neverrehearse recalls with the transaction that will be used under pressure. The drill should find the chain’s broken links on a quiet Tuesday, not during the event.

A recall is a where-used query with a clock on it. The chain is either landed and whole, or rebuilt under pressure.

◆ The trace, both directionssixty units, accounted.

Batch B-7741, traced	Documents	Units
Received into raw store	1	60
Issued to production orders	2	60
Shipped in customer deliveries	3	58
Still on hand, finished store		2

Sixty in, sixty consumed across two orders, 58 shipped across three deliveries, two on the shelf: the units reconcile at every hop, which is exactly what the query must prove before anyone calls a customer. Sample values are illustrative, never client data.

◆ Where the trace snapsrepacks and plant walls.

The delivered where-used trace follows a batch number, so it ends wherever the number changes: repacking, relabeling, a new batch at a second plant. Practitioners report recall drills stalling at exactly these seams. The landed genealogy maps old number to new at every transformation, and the walls come down.

◆ The drill is the metrichours, measured on a quiet day.

Regulators and customers measure recall readiness in elapsed hours. Running the query quarterly against a random batch, and recording the hours, turns traceability from a claimed capability into a number on a page.

Use case

Problem

Recall drills stall at repacks and plant boundaries, the trace lives in a transaction nobody times, and readiness is a claim instead of a number.

What we build

Batch genealogy landed with transformations mapped: both-direction traces in one query, units reconciling at every hop, drills timed quarterly.

What you get

Recalls answered in hours with evidence: the chain whole across repacks and plants, customers named from deliveries, and a readiness number you can show.

Pick a batch at random. How many hours to trace it?

We land the genealogy and make it minutes.

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.
where-used: The trace from a batch to everywhere it went.
MB56: The delivered trace; follows the number, drops at repacks.
genealogy: The landed old-to-new batch map across transformations.
recall drill: The timed quarterly rehearsal that makes readiness a number.