Business problem

Manufacturing & Production

Whether the plant built what the plan said it would build.

Metrics

Computable definitions from the KPI Dictionary — every decision switch made explicit, with the formula behind it.

KPI	Formula	What it answers
Schedule AttainmentK-08	$\begin{aligned} \text{Mix attainment} &= \frac{\sum_{i} \min\!\left(c_i,\, s_i\right)}{\sum_{i} s_i} \\ \text{Volume attainment} &= \frac{\sum_{i} c_i}{\sum_{i} s_i} \end{aligned}$	Did production build what the schedule said, when it said — measured against which frozen schedule, on volume or on mix, and do overbuilds cancel shortfalls?
First Pass YieldK-13	$\begin{aligned} \text{FPY} &= \frac{\sum u^{\mathrm{good},1}}{\sum u^{\mathrm{started}}} \\ \text{RTY} &= \prod_{k=1}^{K} \text{FPY}_k \end{aligned}$	Of everything started into the process, how much came out conforming the first time — measured at which boundary, counted in which units, and with rework recorded where it can still be seen?

Schedule attainment is where over-production quietly pays for under-production. Sum what was built and divide by what was planned, and a line that ran long covers a line that never ran at all — so the definition here caps each row at its own plan before summing, and publishes the uncapped figure beside it rather than instead of it. Which schedule counts as the plan matters just as much: the frozen one, or the one as it stood at the end of the week. The reference build runs that definition over a simulated year of weekly schedules across two fictional plants, and the six ERP modules below are where work orders, routings and confirmations actually live in each system. First pass yield asks the sibling question — of what was built, how much came out right the first time — and it is the entry where the recording convention decides whether the metric can be computed at all: rework that overwrites its original operation result leaves nothing to count.

SAP modeling guides

Start from the business question, not the table. Each guide covers the table set, the joins and their traps, the grain decision, extraction into Databricks, and working SQL.

Reference builds

Reference builds for this business problem, implementing the definitions above wherever one exists, running over frozen, simulated data. Not a resource and not a case study — no client data, and no client named.

Production Schedule PerformanceDid the plant build what the frozen schedule said — or did total volume hide the wrong mix?

In the references

Where this data lives in each source system. A way into the ERP references, not an index of them — every reference landing lists all of its modules.

SAPProduction Planning SAPQuality Management JDEShop Floor Management D365Production Control M3Manufacturing EBSWork in Process

The other business problems

Inventory & Working Capital — What you're holding, why it's there, and what it costs to hold it.
Demand Planning & Forecasting — How wrong the forecast is, in which direction, and where the error is worth fixing.
Customer Service & Fulfillment — Whether the order arrived complete, on the date you committed to.
Procurement & Supply — What's on order, when it lands, and how the supplier actually performs.
Data Foundation & Governance — Landing ERP data in a lakehouse without losing deletes, history, or control of who reads it.

See this domain in the whole library