What production actually consumed

Issues are where stock becomes cost. May’s 118 issue documents consumed 1,180 units across production, maintenance, and the overhead lane, and the honest reading of their dates is the difference between a clean close and a timing smear.

RuleLand every issue with its consumer, order, and date of record, and reconcile backflushed quantities to confirmations, because automatic postings inherit automatic errors.

Nevertreat the issue date as the consumption date when backflushing is on. The posting happens at confirmation, and the gap between the two rewrites the month’s timing.

Issues are where stock becomes cost. The consumer lane decides whose cost, and the date decides whose month.

◆ May issues, by consumerthe 261 row, opened.

Consumer	Documents	Units
Production orders	92	960
Maintenance orders	18	150
Cost centers, direct to overhead	8	70
Issues to orders, May	118	1,180

The totals are the movement partition’s 261 row exactly. The cost-center lane is the one to watch: material leaving stock without an order bypasses product costing entirely, which is sometimes right and always worth counting. Sample values are illustrative, never client data.

◆ The date the backflush writesconfirmation time, not consumption time.

With backflushing, the issue posts when the operation confirms, not when the material was used. Days can separate the two, and at month end those days move cost between periods. The landed history keeps both dates where they differ, so the close reads timing instead of guessing it.

◆ The wrong-order issuesilent until the variance review.

An issue against the wrong production order prices one product with another’s material and shows up weeks later as paired variances nobody connects. Trending issues per order against the bill of materials flags the outliers while the month is still open.

Use case

Problem

Backflush timing smears cost across period ends, cost-center issues leak past product costing, and wrong-order issues surface as unexplained variances.

What we build

Issues landed with consumer, order, and both dates: confirmation timing visible, the overhead lane counted, per-order consumption trended against the bill.

What you get

Consumption that lands where and when it happened: period ends without timing smear, an overhead lane with a number, and wrong-order issues caught in-month.

How many days sit between your confirmations and consumption?

We land both dates and measure the smear.

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.
261: The issue-to-order movement type this page opens.
backflush: Automatic issue posted at operation confirmation.
cost-center issue: Material to overhead without an order; the 201 family.
bill of materials: The recipe an order’s consumption should resemble.