Search Results ahl_uc_details_for_hgrid




Overview
Explore in AI Chat

Overview

APPS.AHL_UC_DETAILS_FOR_HGRID is a table in the Oracle EBS Complex Maintenance Repair and Overhaul (AHL) product. Despite the "details" naming convention, its documented 72-column physical schema and its unique index on UNIT_NODE_ID identify it as a materialized, flat representation of the maintenance hierarchy grid (HGRID) used by the AHL user interface. In Oracle EBS 12.1.1 and 12.2.2 the table is delivered in VALID status and is used to assemble the unit configuration tree, including node-level attributes, position data, installed component information, and disposition, condition, and severity details rendered in a single grid.

From a Data Vault modeling perspective, the metadata's heuristic FK analysis classifies this object as standalone, though a more natural interpretation is that of a snapshot or bridge-like structure. It carries identifying keys (UNIT_NODE_ID, ROOT_INSTANCE_ID, PATH_POSITION_ID) alongside descriptive columns, effectively storing the current node context for a hierarchy grid rather than a normalized entity. The table is typically populated and consumed during runtime rendering of the unit configuration screen rather than as a long-term transactional record.

Key Information Stored

The documented schema centers on identifying hierarchy context and current node content. UNIT_NODE_ID is the unique constraint key, serving as the node-level surrogate; ROOT_INSTANCE_ID anchors the top of the configuration tree, while PATH_POSITION_ID ties the node to the maintenance path position. RELATIONSHIP_ID and PARENT_REL_ID, PARENT_INSTANCE_ID, and PARENT_INSTANCE_NUMBER describe the parent-child placement of the node.

Position and instalment details are held in CURR_ITEM_ID, CURR_INSTANCE_ID, CURR_ITEM_NUMBER, CURR_INSTANCE_NUMBER, CURR_SERIAL_NUMBER, CURR_LOT_NUMBER, CURR_QUANTITY, UNIT_OF_MEASURE, ATA, and POSITION. Installed-component context is carried by INST_INSTANCE_ID, INST_ITEM_NUMBER, INST_INSTANCE_NUMBER, INST_SERIAL_NUMBER, INSTANCE_QUANTITY, INSTALL_QUANTITY, INSTALL_DATE, and REMOVAL_DATE. Node-level UI flags such as NOT_LEAF_NODE_FLAG, NODE_LEVEL, HGRID_NODE_PATH, SELECT_DISABLE_FLAG, and SEARCH_FLAG govern grid rendering and navigation.

Disposition, condition, and service details include DISPOSITION_ID, DISPOSITION_STATUS, DISPOSITION_QTY, CONDITION_ID, CONDITION_MEANING, PROBLEM_CODE, PROBLEM_MEANING, SEVERITY_ID, SEVERITY_NAME, SERVICE_TYPE_ID, SERVICE_TYPE, ESTIMATED_DURATION, and SUMMARY. These support the operational decision-making view typical of MRO activity grids.

Common Use Cases and Queries

Typical usage involves rendering the hierarchy grid for a specified root instance, showing current, installed, and disposition information together. A standard query pattern filters by root:

  • SELECT unit_node_id, node_level, hgrid_node_path, curr_item_number, curr_serial_number, disposition_status, severity_name FROM ahl_uc_details_for_hgrid WHERE root_instance_id = :root_instance_id ORDER BY hgrid_node_path;
  • SELECT unit_node_id, path_position_id, parent_instance_number, install_date, removal_date, condition_meaning FROM ahl_uc_details_for_hgrid WHERE search_flag = 'Y' AND not_leaf_node_flag = 'N';

Reporting scenarios include component removal and installation histories (via INSTALL_DATE, REMOVAL_DATE, INSTANCE_QUANTITY), disposition tracking (DISPOSITION_STATUS, DISPOSITION_QTY), and top-N problem/severity analysis grouped by PROBLEM_CODE or SEVERITY_NAME. Because the table is a grid cache, queries are usually scoped tightly by ROOT_INSTANCE_ID or PATH_POSITION_ID to avoid expensive full scans.

Related Objects

Five foreign keys are documented, providing the core join paths:

Additional related objects include the node's current and installed instance headers (keyed by CURR_INSTANCE_ID and INST_INSTANCE_ID), and the unit hierarchy structures referenced by ROOT_INSTANCE_ID, which together form the configuration tree underlying the HGRID user interface.