Skip to content
Fusion Reference

WIS_WD_OPERATIONS_B

Product: WISmaster

Work 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

Grain note

Operation rows are effectivity slices (EFFECTIVE_FROM_DATE/EFFECTIVE_TO_DATE) — filter the window you mean or steps multiply

Notes

No org column — the plant derives through the header. Operation names live on the translation companion (WIS_WD_OPERATIONS_TL, not yet cataloged). Supplier operations carry the outside-processing item and suggested supplier.

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Header & line

WIS_WD_OPERATIONS_B lines join back to their header WIS_WORK_DEFINITIONS — and the org column — so a line never fans out.

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.

Fields

13 fields · 1 key

13 fields.

Table fields: position, field name, description, data type, and flags. 13 fields.
#FieldDescriptionTypeFlags
1WD_OPERATION_IDSurrogate key of the operation rowNUMBER
Key
2WORK_DEFINITION_IDParent work definition headerNUMBER
3OPERATION_SEQ_NUMBERExecution order within the definitionNUMBER
4OPERATION_TYPEIn-house vs supplier operationVARCHAR2
ORA_WIS_OPERATION_TYPE
5WORK_CENTER_IDWork center where the operation runsNUMBER
6EFFECTIVE_FROM_DATEStart of this operation row's effectivity sliceTIMESTAMP
7EFFECTIVE_TO_DATEEnd of the slice — NULL while openTIMESTAMP
8STANDARD_OPERATION_IDThe reusable standard operation referenced, when one isNUMBER
9COUNT_POINT_FLAGCompletion must be explicitly reported at this stepVARCHAR2
10AUTO_TRANSACT_FLAGMaterials and resources auto-charge at this stepVARCHAR2
11OP_YIELD_FACTORFraction of starting quantity yielded (1 = 100%)NUMBER
12SUPPLIER_IDSuggested supplier for supplier operationsNUMBER
13OSP_ITEM_IDOutside-processing service item for supplier operationsNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

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

4 parameters not filled: <catalog>, <schema>, <WD_OPERATION_ID>, <watermark>

-- ============================================================
-- Table  : WIS_WD_OPERATIONS_B — Work 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
-- Purpose: Column-selected read of WIS_WD_OPERATIONS_B — auto-generated from field metadata
-- Grain  : One row per WD_OPERATION_ID
-- Caution: Operation rows are effectivity slices (EFFECTIVE_FROM_DATE/EFFECTIVE_TO_DATE) — filter the window you mean or steps multiply
-- 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.WD_OPERATION_ID AS "Surrogate key of the operation row",
  t.WORK_DEFINITION_ID AS "Parent work definition header",
  t.OPERATION_SEQ_NUMBER AS "Execution order within the definition",
  t.OPERATION_TYPE AS "In-house vs supplier operation",  -- decode t.OPERATION_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIS_OPERATION_TYPE', LANGUAGE-filtered)
  t.WORK_CENTER_ID AS "Work center where the operation runs",
  t.EFFECTIVE_FROM_DATE AS "Start of this operation row's effectivity slice",
  t.EFFECTIVE_TO_DATE AS "End of the slice — NULL while open",
  t.STANDARD_OPERATION_ID AS "The reusable standard operation referenced, when one is",
  t.COUNT_POINT_FLAG AS "Completion must be explicitly reported at this step",
  t.AUTO_TRANSACT_FLAG AS "Materials and resources auto-charge at this step",
  t.OP_YIELD_FACTOR AS "Fraction of starting quantity yielded (1 = 100%)",
  t.SUPPLIER_ID AS "Suggested supplier for supplier operations",
  t.OSP_ITEM_ID AS "Outside-processing service item for supplier operations"
FROM <catalog>.<schema>.WIS_WD_OPERATIONS_B t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.WD_OPERATION_ID = <WD_OPERATION_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.WD_OPERATION_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

  • WIS_WORK_DEFINITIONSWIS_WD_OPERATIONS_Bheader line · 1:N
    ON WIS_WORK_DEFINITIONS.WORK_DEFINITION_ID = WIS_WD_OPERATIONS_B.WORK_DEFINITION_ID
  • 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

Browse more Manufacturing tables

More Manufacturing tables

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.