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
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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 →
Fields
9 fields · 1 key
| # | 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_Bon 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_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;5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <RESOURCE_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_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