Search Results mtl_user_supply

Overview

The WIP_ENTITIES table is a core master data table within the Oracle E-Business Suite Work in Process (WIP) module, serving as the central repository for information common to all discrete jobs, repetitive schedules, and flow schedules. It functions as the primary identifier and control record for any manufacturing work order entity within the system. Every job or schedule created in Oracle WIP is assigned a unique WIP_ENTITY_ID and a corresponding WIP_ENTITY_NAME, which are stored in this table. Its role is to provide a unified reference point for transactional and costing processes, linking the work order to its associated item, organization, and numerous supporting transactions and interfaces.

Key Information Stored

The table's structure is defined by its primary and unique keys, which enforce critical business rules. The primary key, WIP_ENTITIES_PK, is the system-generated, unique numeric identifier WIP_ENTITY_ID. The unique key, WIP_ENTITIES_UK, enforces the uniqueness of the combination of WIP_ENTITY_NAME and ORGANIZATION_ID, ensuring no two work orders in the same organization share the same name. Other essential columns include ORGANIZATION_ID, which links the entity to its manufacturing organization in INV_ORG_PARAMETERS, and PRIMARY_ITEM_ID, which references the manufactured assembly (MTL_SYSTEM_ITEMS_B) being built. The table also stores status, date, and descriptive attributes that define the entity's lifecycle and type (e.g., discrete job vs. repetitive schedule).

Common Use Cases and Queries

This table is fundamental for reporting, data validation, and integration. Common use cases include generating work order master lists, validating job existence before transaction submission, and linking work order data to cost and material transactions. A typical query retrieves key job information by joining to item and organization tables:

• SELECT we.wip_entity_name, we.wip_entity_id, msib.segment1 item_code, we.organization_id FROM wip_entities we, mtl_system_items_b msib WHERE we.primary_item_id = msib.inventory_item_id AND we.organization_id = msib.organization_id AND we.wip_entity_name = :p_job_name;

Another critical pattern involves analyzing all transactions for a specific work order by joining WIP_ENTITIES to transactional interfaces like WIP_MOVE_TXN_INTERFACE or WIP_COST_TXN_INTERFACE via the WIP_ENTITY_ID.

Related Objects

As indicated by its extensive foreign key relationships, WIP_ENTITIES is a hub table referenced by nearly all major WIP and cost transaction tables. Key dependent transactional tables include WIP_DISCRETE_JOBS and WIP_FLOW_SCHEDULES, which store type-specific details. Transaction tables like WIP_MOVE_TRANSACTIONS and WIP_COST_TXN_INTERFACE reference it. For costing, tables such as CST_COMP_SNAPSHOT and WIP_PAC_PERIOD_BALANCES depend on it. It is also referenced by planning (MRP_ITEM_WIP_ENTITIES), quality (QA_RESULTS), purchasing (PO_REQUISITION_LINES_ALL), and serial number tracking (MTL_SERIAL_NUMBERS) modules, highlighting its enterprise-wide integration.