WIS_WD_VERSIONS
Product: WISmasterWork definition versions — dated snapshots of the version-controlled header attributes, with the approval status gating which version execution uses
VERSION_NUMBER is a VARCHAR2 — ordering it numerically mis-sorts past version 9; order by EFFECTIVE_FROM_DATE instead
Reconstructing a routing as of a version means overlapping this table's effectivity window with the operations' own EFFECTIVE_FROM/TO_DATE slices — operations carry no version FK. ORGANIZATION_ID here is nullable, so the catalog doesn't anchor on it.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
Fields
7 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WORK_DEFINITION_VERSION_ID | Surrogate key of the version | NUMBER | Key |
| 2 | WORK_DEFINITION_ID | The work definition being versioned | NUMBER | |
| 3 | VERSION_NUMBER | The version label — a VARCHAR2, never sort it numerically | VARCHAR2 | |
| 4 | EFFECTIVE_FROM_DATE | Start of the version's effectivity window | TIMESTAMP | |
| 5 | EFFECTIVE_TO_DATE | End of the window — NULL while open | TIMESTAMP | |
| 6 | ORGANIZATION_ID | Plant — nullable here, so the catalog doesn't anchor on it | NUMBER | |
| 7 | APPROVAL_STATUS_CODE | Version approval status | VARCHAR2 | ORA_WIS_WD_VERSION_STATUS |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of WIS_WD_VERSIONSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- 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 partition column 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;4 parameters not filled: <catalog>, <schema>, <WORK_DEFINITION_VERSION_ID>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON WIS_WD_VERSIONS.WORK_DEFINITION_ID = WIS_WORK_DEFINITIONS.WORK_DEFINITION_IDON WIE_WORK_ORDERS_B.WORK_DEFINITION_VERSION_ID = WIS_WD_VERSIONS.WORK_DEFINITION_VERSION_ID