Expected vs Scanned HUs
A worklist expects HUs, while scanner logs record actual HUs. Find missing and wrong scans.
BUSINESS KEYPO + SM + HU
COMPARE / MEASUREExpected/Scanned
BEST STARTReconcile expected keys against scanned keys and classify missing/wrong.
Workflow
- Confirm the grain: decide what one row should represent in the final result.
- Profile key uniqueness and missing data before matching or aggregating.
- Calculate the result on a small sample and reconcile it manually.
- Run the full dataset, review exceptions, then export the evidence you need.
READY FOR THE REAL FILE?
Open tool →Use the matching WorkTools utility
Your file stays in the browser for supported local tools.
What can go wrong
Most incorrect results come from the wrong key, one-to-many joins, mixed data types, hidden whitespace or aggregating at the wrong grain. Treat these checks as part of the analysis, not optional cleanup.