Results for “phantom_item_id”

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

Overview

WIP_OPERATION_RESOURCES is a transactional table in the Work in Process (WIP) module of Oracle E-Business Suite, owned by the WIP schema. It stores the resources—labor, machines, and outside processing—that are required to perform specific operations on a discrete job or repetitive schedule. Each row represents one resource requirement attached to a WIP operation, holding both the planned and relieved (actual) quantities and values associated with that resource. The table is central to shop-floor costing, capacity planning, and resource utilization reporting.

Under a heuristic Data Vault classification mined from the foreign key structure, WIP_OPERATION_RESOURCES is satellite-leaning. Its primary key (WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, REPETITIVE_SCHEDULE_ID) is largely inherited from WIP_OPERATIONS, and most of its columns are descriptive measures and attributes rather than independent business keys. In a Data Vault model, this object would typically be modeled as a satellite attached to the operation hub/link, not as an independent hub.

Key Information Stored

The surrogate/business key of the table is defined by the unique index WIP_OPERATION_RESOURCES_U1 over WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, ORGANIZATION_ID, and REPETITIVE_SCHEDULE_ID. The primary key constraint, WIP_OPERATION_RESOURCES_PK, covers the same columns minus ORGANIZATION_ID. The most operationally significant columns include:

• WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, REPETITIVE_SCHEDULE_ID — the composite identifier linking the resource to a specific operation on a job or schedule.
• RESOURCE_ID — foreign key to BOM_RESOURCES, identifying the labor or machine resource.
• ACTIVITY_ID — foreign key to CST_ACTIVITIES, tying the resource to a costing activity.
• DEPARTMENT_ID, SETUP_ID — foreign keys to BOM_DEPARTMENTS and BOM_SETUP_TYPES, indicating where the work is performed.
• USAGE_RATE_OR_AMOUNT, BASIS_TYPE, UOM_CODE, ASSIGNED_UNITS, APPLIED_RESOURCE_UNITS — the planned usage rate, its basis (per unit or per order), unit of measure, assigned quantity, and applied quantity.
• APPLIED_RESOURCE_VALUE, RELIEVED_RES_VALUE, RELIEVED_RES_UNITS, RELIEVED_RES_COMPLETION_UNITS, RELIEVED_RES_SCRAP_UNITS — the applied and relieved costs/quantities used in WIP costing and variance calculation.
• STANDARD_RATE_FLAG, AUTOCHARGE_TYPE, SCHEDULED_FLAG, FIRM_FLAG, PHANTOM_FLAG — control flags governing charging, scheduling, and phantom handling.
• START_DATE, COMPLETION_DATE, ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE — the planned and actual timing of resource consumption.

Common Use Cases and Queries

Typical reporting scenarios include operation-level resource cost rollups, shop-floor variance analysis, and resource utilization queries. A common pattern joins WIP_OPERATION_RESOURCES to WIP_OPERATIONS and BOM_RESOURCES to display resource detail for a job:

• Querying planned versus relieved resource values for a WIP entity to explain resource variances.
• Joining to BOM_RESOURCES via RESOURCE_ID to obtain resource names, descriptions, and rates for capacity planning.
• Joining to CST_ACTIVITIES via ACTIVITY_ID to group costs by costing activity for cost accounting reports.
• Auditing rows for a repetitive schedule using REPETITIVE_SCHEDULE_ID to support rate-based production analysis.
• Reconciling interface staging against final values through WIP_COST_TXN_INTERFACE and WIP_OPERATION_RESOURCE_USAGE.

Related Objects

WIP_OPERATION_RESOURCES participates in a well-defined set of relationships:

• WIP_OPERATIONS — parent table; joined on WIP_ENTITY_ID, OPERATION_SEQ_NUM, and REPETITIVE_SCHEDULE_ID.
• BOM_RESOURCES — referenced through RESOURCE_ID for resource definitions and rates.
• CST_ACTIVITIES — referenced through ACTIVITY_ID for costing activity classification.
• BOM_DEPARTMENTS — referenced through DEPARTMENT_ID.
• BOM_SETUP_TYPES — referenced through SETUP_ID for setup-related charging.
• WIP_OPERATION_RESOURCE_USAGE — child table that references this table on the same composite key columns.
• WIP_COST_TXN_INTERFACE — interface table that references this table, used during cost transaction import and processing.

Together these relationships make WIP_OPERATION_RESOURCES a pivotal detail table for WIP costing, resource scheduling, and production reporting in both 12.1.1 and 12.2.2.