Reference domain

Procurement

Procurement is the first ABCS domain defined beyond a representative capability catalog. Draft 0.2 uses it to prove the Business Object, key, relationship, state and capability-contract models before deeper expansion into other domains.

Reference Business Objects

Object	Canonical identity	Business meaning
Purchase Requisition	`procurement.purchase-requisition`	An internal request for goods or services to be purchased.
Supplier	`procurement.supplier`	A procurement-domain view of a Party providing goods or services.
Purchase Order	`procurement.purchase-order`	A commercial purchasing document issued by a buyer to a supplier.
Receipt	`procurement.receipt`	A record that goods or services were received against a purchasing document.

Purchase Order capabilities

procurement.purchase-order.get

procurement.purchase-order.search

procurement.purchase-order.create

procurement.purchase-order.update

procurement.purchase-order.submit

procurement.purchase-order.approve

procurement.purchase-order.reject

procurement.purchase-order.cancel

Requisition, Supplier and Receipt capabilities

procurement.purchase-requisition.create

procurement.purchase-requisition.submit

procurement.purchase-requisition.approve

procurement.purchase-requisition.cancel

procurement.supplier.get

procurement.supplier.search

procurement.receipt.get

procurement.receipt.search

procurement.receipt.create

procurement.receipt.reverse

Purchase Order canonical shape

number
revision
orderDate
buyer
supplier
supplierSite
currency
paymentTerms
shipTo
billTo
requisitions[]
lines[]
  lineNumber
  item
  description
  quantity
  unitPrice
  amount
  requestedDeliveryDate
amounts
status
  lifecycle
  approval
  fulfillment
  invoicing
createdAt
updatedAt

The canonical model intentionally describes useful cross-application business semantics rather than reproducing every field available in an ERP.

Business keys

A Purchase Order may use number as its primary business key scoped to the buyer. ABCS does not force an artificial universal record UUID when real business identifiers already exist.

Relationships

Purchase Requisition ──────┐
                            ▼
Supplier ───────────────► Purchase Order ───────────────► Receipt
                            │
                            └── future cross-domain relationship to Invoice

Multidimensional state

Dimension	Draft 0.2 canonical values
Lifecycle	draft, open, closed, cancelled
Approval	not-required, not-submitted, pending, approved, rejected
Fulfillment	not-received, partially-received, received
Invoicing	not-invoiced, partially-invoiced, invoiced

Machine-readable source

Application-specific APIs, field mappings, authentication, transports, adapters and implementation constraints belong to implementations—not the canonical ABCS identity or business object.