Search Results wip_entities




The WIP_ENTITIES table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a fundamental data structure within the Work in Process (WIP) module. It serves as the primary repository for tracking discrete manufacturing jobs, repetitive schedules, and associated work orders. This table is integral to managing production operations, cost accounting, and shop floor control in Oracle Manufacturing.

Table Structure and Key Columns

The WIP_ENTITIES table contains critical columns that define work orders and their attributes:
  • WIP_ENTITY_ID - Primary key identifier for each work order or repetitive schedule.
  • ORGANIZATION_ID - Links to the manufacturing organization where the work is performed.
  • WIP_ENTITY_NAME - The work order number or repetitive assembly identifier.
  • ENTITY_TYPE - Distinguishes between discrete jobs (1) and repetitive schedules (2).
  • STATUS_TYPE - Tracks work order lifecycle (1=Unreleased, 2=Released, 3=Complete, 4=On Hold, 5=Cancelled).
  • PRIMARY_ITEM_ID - References the manufactured item from MTL_SYSTEM_ITEMS_B.
  • DATE_RELEASED - Timestamp when the work order was released to production.
  • DATE_COMPLETED - Timestamp when the work order was completed.
  • START_QUANTITY - Planned quantity for the work order.
  • QUANTITY_COMPLETED - Actual completed quantity.

Functional Relationships

The WIP_ENTITIES table maintains relationships with several key Oracle Manufacturing tables:
  • MTL_SYSTEM_ITEMS_B - For item master data through PRIMARY_ITEM_ID
  • WIP_OPERATIONS - Stores routing operations for the work order
  • WIP_REQUIREMENTS - Contains component requirements for the work order
  • WIP_TRANSACTIONS - Records material and resource transactions
  • CST_COST_DETAILS - Stores cost accumulation details

Business Process Integration

The table supports multiple manufacturing processes:
  1. Work Order Creation - New records are inserted when discrete jobs or repetitive schedules are created
  2. Status Management - STATUS_TYPE tracks work order progression through its lifecycle
  3. Material Consumption - Component requirements are linked via WIP_ENTITY_ID
  4. Production Reporting - QUANTITY_COMPLETED is updated through WIP transactions
  5. Cost Collection - Provides the foundation for WIP accounting and variance analysis

Technical Considerations

Key technical aspects of the WIP_ENTITIES table include:
  • Indexed on WIP_ENTITY_ID, ORGANIZATION_ID, and WIP_ENTITY_NAME for performance
  • Maintained through standard Oracle APIs (WIP_JOB_DISPATCH_PUB, WIP_REPETITIVE_PUB)
  • Subject to Oracle's data integrity constraints and validation rules
  • Integrated with Oracle's concurrent processing framework

Customization and Extension

While the core table structure should not be modified, common extension approaches include:
  • Adding descriptive flexfields for custom attributes
  • Creating database triggers for supplemental validation
  • Developing custom views that join with WIP_ENTITIES
  • Implementing custom APIs that reference the table
The WIP_ENTITIES table remains a critical component of Oracle's manufacturing solution, providing the structural foundation for production tracking, cost management, and shop floor control in both discrete and repetitive manufacturing environments.