PO_LINE_LOCATIONS_ALL

-- ============================================================
-- Table  : PO_LINE_LOCATIONS_ALL — PO schedules — one row per shipment schedule (or blanket price break) with need-by/promised dates and the system-maintained received/accepted/rejected/billed quantity buckets; the workhorse grain for open-PO analytics
-- Purpose: Column-selected read of PO_LINE_LOCATIONS_ALL — auto-generated from field metadata
-- Grain  : One row per LINE_LOCATION_ID
-- Caution: QUANTITY_RECEIVED/ACCEPTED/REJECTED and QUANTITY_BILLED are running totals maintained by Receiving and Payables — balances, not events; open quantity is ordered − received − cancelled
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.LINE_LOCATION_ID AS "Surrogate key of the schedule",
  t.PO_LINE_ID AS "Parent line",
  t.PO_HEADER_ID AS "Parent header (denormalized)",
  t.SHIPMENT_NUM AS "Visible schedule number",
  t.SHIP_TO_ORGANIZATION_ID AS "Receiving inventory organization — the org half of every item join from procurement",
  t.SHIP_TO_LOCATION_ID AS "Ship-to location",
  t.QUANTITY AS "Scheduled quantity (or price-break quantity on agreements)",
  t.QUANTITY_RECEIVED AS "Cumulative quantity received to date — maintained by Receiving, a balance not an event",
  t.QUANTITY_ACCEPTED AS "Post-inspection accepted total",
  t.QUANTITY_REJECTED AS "Post-inspection rejected total",
  t.QUANTITY_BILLED AS "Quantity invoiced by Payables to date",
  t.QUANTITY_CANCELLED AS "Quantity cancelled — open quantity is QUANTITY − QUANTITY_RECEIVED − QUANTITY_CANCELLED",
  t.PRICE_OVERRIDE AS "Schedule price / price-break price",
  t.NEED_BY_DATE AS "Requested delivery date",
  t.PROMISED_DATE AS "Supplier-promised delivery date",
  t.SCHEDULE_STATUS AS "Schedule status — closure is this plus three separate close dates, no CLOSED_CODE",
  t.MATCH_OPTION AS "Match invoices to the PO or to the receipt",
  t.DESTINATION_TYPE_CODE AS "Inventory vs expense destination"
FROM <catalog>.<schema>.PO_LINE_LOCATIONS_ALL t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.LINE_LOCATION_ID = <LINE_LOCATION_ID>
  -- AND t.NEED_BY_DATE >= DATE '<DATE_FROM>'
  -- AND t.NEED_BY_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.LINE_LOCATION_ID;