Analytics Catalog/Data dictionary/WIS_WORK_DEFINITIONS
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

WIS_WORK_DEFINITIONS

SharedUsed in 21 subject areas15 reporting columns

Work Instructions (WIS).

Likely primary key: WORK_DEFINITION_ID (inferred from Oracle naming conventions, verify against Tables & Views)
Joins (inferred from key columns): ORGANIZATION_ID → INV_ORGANIZATION_DEFINITIONS_V

Columns

ColumnKeyIn reportsDescription (inferred)
COSTING_PRIORITY●Costing priority.
INACTIVE_DATE●Inactive date.
MINIMUM_TRANSFER_QUANTITY●Minimum transfer quantity.
ORGANIZATION_ID●Identifier for the organization.
PREASSIGN_LOT_FLAG●Indicator (Y/N) for the preassign lot.
PRODUCTION_PRIORITY●Production priority.
QUANTITY●Quantity.
SERIAL_TRACKING_FLAG●Indicator (Y/N) for the serial tracking.
STATUS_CODE●Code identifying the status.
SYSTEM_GENERATED_FLAG●Indicator (Y/N) for the system generated.
TRANSFORM_FROM_ITEM_ID●Identifier for the transform from item.
UOM_CODE●Code identifying the unit of measure.
WORK_DEFINITION_HEADER_NAME●Name of the work definition header.
WORK_DEFINITION_IDPK?●Identifier for the work definition.
WORK_DEFINITION_TYPE●Type of work definition.

Used by reports

No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed keys.

Need the extract + dbt staging for WIS_WORK_DEFINITIONS?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern