Results for “ahl_operation_resources”

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

Overview

The AHL_OPERATION_RESOURCES table resides in the AHL schema (Complex Maintenance Repair and Overhaul) and stores the resource requirements associated with individual job operations within a maintenance work order. Each row represents a specific resource — such as labor, equipment, or a crew skill — allocated against a work order operation, together with its planned quantity, duration, and scheduling window. In Oracle EBS 12.1.1 and 12.2.2 this table acts as the operational bridge between the maintenance execution layer (work order operations) and the manufacturing resource definition layer (BOM resources), enabling capacity planning, cost rollup, and resource scheduling for complex MRO jobs.

Heuristic Data Vault modeling classifies AHL_OPERATION_RESOURCES as satellite-leaning. This is a modeling suggestion only: the table carries descriptive and transactional attributes (quantity, duration, schedule dates, and WHO/attribute columns) attached to a parent operation, rather than functioning as a pure hub of unique business keys or a link resolving many-to-many relationships. This characteristic should guide any dimensional or Data Vault design built on top of the table.

Key Information Stored

The table contains 32 documented columns. The most significant are:

• OPERATION_RESOURCE_ID — the surrogate primary key, enforced by AHL_OPERATION_RESOURCES_PK and also backed by the unique index AHL_OPERATION_RESOURCES_U1. All foreign references from child tables point to this column.
• WORKORDER_OPERATION_ID — foreign key to AHL_WORKORDER_OPERATIONS; identifies the parent operation this resource belongs to.
• RESOURCE_ID — foreign key to BOM_RESOURCES; identifies the resource (labor, machine, or equipment) being planned.
• RESOURCE_SEQUENCE_NUM — ordering of multiple resources within the same operation.
• QUANTITY and DURATION — the planned units consumed and the expected elapsed time for the resource.
• SCHEDULED_START_DATE and SCHEDULED_END_DATE — the planned scheduling window.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org / security-group access control.
• RT_OPER_RESOURCE_ID — retained attribute supporting resource tracking.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS concurrency and audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns for customer extensions.

Common Use Cases and Queries

Typical reporting and extraction scenarios include operation-level resource loading, workload/capacity analysis, and cost estimation for MRO jobs. A common join retrieves resources for a specific work order operation:

SELECT r.operation_resource_id, r.resource_id, r.quantity, r.duration,
       r.scheduled_start_date, r.scheduled_end_date
 FROM ahl_operation_resources r
 WHERE r.workorder_operation_id = :p_operation_id
 ORDER BY r.resource_sequence_num;

To resolve resource descriptions, join to BOM_RESOURCES on RESOURCE_ID. To trace actual consumption, join to AHL_WO_OPERATIONS_TXNS on OPERATION_RESOURCE_ID. To trace assignment-level detail (who or what was assigned), join to AHL_WORK_ASSIGNMENTS. These patterns support shop-floor workload dashboards, resource utilization reports, and reconciliation between planned and actual resource usage.

Related Objects

• AHL_WORKORDER_OPERATIONS — parent operation; join on AHL_OPERATION_RESOURCES.WORKORDER_OPERATION_ID.
• BOM_RESOURCES — resource master definition; join on AHL_OPERATION_RESOURCES.RESOURCE_ID.
• AHL_WORK_ASSIGNMENTS — child table referencing this table via OPERATION_RESOURCE_ID; holds assignment detail.
• AHL_WO_OPERATIONS_TXNS — child transaction table referencing this table via OPERATION_RESOURCE_ID; captures actual resource transactions.
• FND_SECURITY_GROUPS — security grouping; join on SECURITY_GROUP_ID.