Fusion Reference
WIS_RESOURCES_B
Product: WISmasterPer inventory orgThe production resource master — each row an equipment or labor resource that performs operations at work centers, unique per plant by resource code
Identity
Module: ManufacturingInventory-org partitioned (ORGANIZATION_ID)
EBS equivalents (2)
Notes
No cost-rate columns (only COSTED_FLAG — rates live in costing) and no work-center column: resource-to-work-center is many-to-many through a bridge table (not yet cataloged). Names are on WIS_RESOURCES_TL (not yet cataloged).
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.
Extract access
The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.
- FscmTopModelAM.ScmExtractAM.WisBiccExtractAM.ResourceExtractPVOOTBI: Manufacturing - Resource Usage Real Time
Plant Resources data store (labor or equipment) — keyed on ResourceId. The usage subject area is the OTBI surface where the resource is the central dimension.
Oracle data-store documentation (opens in new tab)
Fields
9 fields · 1 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | RESOURCE_ID | Surrogate key of the resource | NUMBER | Key |
| 2 | RESOURCE_CODE | User-facing resource code — unique per plant | VARCHAR2 | |
| 3 | RESOURCE_TYPE | Equipment vs labor | VARCHAR2 | ORA_WIS_RESOURCE_TYPE |
| 4 | RESOURCE_CLASS_CODE | Resource class grouping | VARCHAR2 | ORA_WIS_RESOURCE_CLASS |
| 5 | ORGANIZATION_ID | Plant owning the resource | NUMBER | |
| 6 | UOM_CODE | Unit the resource is charged in (typically time) | VARCHAR2 | |
| 7 | COSTED_FLAG | Resource participates in costing — rates live in cost management | VARCHAR2 | |
| 8 | INACTIVE_DATE | End-dating — NULL while active | DATE | |
| 9 | AUTO_EQUIPMENT_FLAG | Marks the resource as automation equipment | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of WIS_RESOURCES_B on 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.
Query parameters
5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <RESOURCE_ID>, <watermark>
-- ============================================================
-- Table : WIS_RESOURCES_B — The production resource master — each row an equipment or labor resource that performs operations at work centers, unique per plant by resource code
-- Purpose: Column-selected read of WIS_RESOURCES_B — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + RESOURCE_ID
-- 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.RESOURCE_ID AS "Surrogate key of the resource",
t.RESOURCE_CODE AS "User-facing resource code — unique per plant",
t.RESOURCE_TYPE AS "Equipment vs labor", -- decode t.RESOURCE_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIS_RESOURCE_TYPE', LANGUAGE-filtered)
t.RESOURCE_CLASS_CODE AS "Resource class grouping", -- decode t.RESOURCE_CLASS_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIS_RESOURCE_CLASS', LANGUAGE-filtered)
t.ORGANIZATION_ID AS "Plant owning the resource",
t.UOM_CODE AS "Unit the resource is charged in (typically time)",
t.COSTED_FLAG AS "Resource participates in costing — rates live in cost management",
t.INACTIVE_DATE AS "End-dating — NULL while active",
t.AUTO_EQUIPMENT_FLAG AS "Marks the resource as automation equipment"
FROM <catalog>.<schema>.WIS_RESOURCES_B t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the business unit — see quirks guide #item-org-striping
-- AND t.RESOURCE_ID = <RESOURCE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.RESOURCE_ID;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON WIS_RESOURCES_B.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_IDON WIE_WO_OPERATION_RESOURCES.RESOURCE_ID = WIS_RESOURCES_B.RESOURCE_ID AND WIE_WO_OPERATION_RESOURCES.ORGANIZATION_ID = WIS_RESOURCES_B.ORGANIZATION_IDON WIE_RESOURCE_TRANSACTIONS.RESOURCE_ID = WIS_RESOURCES_B.RESOURCE_ID AND WIE_RESOURCE_TRANSACTIONS.ORGANIZATION_ID = WIS_RESOURCES_B.ORGANIZATION_ID
More Manufacturing tables
- WIS_WD_OPERATIONS_BWork definition operations — the ordered, date-effective steps of a work definition, each pointing at the work center where it runs and optionally at a reusable standard operation
- WIS_WD_VERSIONSWork definition versions — dated snapshots of the version-controlled header attributes, with the approval status gating which version execution uses
- WIS_WORK_CENTERS_BThe work center master — a physical station inside a work area where a type of operation happens; deliberately thin, with names in the translation companion and capacity on the resource assignments
- WIS_WORK_DEFINITIONSThe work definition header — one row per item + definition-name combination in a plant, binding the produced item, the item structure supplying material requirements, and the work method; the Fusion successor to the routing
- WIE_OPERATION_TRANSACTIONSThe shop-floor product ledger — one row per movement of primary-product quantity through operation dispatch states: completions, moves, scrap, reject, and their reversals
- WIE_RESOURCE_TRANSACTIONSThe resource charge ledger — labor and equipment usage charged (or reversed) against work order operation resources, with full lineage down to the resource assignment