PO_RELEASES_ALL

-- ============================================================
-- Table  : PO_RELEASES_ALL — Blanket and planned PO releases — one row per release with its number, date, buyer, and approval status; the shipment schedules a release creates point back here
-- Purpose: Column-selected read of PO_RELEASES_ALL — auto-generated from field metadata
-- Grain  : One row per operating unit (ORG_ID) + PO_RELEASE_ID
-- 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.PO_RELEASE_ID AS "Surrogate key of the release",
  t.PO_HEADER_ID AS "The blanket or planned PO being released — release numbers are unique within it",
  t.ORG_ID AS "Operating unit",
  t.RELEASE_NUM AS "Release number within the agreement",
  t.RELEASE_DATE AS "When the release was created — the primary analysis date",
  t.RELEASE_TYPE AS "Blanket vs scheduled release",
  t.AUTHORIZATION_STATUS AS "Approval status — same Purchasing lookup ladder as headers",
  t.APPROVED_FLAG AS "Y once approved",
  t.APPROVED_DATE AS "Last approval date",
  t.CLOSED_CODE AS "Release closure state",
  t.CANCEL_FLAG AS "Y when cancelled",
  t.AGENT_ID AS "The buyer on the release",
  t.REVISION_NUM AS "Revision number of the release"
FROM <catalog>.<schema>.PO_RELEASES_ALL t
WHERE
  t.ORG_ID = <operating_unit_id>  -- operating unit (MOAC does not filter extracts)
  -- AND t.PO_RELEASE_ID = <PO_RELEASE_ID>
  -- AND t.RELEASE_DATE >= DATE '<DATE_FROM>'
  -- AND t.RELEASE_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.PO_RELEASE_ID;