00 — Overview

R10 reference application. Built from the v0.14 Work & Supply reference pack. The demo data is fictional; supplier names, prices and order numbers are illustrative.

What Purchasing is

Purchasing answers "has it been bought, and when will it come?" It does not decide what an item is (Catalogue), hold stock or check goods in (Inventory), or plan the work (Work Management) — it turns a need into an order and keeps track of the supplier's promises.

The 10 models

Requirements (2) - PurchaseRequirement — a need to buy: item, quantity, required-by date, priority, procurement route, the material requirement and work order it serves, status (draft → sourcing → approved → ordered → received, or cancelled / closed). - PurchaseApproval — an approval asked for and decided (financial delegation etc.).

Purchase orders (3) - PurchaseOrder — the order to a supplier: number, status, dates, totals, the supplier's and the ERP's references. - PurchaseOrderLine — what is ordered: item (with description, part number and unit as they were when ordered), quantity, price, the material requirement it is for. - SupplierAcknowledgement — the supplier's acceptance of the order, with any exceptions.

Delivery (3) - DeliveryCommitment — the supplier's promised date and quantity for a line. A change is a new revision that supersedes the previous one; nothing is overwritten. - Shipment / ShipmentLine — what was dispatched, when, by which carrier.

Exceptions & history (2) - ProcurementException — something needing attention: goods rejected or quarantined at receipt, a delivery at risk. - ProcurementStatusHistory — every status change of a requirement or order, with the reason and the network message that caused it.

The demo story

New requirements continue the series (PR-1002, PO-004412, SH-2002 …).