WIS_WD_VERSIONS

-- ============================================================
-- Table  : WIS_WD_VERSIONS — Work definition versions — dated snapshots of the version-controlled header attributes, with the approval status gating which version execution uses
-- Purpose: Column-selected read of WIS_WD_VERSIONS — auto-generated from field metadata
-- Grain  : One row per WORK_DEFINITION_VERSION_ID
-- Caution: VERSION_NUMBER is a VARCHAR2 — ordering it numerically mis-sorts past version 9; order by EFFECTIVE_FROM_DATE instead
-- 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.WORK_DEFINITION_VERSION_ID AS "Surrogate key of the version",
  t.WORK_DEFINITION_ID AS "The work definition being versioned",
  t.VERSION_NUMBER AS "The version label — a VARCHAR2, never sort it numerically",
  t.EFFECTIVE_FROM_DATE AS "Start of the version's effectivity window",
  t.EFFECTIVE_TO_DATE AS "End of the window — NULL while open",
  t.ORGANIZATION_ID AS "Plant — nullable here, so the catalog doesn't anchor on it",
  t.APPROVAL_STATUS_CODE AS "Version approval status"  -- decode t.APPROVAL_STATUS_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIS_WD_VERSION_STATUS', LANGUAGE-filtered)
FROM <catalog>.<schema>.WIS_WD_VERSIONS t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.WORK_DEFINITION_VERSION_ID = <WORK_DEFINITION_VERSION_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.WORK_DEFINITION_VERSION_ID;