WIS_WD_OPERATIONS_B
Product: WISmasterWork 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
Operation rows are effectivity slices (EFFECTIVE_FROM_DATE/EFFECTIVE_TO_DATE) — filter the window you mean or steps multiply
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.
- FscmTopModelAM.ScmExtractAM.WisBiccExtractAM.WDOperationExtractPVO
Work Definition Operations data store — keyed on WdOperationId; the store joins base + translation entities, so expect translated name attributes.
Oracle data-store documentation →
Fields
13 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WD_OPERATION_ID | Surrogate key of the operation row | NUMBER | Key |
| 2 | WORK_DEFINITION_ID | Parent work definition header | NUMBER | |
| 3 | OPERATION_SEQ_NUMBER | Execution order within the definition | NUMBER | |
| 4 | OPERATION_TYPE | In-house vs supplier operation | VARCHAR2 | ORA_WIS_OPERATION_TYPE |
| 5 | WORK_CENTER_ID | Work center where the operation runs | NUMBER | |
| 6 | EFFECTIVE_FROM_DATE | Start of this operation row's effectivity slice | TIMESTAMP | |
| 7 | EFFECTIVE_TO_DATE | End of the slice — NULL while open | TIMESTAMP | |
| 8 | STANDARD_OPERATION_ID | The reusable standard operation referenced, when one is | NUMBER | |
| 9 | COUNT_POINT_FLAG | Completion must be explicitly reported at this step | VARCHAR2 | |
| 10 | AUTO_TRANSACT_FLAG | Materials and resources auto-charge at this step | VARCHAR2 | |
| 11 | OP_YIELD_FACTOR | Fraction of starting quantity yielded (1 = 100%) | NUMBER | |
| 12 | SUPPLIER_ID | Suggested supplier for supplier operations | NUMBER | |
| 13 | OSP_ITEM_ID | Outside-processing service item for supplier operations | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of WIS_WD_OPERATIONS_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_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 partition column 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;4 parameters not filled: <catalog>, <schema>, <WD_OPERATION_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_WORK_DEFINITIONS.WORK_DEFINITION_ID = WIS_WD_OPERATIONS_B.WORK_DEFINITION_IDON WIS_WD_OPERATIONS_B.WORK_CENTER_ID = WIS_WORK_CENTERS_B.WORK_CENTER_ID