Search Results wip_discrete_jobs

Overview

The WIP_DISCRETE_JOBS table is the central transactional repository for discrete manufacturing jobs within Oracle E-Business Suite Work in Process (WIP) module. It stores the master definition and current status of every discrete job created in the system, which represents a specific production order for a standard item. This table is fundamental to the manufacturing execution lifecycle, tracking a job from its creation and release through to its completion and closure. Its integrity is maintained by the primary key constraint WIP_DISCRETE_JOBS_PK on the WIP_ENTITY_ID column, ensuring each job has a unique identifier. The table's extensive foreign key relationships with core inventory, bill of material, and general ledger tables underscore its critical role in integrating manufacturing operations with financial and supply chain management.

Key Information Stored

The table's columns can be categorized into several key functional areas. The primary identifier is WIP_ENTITY_ID, which is the unique system-generated key for the job. Essential descriptive and control columns include ORGANIZATION_ID, PRIMARY_ITEM_ID, JOB_NAME, DESCRIPTION, and STATUS_TYPE, which defines the job's current state (e.g., Unreleased, Released, Complete, On Hold, Cancelled). Manufacturing execution data is captured through fields like START_QUANTITY, QUANTITY_COMPLETED, QUANTITY_SCRAPPED, and SCHEDULED_START_DATE. The table also holds critical references to product definitions via BOM_REVISION, ROUTING_REVISION, COMMON_BOM_SEQUENCE_ID, and COMMON_ROUTING_SEQUENCE_ID. A significant portion of the table's structure is dedicated to financial integration, storing the general ledger accounts for cost accumulation and variance posting, such as MATERIAL_ACCOUNT, RESOURCE_ACCOUNT, OVERHEAD_ACCOUNT, and their corresponding variance accounts (e.g., MATERIAL_VARIANCE_ACCOUNT).

Common Use Cases and Queries

This table is central to operational reporting, performance analysis, and data extraction. Common queries involve retrieving a list of active jobs, analyzing job status, and calculating work-in-process valuations. A fundamental query to list all released jobs for a specific organization would filter on STATUS_TYPE and ORGANIZATION_ID. For cost analysis, a join with the GL_CODE_COMBINATIONS table on the material and resource account columns allows for the reconciliation of WIP balances. Technical integrations often query this table to validate job existence or to extract job details for interfacing with external MES systems. A typical pattern for job summary reporting involves joining WIP_DISCRETE_JOBS with MTL_SYSTEM_ITEMS_B on PRIMARY_ITEM_ID and ORGANIZATION_ID to include item details.

SELECT wdj.JOB_NAME,
       wdj.DESCRIPTION,
       msi.CONCATENATED_SEGMENTS ITEM,
       wdj.STATUS_TYPE,
       wdj.START_QUANTITY,
       wdj.QUANTITY_COMPLETED
FROM WIP.WIP_DISCRETE_JOBS wdj,
     INV.MTL_SYSTEM_ITEMS_B msi
WHERE wdj.ORGANIZATION_ID = msi.ORGANIZATION_ID
  AND wdj.PRIMARY_ITEM_ID = msi.INVENTORY_ITEM_ID
  AND wdj.ORGANIZATION_ID = :p_org_id
  AND wdj.STATUS_TYPE IN (3, 4) -- Released, Complete
ORDER BY wdj.SCHEDULED_START_DATE;

Related Objects

As indicated by its foreign keys, WIP_DISCRETE_JOBS has deep dependencies across multiple EBS modules. Its primary relationships are with Inventory (MTL_SYSTEM_ITEMS_B, MTL_ITEM_REVISIONS_B, MTL_RTG_ITEM_REVISIONS, MTL_SECONDARY_LOCATORS), Bills of Material (BOM_STRUCTURES_B, BOM_OPERATIONAL_ROUTINGS), and General Ledger (GL_CODE_COMBINATIONS, referenced by numerous accounting columns). Transactional child tables, such as WIP_TRANSACTIONS and WIP_OPERATIONS, record the material and resource movements against the job master record defined here. For programmatic interaction, the Oracle-supplied WIP_JOB package provides public APIs for creating, updating, and managing discrete jobs, which internally manipulate this table. Key views like WIP_DISCRETE_JOBS_V provide application-level abstractions of the underlying table data.