Search Results ahl_rt_oper_resources_v




Overview
Explore in AI Chat

Overview

The AHL_RT_OPER_RESOURCES_V view is an APPS-owned, VALID database object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, belonging to the AHL — Complex Maintenance Repair and Overhaul product family. Its purpose is to present the runtime operational resource assignments recorded against maintenance and overhaul work orders, enriching the raw identifier columns stored in the underlying transaction table with their corresponding coded meanings. The view performs the description expansion by joining AHL_RT_OPER_RESOURCES to FND_LOOKUP_VALUES_VL and related lookup sources, so that columns such as COST_BASIS_ID, SCHEDULED_TYPE_ID, AUTOCHARGE_TYPE_ID, and STANDARD_RATE_FLAG are surfaced as human-readable values (COST_BASIS, SCHEDULED_TYPE, AUTOCHARG, and the standard-rate yes/no meaning). In integration and reporting terms, the view is the recommended read interface for AHL resource-costing data, since it removes the need for callers to resolve lookup codes themselves and protects consumers from direct dependency on the base table's surrogate keys.

Underlying Base Objects

The view is defined over four documented referenced objects: AHL_RESOURCES_V (view), AHL_RT_OPER_RESOURCES (synonym), CST_ACTIVITIES (synonym), and MFG_LOOKUPS (view). The driving table is AHL_RT_OPER_RESOURCES (alias ARO), which supplies the resource-assignment rows, descriptive flexfield attributes, quantity, duration, and the foreign keys to lookup codes. The resource identity itself is resolved through AHL_RESOURCES_V (alias ASO), joined on ASO.RESOURCE_ID = ARO.ASO_RESOURCE_ID, supplying NAME, DESCRIPTION, RESOURCE_TYPE_ID, and RESOURCE_TYPE. Activity descriptions are drawn from CST_ACTIVITIES via an outer join on ACTIVITY_ID. Lookup meanings are supplied by four aliases of MFG_LOOKUPS using outer joins: CB (CST_BASIS), ST (BOM_RESOURCE_SCHEDULE_TYPE), ACT (BOM_AUTOCHARGE_TYPE), and SR (SYS_YES_NO). All lookup joins are outer joins, so a resource assignment with an unmapped code is retained with a null meaning rather than being dropped from the result set.

Key Columns

  • RT_OPER_RESOURCE_ID — Primary key of the underlying resource-assignment record.
  • ASO_RESOURCE_ID, ASO_RESOURCE_NAME, ASO_RESOURCE_DESC — Identity of the assigned resource, resolved from AHL_RESOURCES_V.
  • RESOURCE_TYPE_ID, RESOURCE_TYPE — Classification of the resource (for example labor, equipment, or service).
  • COST_BASIS_ID and COST_BASIS — The costing basis code and its CST_BASIS lookup meaning, indicating how cost is derived for the resource.
  • SCHEDULED_TYPE_ID and SCHEDULED_TYPE — Scheduling classification, described via BOM_RESOURCE_SCHEDULE_TYPE.
  • AUTOCHARGE_TYPE_ID and AUTOCHARG — Autocharge behavior, described via BOM_AUTOCHARGE_TYPE.
  • STANDARD_RATE_FLAG — Yes/no indicator, described via SYS_YES_NO, denoting use of the standard rate.
  • ACTIVITY_ID and ACTIVITY — Cost activity reference and its description from CST_ACTIVITIES.
  • QUANTITY, DURATION — Assigned resource quantity and duration values.
  • ASSOCIATION_TYPE_CODE, OBJECT_ID — Polymorphic reference identifying the parent work-order object.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns for customer-specific extensions.

Common Use Cases and Queries

The view is typically used to report resource requirements and costing attributes for maintenance work orders, to feed cost roll-up or rate-validation processes, and to drive integrations where lookup descriptions rather than codes are required. A frequent scenario is retrieving costed resource lines by cost basis:

  • Costing analysis: summarizing quantity and duration grouped by COST_BASIS to compare resource consumption across bases.
  • Resource planning: listing scheduled resources for a work order by pivoting on OBJECT_ID and ASSOCIATION_TYPE_CODE.
  • Validation and reconciliation: identifying rows where lookup meanings are null, indicating unmapped or obsolete codes.
  • Integration extracts: supplying downstream systems with fully described resource records.

A representative query filtering on the searched attribute is:

SELECT rt_oper_resource_id, aso_resource_name, resource_type, cost_basis_id, cost_basis, scheduled_type, quantity, duration
  FROM apps.ahl_rt_oper_resources_v
 WHERE cost_basis IS NOT NULL
 ORDER BY cost_basis, aso_resource_name;

Because all lookup joins are outer joins, this query returns only rows with a resolved cost basis; removing the predicate yields the complete assignment population for broader reporting.