Search Results bom_resource_schedule_type




Overview
Explore in AI Chat

Overview

The APPS.AHL_RT_OPER_RESOURCES_V view is a reporting and integration layer over the Oracle E-Business Suite Flow Manufacturing / Enterprise Territory and Resource Management (AHL) operational resource model. It presents runtime routing operation resource assignments — the resources that are scheduled against a manufacturing routing operation — joined to descriptive and reference information so that consumers receive decoded, human-readable values rather than raw lookup codes and identifiers.

Practically, the view resolves foreign keys into meaning text for cost basis, scheduled type, autocharge type, and standard rate flag, and it exposes the resource name, description, resource type, and activity name alongside the scheduling attributes (quantity, duration, schedule sequence). Because the AHL module is the underlying engine for Flow Manufacturing resource and routing data, this view is frequently used in custom concurrent programs, Oracle Reports, OBIEE / BI Publisher data models, Discoverer workbooks, and interface extracts. It is defined with ANSI-style outer joins ((+)) on the lookup and activity lookups, so rows are preserved even when a decoded value is not present.

The user's search term bom_autocharge_type maps directly to one of the view's lookup joins: the column AUTOCHARGE_TYPE_ID is decoded against the MFG_LOOKUPS view with LOOKUP_TYPE = 'BOM_AUTOCHARGE_TYPE'. This is the view's most direct relevance to that search term.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented base objects:

  • AHL_RESOURCES_V (VIEW) — provides the resource master information: NAME, DESCRIPTION, RESOURCE_TYPE_ID, and RESOURCE_TYPE. It is joined to the operation resource table on ASO.RESOURCE_ID = ARO.ASO_RESOURCE_ID. Because this is itself a view, the detail may originate from Flow/organization resource definitions.
  • AHL_RT_OPER_RESOURCES (SYNONYM) — the primary driving table, aliased ARO. It supplies the routing/operation resource assignment: IDs, other-version and audit columns, association type, object identifiers, cost basis, scheduled type, activity, autocharge type, standard rate flag, quantity, duration, schedule sequence, and the 15 descriptive flexfield attribute columns.
  • MFG_LOOKUPS (VIEW) — the Oracle Manufacturing lookup view, joined four times as a decode source: CB for CST_BASIS, ST for BOM_RESOURCE_SCHEDULE_TYPE, ACT for BOM_AUTOCHARGE_TYPE, and SR for SYS_YES_NO. Each join is an outer join keyed on lookup code plus lookup type.
  • CST_ACTIVITIES (SYNONYM) — the Costing activities table, aliased CST, joined via CST.ACTIVITY_ID (+) = ARO.ACTIVITY_ID to resolve the numeric activity to the ACTIVITY name.

The joins are predominantly outer joins, which means the operation resource row is always returned even when a lookup code or activity does not resolve.

Key Columns

  • RT_OPER_RESOURCE_ID — primary surrogate key of the routing operation resource assignment.
  • OBJECT_ID / ASSOCIATION_TYPE_CODE — identify the owning object (e.g., the operation or routing) and the nature of the association.
  • ASO_RESOURCE_ID, NAME, DESCRIPTION, RESOURCE_TYPE_ID, RESOURCE_TYPE — resource identity and classification from AHL_RESOURCES_V.
  • COST_BASIS_ID / MEANING — cost basis code and its CST_BASIS lookup meaning.
  • SCHEDULED_TYPE_ID / MEANING — schedule type and its BOM_RESOURCE_SCHEDULE_TYPE meaning.
  • AUTOCHARGE_TYPE_ID / MEANING — autocharge code and its BOM_AUTOCHARGE_TYPE meaning, the column family matching the user's search.
  • STANDARD_RATE_FLAG / MEANING — yes/no flag decoded via SYS_YES_NO.
  • ACTIVITY_ID / ACTIVITY — costing activity identifier and its name.
  • QUANTITY, DURATION, SCHEDULE_SEQ — scheduling detail for the resource on the operation.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments.
  • OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit/version columns.

Common Use Cases and Queries

A frequent requirement is to report operation resources together with their decoded autocharge behavior, using the BOM_AUTOCHARGE_TYPE lookup — the exact subject of the search term.

SELECT rt_oper_resource_id,
       name,
       resource_type,
       autocharge_type_id,
       meaning          AS autocharge_meaning,
       cost_basis_id,
       quantity,
       duration
FROM   apps.ahl_rt_oper_resources_v
WHERE  autocharge_type_id = 'MANUAL'
ORDER  BY name;

Another common scenario is filtering operations that use standard rates or a specific cost basis:

SELECT name,
       NVL(meaning,'(none)') AS standard_rate,
       schedule_seq,
       duration
FROM   apps.ahl_rt_oper_resources_v
WHERE  standard_rate_flag = 'Y'
  AND  cost_basis_id IN ('RESOURCE','MACHINE');

The view is also used to extract flexfield attributes for integrations, and to drive BI Publisher report models that summarize autocharged resources by routing operation. Because the lookup joins are outer joins, report logic should apply NVL or a default to MEANING columns to avoid nulls when a lookup value is undefined or retired.