Consolidated data

Report months follow the procurement cycle, not the calendar: report month M draws data from the 21st of (M-2) through the 20th of (M-1). For example January = 21 Nov–20 Dec, February = 21 Dec–20 Jan. KPI 1/2/3 window on PO date, KPI 4 on PR date, KPI 7 on vendor creation date.

LEAD TIME is the master sheet (PR → PO → GRPO, one row per PR-line, including PRs not yet converted to a PO). It sets the dashboard's date span, is KPI 4's denominator, and carries the goods-receipt detail: GR date and quantity, the ordered PO quantity, the PO Due Date (ETA), last/current price and PR→PO days.

PO REPORT enriches it with the PO detail that LEAD TIME lacks: the Lokal/Impor flag (the KPI 2 vs KPI 3 split), plus ETA, currency and unit price, joined on PO No.

VENDOR LIST is the vendor master; KPI 7 counts Active vendors whose creation date falls in the window (cumulative per year, target 6).

KPI 2/3 'received' logic is quantity-aware: a PO-item counts as received only when the running sum of GR quantities reaches the ordered quantity; the completion date (the GR that crosses the ordered qty) is compared to ETA + 7 days (Local) / 14 days (Import).

On import each file is upserted by its natural key, so re-uploading an updated export updates rows in place instead of duplicating them. KPI 5 (Quality) and 6 (Substitution) have no source in these files yet — they are seeded with best-case defaults so the scorecard is complete; replace those entries as real data arrives.

Realisasi here uses a 7-day tolerance (local). Each KPI's own formula is on its methodology page — click any KPI title on the dashboard.