Results for “mrp_schedule_consumptions”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WIP_ENTITIES is the master table for Oracle Work in Process in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the information common to all work orders, including discrete jobs, repetitive schedules, and flow schedules, and acts as the parent entity from which job-specific details are derived. Every production, costing, shop floor, and material transaction in the WIP module ultimately resolves back to a single row in WIP_ENTITIES through the WIP_ENTITY_ID surrogate key. The table is owned by the WIP schema and is classified as VALID across the supported releases.

The heuristic Data Vault classification supplied by the ETRM metadata identifies WIP_ENTITIES as a hub. Under a Data Vault modeling approach, this suggests that WIP_ENTITY_ID should be persisted as a durable business key that links many dependent satellites and link tables. In practice, WIP_ENTITIES behaves as the central anchor to which dozens of transactional and interface tables attach, which is consistent with the hub classification.

Key Information Stored

The physical schema documented for 12.2.2 contains 16 columns. The most significant are listed below.

• WIP_ENTITY_ID — the surrogate primary key, enforced by WIP_ENTITIES_PK and WIP_ENTITIES_U1. All foreign key relationships in the module reference this column.
• WIP_ENTITY_NAME — the user-visible job or schedule name; together with ORGANIZATION_ID, it forms the business-key candidate WIP_ENTITIES_U2.
• ORGANIZATION_ID — the inventory organization in which the job was created; also the foreign key to WIP_PARAMETERS.
• ENTITY_TYPE — distinguishes the entity category (discrete job, repetitive schedule, flow schedule).
• PRIMARY_ITEM_ID — the assembly item being built; foreign key to MTL_SYSTEM_ITEMS_B.
• DESCRIPTION — free-text description of the entity.
• GEN_OBJECT_ID — links the entity to its work-order object definition.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — concurrent program context that created or last modified the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

WIP_ENTITIES is used to resolve job identity in reporting, costing, and interface processing. A typical lookup joins the entity to its job detail table:

SELECT we.wip_entity_id,
       we.wip_entity_name,
       we.entity_type,
       wdj.status_type
  FROM wip.wip_entities we,
       wip.wip_discrete_jobs wdj
 WHERE we.wip_entity_id = wdj.wip_entity_id
   AND we.organization_id = :org_id;

Costing inquiries frequently join the entity to standard cost adjustment tables. Since the user searched for cst_std_cost_adj_debug, the relevant pattern resolves the debug rows back to the job:

SELECT d.wip_entity_id,
       e.wip_entity_name,
       d.cost_update_id
  FROM cst.cst_std_cost_adj_debug d,
       wip.wip_entities e
 WHERE d.wip_entity_id = e.wip_entity_id;

Common reporting scenarios include open job listings by organization, pending transaction interface reconciliation, shop floor status monitoring, and variance analysis that aggregates WIP_TRANSACTIONS by entity.

Related Objects

The ETRM relationship data identifies WIP_ENTITIES as a hub with two outgoing foreign keys and numerous inbound references. The most significant related tables include:

• WIP_DISCRETE_JOBS via WIP_ENTITY_ID — job-specific attributes.
• WIP_REPETITIVE_ITEMS via WIP_ENTITY_ID — repetitive schedule definition.
• WIP_FLOW_SCHEDULES via WIP_ENTITY_ID — flow schedule definition.
• WIP_TRANSACTIONS and WIP_MOVE_TRANSACTIONS via WIP_ENTITY_ID — shop floor activity.
• WIP_COST_TXN_INTERFACE and WIP_MOVE_TXN_INTERFACE via WIP_ENTITY_ID — inbound staging.
• CST_STD_COST_ADJ_DEBUG, CST_STD_COST_ADJ_TEMP, and CST_STD_COST_ADJ_VALUES via WIP_ENTITY_ID — standard cost adjustment processing.
• MTL_SYSTEM_ITEMS_B via PRIMARY_ITEM_ID and ORGANIZATION_ID — assembly master.
• MTL_SERIAL_NUMBERS via ORIGINAL_WIP_ENTITY_ID — serial genealogy.

These relationships confirm WIP_ENTITIES as the central junction for WIP, costing, and material tracking transactions.