Skip to content
Fusion Reference

WIS_WORK_CENTERS_B

Product: WISmasterPer inventory org

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

Notes

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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 →

Fields

6 fields · 1 key

Table fields: position, field name, description, data type, and flags. 6 fields.
#FieldDescriptionTypeFlags
1WORK_CENTER_IDSurrogate key of the work centerNUMBER
Key
2WORK_CENTER_CODEUser-facing work center codeVARCHAR2
3ORGANIZATION_IDPlant owning the work centerNUMBER
4WORK_AREA_IDParent work areaNUMBER
5INACTIVE_DATEEnd-dating — NULL while activeDATE
6OVERRIDE_CALENDAR_FLAGWork-center calendars override the plant calendarVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of WIS_WORK_CENTERS_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.

Query parameters
-- ============================================================
-- 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;

5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WORK_CENTER_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

  • WIS_WD_OPERATIONS_BWIS_WORK_CENTERS_Bforeign key · N:1
    ON WIS_WD_OPERATIONS_B.WORK_CENTER_ID = WIS_WORK_CENTERS_B.WORK_CENTER_ID
  • WIS_WORK_CENTERS_BINV_ORG_PARAMETERSforeign key · N:1
    ON WIS_WORK_CENTERS_B.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
  • WIE_WO_OPERATIONS_BWIS_WORK_CENTERS_Bforeign key · N:1
    ON 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_ID
  • WIE_WO_OPERATION_RESOURCESWIS_WORK_CENTERS_Bforeign key · N:1
    ON 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

Browse more Manufacturingtables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.