Search Results wip.wip_entities




The WIP.WIP_ENTITIES table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a fundamental component of the Work in Process (WIP) module, serving as a central repository for tracking discrete manufacturing jobs, repetitive schedules, and flow schedules. This table stores essential metadata about production entities, enabling organizations to manage manufacturing operations efficiently. Below is a detailed technical summary of its structure, purpose, and integration within Oracle EBS.

1. Purpose and Functional Overview

The WIP_ENTITIES table acts as the primary entity for recording work orders and production schedules in Oracle WIP. It maintains critical attributes such as job status, type, dates, and associated inventory items. Key functionalities supported by this table include:
  • Job Creation & Tracking: Stores discrete jobs, repetitive schedules, and flow manufacturing data.
  • Status Management: Tracks lifecycle states (e.g., "Unreleased," "Released," "Complete," "Closed").
  • Integration: Links to BOM, Inventory, and Costing modules for material and resource transactions.

2. Key Columns and Data Structure

The table comprises columns that define the production entity’s properties and relationships:
  • WIP_ENTITY_ID: Primary key, uniquely identifying each job/schedule.
  • ORGANIZATION_ID: Links to the inventory organization (via INV.ORG_ORGANIZATION_DEFINITIONS).
  • WIP_ENTITY_NAME: User-assigned job/schedule name (e.g., "JOB-1001").
  • ENTITY_TYPE: Distinguishes between discrete (1), repetitive (2), or flow (3) schedules.
  • STATUS_TYPE: Numeric code reflecting job status (mapped to WIP.WIP_DISCRETE_JOBS or WIP_REPETITIVE_SCHEDULES).
  • PRIMARY_ITEM_ID: References the assembled item (MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID).
  • DATE_RELEASED, DATE_COMPLETED: Timestamps for job milestones.

3. Integration with Other Modules

WIP_ENTITIES integrates with core EBS modules:
  • Inventory (INV): Ties to MTL_SYSTEM_ITEMS_B for item details and MTL_PARAMETERS for organization settings.
  • Bills of Material (BOM): References BOM_BILL_OF_MATERIALS for component structures.
  • Cost Management (CST): Links to CST_COST_ELEMENTS for job costing.
  • Shop Floor: Feeds data to WIP_OPERATIONS for routing steps.

4. Technical Considerations

  • Indexing: Key columns like WIP_ENTITY_ID and ORGANIZATION_ID are indexed for performance.
  • Data Volume: Large-scale manufacturers may partition the table by ORGANIZATION_ID.
  • Audit Trails: Changes are logged in WIP_ENTITIES_TL (translations) and related audit tables.

5. Common Use Cases

  • Job Status Queries: Monitoring open jobs via STATUS_TYPE filters.
  • Reporting: Extracting job metrics (cycle times, yields) by joining with WIP_DISCRETE_JOBS.
  • API Interactions: Used by Oracle’s WIP APIs (e.g., WIP_JOB_PUB) for programmatic job creation.

6. Version-Specific Notes

  • EBS 12.1.1: Supports basic discrete/repetitive jobs; limited flow manufacturing features.
  • EBS 12.2.2: Enhanced with Oracle’s "Flow Manufacturing" enhancements, adding columns for lean scheduling.
In summary, WIP.WIP_ENTITIES is a cornerstone table for Oracle WIP, enabling end-to-end production tracking. Its design ensures seamless interoperability with other EBS modules while providing the flexibility needed for diverse manufacturing methodologies.