# Oracle Fusion Manufacturing Tables: Work Orders, Work Definitions and Join Keys

> Source: https://netray.co/tools/oracle-fusion-manufacturing-tables-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A searchable list of the main Oracle Fusion Manufacturing tables for work orders and work definitions, with purpose, key columns and join notes for BI Publisher reports.

## Category

oracle

## Erp

Oracle Fusion Cloud SCM

## Audience

- Fusion report developer
- BI analyst
- Manufacturing functional consultant

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Table

**Key:** table

**Type:** text

#### Area

**Key:** area

**Type:** select

**Options:**

- Work definition
- Work order
- Item and organization
- Inventory
- Costing

#### What it holds

**Key:** purpose

**Type:** text

#### Key and join columns

**Key:** keys

**Type:** text

**Rows:**

**Table:** WIS_WORK_DEFINITIONS

**Area:** Work definition

**Purpose:** Header of a work definition, the manufacturing routing and bill of materials for an item in an organization

**Keys:** WORK_DEFINITION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID

**Table:** WIS_WORK_DEFINITION_VERSIONS

**Area:** Work definition

**Purpose:** Versions of a work definition with effective dates

**Keys:** WORK_DEFINITION_ID, VERSION_NUMBER

**Table:** WIS_OPERATIONS_B

**Area:** Work definition

**Purpose:** Operations defined in a work definition version

**Keys:** OPERATION_ID, WORK_DEFINITION_ID, OPERATION_SEQUENCE_NUMBER

**Table:** WIS_OPERATION_MATERIALS

**Area:** Work definition

**Purpose:** Component materials needed at each operation

**Keys:** OPERATION_ID, INVENTORY_ITEM_ID

**Table:** WIS_OPERATION_RESOURCES

**Area:** Work definition

**Purpose:** Labor and machine resources used at each operation

**Keys:** OPERATION_ID, RESOURCE_ID

**Table:** WIE_WORK_ORDERS_B

**Area:** Work order

**Purpose:** Work order header: item, quantity, status and planned dates

**Keys:** WORK_ORDER_ID, WORK_ORDER_NUMBER, ORGANIZATION_ID, INVENTORY_ITEM_ID

**Table:** WIE_WO_OPERATIONS_B

**Area:** Work order

**Purpose:** Operations on a work order, copied from the work definition and executed

**Keys:** WO_OPERATION_ID, WORK_ORDER_ID

**Table:** WIE_WO_OPERATION_MATERIALS

**Area:** Work order

**Purpose:** Required and issued component quantities per work order operation

**Keys:** WO_OPERATION_ID, INVENTORY_ITEM_ID

**Table:** WIE_WO_OPERATION_RESOURCES

**Area:** Work order

**Purpose:** Planned and actual resource usage per work order operation

**Keys:** WO_OPERATION_ID, RESOURCE_ID

**Table:** EGP_SYSTEM_ITEMS_B

**Area:** Item and organization

**Purpose:** Item master by organization, join to resolve item numbers

**Keys:** INVENTORY_ITEM_ID, ORGANIZATION_ID

**Table:** EGP_SYSTEM_ITEMS_TL

**Area:** Item and organization

**Purpose:** Translated item descriptions, filter on LANGUAGE

**Keys:** INVENTORY_ITEM_ID, ORGANIZATION_ID, LANGUAGE

**Table:** INV_ORG_PARAMETERS

**Area:** Item and organization

**Purpose:** Inventory organization setup, including organization code and master organization

**Keys:** ORGANIZATION_ID, ORGANIZATION_CODE, MASTER_ORGANIZATION_ID

**Table:** INV_MATERIAL_TXNS

**Area:** Inventory

**Purpose:** Inventory transactions including work order issues and completions

**Keys:** TRANSACTION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID

**Table:** INV_ONHAND_QUANTITIES_DETAIL

**Area:** Inventory

**Purpose:** Current on-hand quantity by item, subinventory and lot

