Results for “ahl_pc_tree_v”

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

Overview

The AHL_PC_TREE_V view resides in the APPS schema and belongs to the AHL (Complex Maintenance Repair and Overhaul) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose "PC Tree info," that is, the hierarchical structure of a physical configuration (PC) tree, which in the AHL model represents the assembly of a maintained unit, its subcomponents, and associated items. The view presents both the structural nodes of the configuration hierarchy and the associations (typically unit item assignments) that hang from those nodes.

Functionally, AHL_PC_TREE_V is a reporting and integration artifact. It presents a flattened, tree-oriented projection of the physical configuration so that downstream consumers — custom reports, OBIEE extracts, interfaces, or diagnostic queries — can traverse parent/child relationships without navigating the separate node and association entities directly. Because it is a view, no data is stored within it; it is a real-time representation derived from its base objects, and it is delivered with a status of VALID in the ETRM 12.2.2 data model. The presence of standard EBS WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and the DFF attribute columns confirms it is a standard, open-interface style object suitable for BI Publisher, concurrent program output, and custom SQL.

Underlying Base Objects

The view text is a UNION of two SELECT statements, and the documented referenced base objects are:

• AHL_PC_NODES_VL (VIEW) — supplies the node-level rows, aliased AHNO in both branches.
• AHL_PC_ASSOCIATIONS_V (VIEW) — supplies the association-level rows, aliased AHASS in the second branch.

The first branch of the UNION selects directly from AHL_PC_NODES_VL. The second branch joins AHL_PC_ASSOCIATIONS_V to AHL_PC_NODES_VL on AHNO.PC_NODE_ID = AHASS.PC_NODE_ID, so the header context (PC_HEADER_ID) for association rows is resolved through the parent node record. The UNION therefore produces a single, uniform result set in which structural nodes and their associated unit items appear side by side.

Key Columns

• PC_NODE_ID — for node rows, the node identifier from AHL_PC_NODES_VL; for association rows, it carries the association identifier (PC_ASSOCIATION_ID), so consumers must use NODE_TYPE to disambiguate.
• ROW_ID — the surrogate row identifier of the source record.
• LINK_TO_NODE_ID — a self-referencing pointer used to link a row to another node in the tree. It is populated from LINK_TO_NODE_ID on node rows and from LINK_TO_ASSOCIATION_ID on association rows; this is the column most relevant to the "link_to_node_id" search.
• PARENT_NODE_ID — the parent pointer establishing hierarchy; association rows use the owning PC_NODE_ID as their parent.
• NAME / DESCRIPTION — for nodes, the node name/description; for associations, UNIT_ITEM_NAME and UNIT_ITEM_DESCRIPTION.
• NODE_TYPE — node rows are hard-coded to 'N'; association rows carry ASSOCIATION_TYPE_FLAG.
• UNIT_ITEM_ID / INVENTORY_ORG_ID — zero for nodes, real values (from AHL_PC_ASSOCIATIONS_V) for associations.
• CHILD_COUNT, DRAFT_FLAG, OPERATION_STATUS_FLAG, SECURITY_GROUP_ID — tree statistics and status/security metadata.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY — descriptive flexfield columns carried through from both sources.

Common Use Cases and Queries

Typical uses include rendering a physical configuration tree for a maintenance work order, reconciling node-to-association links, and extracting association unit items for a given configuration header. The following query lists nodes and their linked-node reference for a given PC header:

SELECT pc_node_id, name, parent_node_id, link_to_node_id, node_type
FROM   apps.ahl_pc_tree_v
WHERE  pc_header_id = :pc_header_id
ORDER  BY parent_node_id, name;

To isolate the association-level unit items (and their link pointers):

SELECT pc_node_id, name, parent_node_id, link_to_node_id,
       unit_item_id, inventory_org_id, node_type
FROM   apps.ahl_pc_tree_v
WHERE  node_type != 'N'
AND    pc_header_id = :pc_header_id;

When resolving LINK_TO_NODE_ID, note that the target may be either a node or an association depending on the row's NODE_TYPE; a self-join is therefore required to resolve the linked entity's name and description reliably.