Search Results eam_meter_readings

Overview

WIP_DISCRETE_JOBS is the master table for discrete manufacturing jobs in Oracle Work in Process. Owned by the WIP schema and valid in both Oracle EBS 12.1.1 and 12.2.2, it stores one row per discrete job, recording the item being built, the quantities and dates associated with the job, the bill of material and routing references, and the general ledger accounts used to absorb and variance material, resource, overhead, and outside processing costs. Because the primary key is WIP_ENTITY_ID, the table is a specialized extension of WIP_ENTITIES, which holds the common attributes shared by discrete jobs, repetitive schedules, and flow schedules. Under the heuristic Data Vault classification derived from the foreign key structure, WIP_DISCRETE_JOBS is modeled as a hub: its identity is the WIP_ENTITY_ID business key, and its many outbound foreign keys point to descriptive and reference entities rather than to other hubs directly.

Key Information Stored

The documented physical schema contains 121 columns. The most functionally significant are listed below.

• WIP_ENTITY_ID — the surrogate primary key, defined by the WIP_DISCRETE_JOBS_PK constraint and also present in the unique index WIP_DISCRETE_JOBS_U1 (WIP_ENTITY_ID, ORGANIZATION_ID). ORGANIZATION_ID is therefore the second business-key candidate component.
• PRIMARY_ITEM_ID — the assembly being manufactured; joins to MTL_SYSTEM_ITEMS_B, MTL_ITEM_REVISIONS_B, and MTL_RTG_ITEM_REVISIONS.
• STATUS_TYPE — the job status (for example unreleased, released, complete, closed), the primary filter in most operational queries.
• JOB_TYPE, CLASS_CODE, WIP_SUPPLY_TYPE — job classification, the WIP accounting class used for cost collection, and the supply type (push, pull, assembly-to-order).
• START_QUANTITY, QUANTITY_COMPLETED, QUANTITY_SCRAPPED, NET_QUANTITY — the planned, completed, scrapped, and remaining quantities that drive completion and close processing.
• SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE, DATE_RELEASED, DATE_COMPLETED, DATE_CLOSED — the scheduling and lifecycle dates.
• BOM_REFERENCE_ID, ROUTING_REFERENCE_ID, COMMON_BOM_SEQUENCE_ID, COMMON_ROUTING_SEQUENCE_ID, BOM_REVISION, ROUTING_REVISION — the specific bill and routing revision frozen to the job.
• COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID — the default completion destination.
• MATERIAL_ACCOUNT, MATERIAL_OVERHEAD_ACCOUNT, RESOURCE_ACCOUNT, OUTSIDE_PROCESSING_ACCOUNT, OVERHEAD_ACCOUNT and the corresponding variance accounts — ten GL_CODE_COMBINATIONS foreign keys that determine how job costs and variances post to the ledger.
• PROJECT_ID, TASK_ID — Oracle Projects references for project-related jobs.

Common Use Cases and Queries

The table is the principal source for open job reports, work order listings, and WIP valuation extracts. Typical filters combine organization, status, and schedule dates. A representative query joins WIP_ENTITIES for the entity name and MTL_SYSTEM_ITEMS_B for the assembly number:

• SELECT dj.WIP_ENTITY_ID, we.WIP_ENTITY_NAME, dj.STATUS_TYPE, dj.START_QUANTITY, dj.QUANTITY_COMPLETED, dj.SCHEDULED_COMPLETION_DATE FROM WIP_DISCRETE_JOBS dj, WIP_ENTITIES we WHERE dj.WIP_ENTITY_ID = we.WIP_ENTITY_ID AND dj.ORGANIZATION_ID = :org AND dj.STATUS_TYPE IN (1,3) ORDER BY dj.SCHEDULED_COMPLETION_DATE;
• Job costing extracts select the account columns alongside quantities to reconcile material and resource absorption against WIP_PERIOD_BALANCES.
• Inquiry and update paths use WIP_ENTITIES and WIP_DISCRETE_JOBS through the WIP job definition forms and the public WIP APIs; direct DML should be restricted to controlled scripts because status transitions interact with period close.

Related Objects

• WIP_ENTITIES — joined on WIP_ENTITY_ID; supplies the job name, entity type, and common audit columns.
• MTL_SYSTEM_ITEMS_B — joined on PRIMARY_ITEM_ID and ORGANIZATION_ID to resolve assembly descriptions.
• BOM_STRUCTURES_B — joined on COMMON_BOM_SEQUENCE_ID for the frozen bill header.
• BOM_OPERATIONAL_ROUTINGS — joined on COMMON_ROUTING_SEQUENCE_ID for the frozen routing header.
• WIP_OPERATIONS and WIP_REQUIREMENT_OPERATIONS — child tables keyed by WIP_ENTITY_ID holding operation and component detail.
• WIP_PERIOD_BALANCES — period cost balances per WIP_ENTITY_ID.
• MTL_MATERIAL_TRANSACTIONS — references the job via TRANSACTION_SOURCE_ID for issue and completion activity.
• WIP_TRANSACTION_ACCOUNTS and WIP_SO_ALLOCATIONS — downstream references carrying accounting and sales order allocation detail.
• GL_CODE_COMBINATIONS — referenced by all ten account columns for ledger validation.