Results for “cumulative_processing_time”

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

Overview

WIP_OPERATION_RESOURCE_USAGE is a Work in Process (WIP) transactional table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model. It records the actual consumption or usage of an operation resource against a specific work order or repetitive schedule, broken down by shift and calendar information. Each row represents resource usage for a discrete interval defined by a start date, completion date, instance, and serial number, enabling detailed tracking of labor and machine time applied at the operation level within a manufacturing environment.

The table resides in the WIP schema and serves as the detail-level companion to WIP_OPERATION_RESOURCES, which defines the resource assignments for an operation. Where WIP_OPERATION_RESOURCES describes what resource is planned, WIP_OPERATION_RESOURCE_USAGE captures how much of that resource was actually consumed, when, and against which entity.

The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. In Data Vault terms, this suggests the table functions primarily as a descriptive satellite attached to a core hub or link (the work order/resource assignment), carrying measures such as assigned units and cumulative processing time alongside temporal context. This classification is a modeling suggestion derived from the FK topology rather than a documented Oracle designation.

Key Information Stored

The primary key, WIP_OPERATION_RESOURCE_USG_PK, is a composite key spanning OPERATION_SEQ_NUM, ORGANIZATION_ID, REPETITIVE_SCHEDULE_ID, RESOURCE_SEQ_NUM, START_DATE, and WIP_ENTITY_ID. A secondary unique constraint, WIP_OPERATION_RESOURCE_USG_UK, extends this with INSTANCE_ID and SERIAL_NUMBER, reflecting the need to distinguish usage rows for serialized or instance-tracked assemblies. The documented physical schema exposes 20 columns; the most significant are described below.

• WIP_ENTITY_ID — Identifier of the work order (discrete job) or repetitive schedule entity against which resource usage is recorded. This is the principal foreign-key column.
• OPERATION_SEQ_NUM — The operation sequence number within the routing, tying the usage row to a specific step of the manufacturing process.
• RESOURCE_SEQ_NUM — Sequence number identifying the specific resource within the operation, forming part of the composite key and FK relationship.
• ORGANIZATION_ID — The inventory organization in which the work order and resource usage occur.
• REPETITIVE_SCHEDULE_ID — The repetitive schedule identifier, permitting resource usage to be tracked at the repetitive schedule level.
• START_DATE / COMPLETION_DATE — The temporal boundaries of the usage interval, allowing usage to be aligned with shifts and calendars.
• ASSIGNED_UNITS — The quantity of resource units assigned or consumed during the interval.
• CUMULATIVE_PROCESSING_TIME — Accumulated processing time recorded for the resource usage, supporting costing and efficiency analysis.
• INSTANCE_ID / SERIAL_NUMBER — Instance and serial identifiers used to distinguish usage against serialized assemblies.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard Oracle EBS audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the process that created or updated the row.

Common Use Cases and Queries

Resource usage data is central to manufacturing cost rollup, resource efficiency reporting, and shop-floor analysis. Typical queries reconcile actual assigned units and processing time against planned resource requirements from WIP_OPERATION_RESOURCES.

To retrieve all resource usage for a work order:

• SELECT WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, ASSIGNED_UNITS, CUMULATIVE_PROCESSING_TIME, START_DATE, COMPLETION_DATE FROM WIP_OPERATION_RESOURCE_USAGE WHERE WIP_ENTITY_ID = :p_wip_entity_id ORDER BY OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, START_DATE;

To analyze usage within a date range for an organization:

• SELECT RESOURCE_SEQ_NUM, SUM(ASSIGNED_UNITS) units, SUM(CUMULATIVE_PROCESSING_TIME) time FROM WIP_OPERATION_RESOURCE_USAGE WHERE ORGANIZATION_ID = :p_org_id AND START_DATE BETWEEN :p_from AND :p_to GROUP BY RESOURCE_SEQ_NUM;

Reporting scenarios include resource utilization by shift, variance analysis between planned and actual resource consumption, and cost accounting feeds to the Cost Management module.

Related Objects

The documented foreign key relates WIP_OPERATION_RESOURCE_USAGE to WIP_OPERATION_RESOURCES on WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, and REPETITIVE_SCHEDULE_ID. Beyond this, the following objects are significant in the surrounding data model:

• WIP_OPERATION_RESOURCES — Parent definition of operation resource assignments; the FK target.
• WIP_DISCRETE_JOBS — Discrete work orders referenced via WIP_ENTITY_ID.
• WIP_REPETITIVE_SCHEDULES — Repetitive schedules referenced via REPETITIVE_SCHEDULE_ID.
• WIP_ENTITIES — Master entity table linking work orders and schedules.
• BOM_OPERATION_RESOURCES — Engineering definition of operation resources feeding WIP resource assignments.
• WIP_MOVE_TRANSACTIONS / WIP_TRANSACTIONS — Shop-floor transactions that drive resource usage accumulation.
• MTL_SYSTEM_ITEMS_B / MTL_PARAMETERS — Organization and item context.
• CST_* interfaces — Cost Management tables and concurrent programs that consume resource usage for cost rollup.