**Keys:** INVENTORY_ITEM_ID, ORGANIZATION_ID, SUBINVENTORY_CODE

**Notes:** Table and column names can differ by release and update. Confirm each one in the Oracle Fusion Cloud SCM Tables and Views guide for your update, or in the BI Publisher data model, before relying on it in production reports.

## Content

**Intro:** Oracle Fusion Manufacturing keeps its data in two families of tables: WIS tables for work definitions and WIE tables for work orders. This reference lists the main ones with join keys for BI Publisher reports.

**Sections:**

#### How to use this reference

**Body:** Search by table name, module area or column. Start with the work order header, WIE_WORK_ORDERS_B, then join down to operations, materials and resources through the work order or operation IDs. Join to EGP_SYSTEM_ITEMS_B on both INVENTORY_ITEM_ID and ORGANIZATION_ID to get item numbers. Join to INV_ORG_PARAMETERS to show the organization code. Always include ORGANIZATION_ID in item joins, because an item exists once per organization and a one-column join duplicates rows.

#### Work definitions versus work orders

**Body:** A work definition describes how an item is made: a versioned set of operations with materials and resources. A work order is the instance created for a quantity and date, and it copies the operations from the work definition when released. That distinction matters for reporting. If you want the standard recipe, query WIS tables. If you want what was planned and issued for a particular order, query WIE tables, since the work order can be changed after creation without altering the definition.

**Bullets:**

- Use WIS tables for routing and BOM structure
- Use WIE tables for order status, issued quantities and actual usage
- Check the version effective date when reading a work definition

#### Reporting tips for BI Publisher and OTBI

**Body:** Prefer subject areas in OTBI for ad hoc work, since they apply security and handle translations for you. Use direct SQL in BI Publisher when you need exact joins or performance control, and run it against the Fusion data source with a data model rather than ad hoc queries in production. Filter on the _B and _TL pairs correctly, and filter translation tables by LANGUAGE equals USERENV language. Test your query with a small date range first, since manufacturing tables grow quickly.

#### Common mistakes

**Body:** The most common errors are joining items on INVENTORY_ITEM_ID alone, forgetting the translation table language filter, and assuming a table or column from Oracle E-Business Suite exists in Fusion. EBS tables such as WIP_DISCRETE_JOBS do not exist in Fusion Cloud, so a migrated report needs rewriting against the WIE and WIS tables. Also confirm your role has access to the data, because Fusion applies data security to subject areas and many tables are not directly queryable in every environment.

**Cta:** Netray can put a private natural-language layer over Oracle Fusion manufacturing data so planners can ask questions without writing BIP queries. It can run on-prem or in your private cloud.

**Faq:**

#### What is the work order table in Oracle Fusion?

**Answer:** The work order header is WIE_WORK_ORDERS_B, with operations, materials and resources in related WIE tables. Verify the exact table and column names for your Fusion update in the Tables and Views guide before using them in a report.

#### What is WIS_WORK_DEFINITIONS?

**Answer:** It holds the header of a work definition, which is the versioned routing and bill of materials for an item in a manufacturing organization. Operations, materials and resources sit in related WIS tables.

#### Is WIP_DISCRETE_JOBS in Oracle Fusion?

**Answer:** No. WIP_DISCRETE_JOBS is an Oracle E-Business Suite table. Fusion Cloud Manufacturing uses WIE work order tables and WIS work definition tables, so EBS reports must be redesigned.

#### How do I get item numbers in a manufacturing query?

**Answer:** Join to EGP_SYSTEM_ITEMS_B on both INVENTORY_ITEM_ID and ORGANIZATION_ID. Add EGP_SYSTEM_ITEMS_TL filtered by language for the description.

## Search terms

oracle fusion manufacturing tables, oracle cloud manufacturing tables, WIE_WORK_ORDERS_B, WIS_WORK_DEFINITIONS, oracle fusion work order table, oracle fusion work definition tables, fusion manufacturing bip query, oracle fusion wip tables

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
