PO_LINE_LOCATIONS_ALL

-- ============================================================
-- Table  : PO_LINE_LOCATIONS_ALL — PO shipment schedules — one row per delivery schedule per line with need-by/promised dates and the running received/billed/cancelled quantity counters; blanket price-break rows share the table
-- Purpose: Column-selected read of PO_LINE_LOCATIONS_ALL — auto-generated from field metadata
-- Grain  : One row per operating unit (ORG_ID) + LINE_LOCATION_ID
-- Caution: Price-break rows share this table with real shipments (SHIPMENT_TYPE distinguishes them), and QUANTITY_RECEIVED/QUANTITY_BILLED are running totals, not events — filter the type and treat the counters as balances
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. 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 shipment schedule — what receiving and drop-ship rows point at",
  t.PO_HEADER_ID AS "The document header (denormalized)",
  t.PO_LINE_ID AS "The document line",
  t.ORG_ID AS "Operating unit",
  t.PO_RELEASE_ID AS "The blanket release that created this shipment — NULL on standard POs",
  t.SHIPMENT_TYPE AS "Shipment vs blanket price break — price-break rows share this table; filter before summing",
  t.SHIPMENT_NUM AS "Shipment number within the line",
  t.SHIP_TO_ORGANIZATION_ID AS "The receiving inventory org — the org half of purchasing's item joins (see quirks guide #two-orgs)",
  t.QUANTITY AS "Ordered quantity on the shipment (or the break quantity on price-break rows)",
  t.QUANTITY_RECEIVED AS "Running total received — a balance, not an event; events live in the receiving ledger",
  t.QUANTITY_BILLED AS "Running total billed by payables matching",
  t.QUANTITY_CANCELLED AS "Quantity cancelled off the shipment",
  t.PRICE_OVERRIDE AS "Shipment-level price (or the break price on price-break rows)",
  t.NEED_BY_DATE AS "When the org needs the goods — the demand-side analysis date",
  t.PROMISED_DATE AS "The supplier's committed date — the OTD denominator",
  t.CLOSED_CODE AS "Shipment closure state",
  t.CANCEL_FLAG AS "Y when the shipment is cancelled"
FROM <catalog>.<schema>.PO_LINE_LOCATIONS_ALL t
WHERE
  t.ORG_ID = <operating_unit_id>  -- operating unit (MOAC does not filter extracts)
  -- 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>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.LINE_LOCATION_ID;