Results for “wip_operation_resource_usage_v”

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

Overview

The APPS.WIP_OPERATION_RESOURCE_USAGE_V view is a Work in Process (WIP) reporting and integration object in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to resolve foreign key data for the base table WIP_OPERATION_RESOURCE_USAGE, presenting denormalized, human-readable descriptive columns (such as resource and department codes) alongside the numeric key values stored in the transactional tables. Because the base usage table records resource consumption against scheduled operations using surrogate keys, the view supplies the join logic that exposes those records in a directly interpretable form. This makes it suitable for custom reports, concurrent program extracts, business intelligence layers, and interface programs that need resource usage data without reconstructing the underlying relational joins.

Underlying Base Objects

The view is defined over six documented base objects in the APPS schema: WIP_OPERATIONS, WIP_OPERATION_RESOURCES, WIP_OPERATION_RESOURCE_USAGE, and the BOM synonyms BOM_RESOURCES, BOM_DEPARTMENTS, and BOM_DEPARTMENT_RESOURCES. The core of the view is an outer join from WIP_OPERATION_RESOURCES (aliased WOR) to WIP_OPERATION_RESOURCE_USAGE (aliased WORU), matched on WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, ORGANIZATION_ID, and REPETITIVE_SCHEDULE_ID (normalized through NVL(..., -1)). The outer join ensures that scheduled resources are returned even when no usage row exists. WIP_OPERATIONS supplies the department context and links the resource to its operation. The BOM tables supply descriptive attributes: BOM_RESOURCES provides RESOURCE_CODE, while BOM_DEPARTMENTS and BOM_DEPARTMENT_RESOURCES supply DEPARTMENT_ID, DEPARTMENT_CODE, and SHARE_FROM_DEPT_ID. A filter restricts output to rows where SCHEDULED_FLAG IN (1, 3, 4).

Key Columns

• WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM — the composite identification of the discrete job or repetitive schedule, its routing operation, and the resource line within that operation.
• REPETITIVE_SCHEDULE_ID — identifies the repetitive schedule; NULL for discrete jobs.
• RESOURCE_ID, RESOURCE_CODE — the resource key and its descriptive code from BOM_RESOURCES.
• DEPARTMENT_ID, DEPARTMENT_CODE, SHARE_FROM_DEPT_ID — the department owning the resource and the shared-from department where applicable.
• START_DATE, COMPLETION_DATE — coalesced from the usage row when present, otherwise from the scheduled resource row via DECODE.
• ASSIGNED_UNITS — likewise coalesced, giving actual assigned units or the scheduled fallback.
• SCHEDULED_FLAG — status indicator of the resource row.
• SETUP — derived flag (0 or 1) indicating whether the resource has a parent resource sequence, distinguishing setup resources.
• INSTANCE_ID, SERIAL_NUMBER — the specific resource instance and serial number represented by the usage record.
• CUMULATIVE_PROCESSING_TIME — the accumulated processing time recorded on the usage row, sourced directly from WIP_OPERATION_RESOURCE_USAGE (the column of interest for users searching cumulative_processing_time). Because it comes from the outer-joined usage table, it is NULL when no usage row exists.

Common Use Cases and Queries

Typical use cases include resource utilization reporting, operation-level time analysis, and extraction feeds for costing or MES integration. The most frequent query filters by organization and job to return resource consumption with descriptive codes:

• Job resource report: SELECT wip_entity_id, operation_seq_num, resource_code, department_code, assigned_units, cumulative_processing_time FROM wip_operation_resource_usage_v WHERE organization_id = :org AND wip_entity_id = :job ORDER BY operation_seq_num, resource_seq_num;
• Setup vs. run time split: filter WHERE setup = 1 or setup = 0 to separate setup resources from run resources.
• Repetitive schedule analysis: aggregate cumulative_processing_time grouped by repetitive_schedule_id and resource_code to compare planned versus actual processing time.

Because the view performs the outer join and code resolution, queries against it are simpler and less error-prone than direct joins across the underlying WIP and BOM tables, making it a practical foundation for both online reports and batch extracts.