WIS_WORK_CENTERS_B
Product: WISmasterPer inventory orgThe 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
No capacity, utilization, or efficiency columns here — those live per resource assignment in the work-center-resources bridge (not yet cataloged), a trap for anyone expecting the EBS department shape. Names are on WIS_WORK_CENTERS_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
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.WorkCenterExtractPVO
Work Centers data store — keyed on WorkCenterId, base + translation joined. In OTBI the work center is a dimension across the manufacturing subject areas, never its own.
Oracle data-store documentation (opens in new tab)
Fields
6 fields · 1 key
6 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WORK_CENTER_ID | Surrogate key of the work center | NUMBER | Key |
| 2 | WORK_CENTER_CODE | User-facing work center code | VARCHAR2 | |
| 3 | ORGANIZATION_ID | Plant owning the work center | NUMBER | |
| 4 | WORK_AREA_ID | Parent work area | NUMBER | |
| 5 | INACTIVE_DATE | End-dating — NULL while active | DATE | |
| 6 | OVERRIDE_CALENDAR_FLAG | Work-center calendars override the plant calendar | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of WIS_WORK_CENTERS_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.
5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WORK_CENTER_ID>, <watermark>
-- ============================================================
-- Table : WIS_WORK_CENTERS_B — The 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
-- Purpose: Column-selected read of WIS_WORK_CENTERS_B — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + WORK_CENTER_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.WORK_CENTER_ID AS "Surrogate key of the work center",
t.WORK_CENTER_CODE AS "User-facing work center code",
t.ORGANIZATION_ID AS "Plant owning the work center",
t.WORK_AREA_ID AS "Parent work area",
t.INACTIVE_DATE AS "End-dating — NULL while active",
t.OVERRIDE_CALENDAR_FLAG AS "Work-center calendars override the plant calendar"
FROM <catalog>.<schema>.WIS_WORK_CENTERS_B t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the business unit — see quirks guide #item-org-striping
-- AND t.WORK_CENTER_ID = <WORK_CENTER_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.WORK_CENTER_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_WD_OPERATIONS_B.WORK_CENTER_ID = WIS_WORK_CENTERS_B.WORK_CENTER_IDON WIS_WORK_CENTERS_B.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_IDON WIE_WO_OPERATIONS_B.WORK_CENTER_ID = WIS_WORK_CENTERS_B.WORK_CENTER_ID AND WIE_WO_OPERATIONS_B.ORGANIZATION_ID = WIS_WORK_CENTERS_B.ORGANIZATION_IDON WIE_WO_OPERATION_RESOURCES.WORK_CENTER_ID = WIS_WORK_CENTERS_B.WORK_CENTER_ID AND WIE_WO_OPERATION_RESOURCES.ORGANIZATION_ID = WIS_WORK_CENTERS_B.ORGANIZATION_ID
More Manufacturing tables
- 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
- WIE_WO_OPERATION_MATERIALSComponent requirements of each work order operation — one row per material line with per-assembly usage, total requirement, supply method, and running issued/allocated/picked counters
- WIE_WO_OPERATION_RESOURCESLabor and equipment requirements for each work order operation — usage rate, required and actual usage, assigned units, and charge behavior
- WIE_WO_OPERATIONS_BWork order operations — one row per execution step with its sequence, work center, count-point behavior, and the quantity balances sitting at each dispatch state