Search Results is_unit

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, AHL.AHL_VISIT_IR_UC_DETAILS is a global temporary table owned by the AHL (Complex Maintenance, Repair and Overhaul) schema. It is defined as an FND Design Data object with VALID status. The table stores the transient, session-scoped detail rows that underpin the Visit Installation / Removed Unit-Component (IR_UC) hierarchy used by the maintenance visit workbench and its Hierarchical Grid (HGrid) interface. Because it is a global temporary table with a data duration of SYS$TRANSACTION, only the session that inserted a given row can see it, and that row is purged automatically at the end of the transaction. This design makes the table an ideal staging structure for building and rendering a tree of installed and removed unit components during a visit, without leaving persistent residue in the database.

From a Data Vault modeling perspective the ETRM-derived heuristic classifies this object as standalone. It is best treated as a transient satellite or staging structure rather than a durable hub or link: no persistent foreign-key lifecycle is enforced, and its content is regenerated per session. Its HGRID_NODE_PATH column, which the user searched for, is the attribute that drives the navigation path displayed in the hierarchical grid.

Key Information Stored

The table spans 44 documented columns. The most operationally significant are:

• VISIT_IR_UC_ID — surrogate primary key and the single-column UNIQUE index (SYS_C001035567); the only unique business-key candidate.
• ROOT_INSTANCE_ID and PARENT_INSTANCE_ID — anchor the hierarchy and define parent-child linkage between assembled instances.
• UNIT_HEADER_ID, UNIT_NAME, and UNIT_NHA — identify the top-level maintained unit.
• CURR_ITEM_ID, CURR_INSTANCE_ID, CURR_ITEM_NUMBER, CURR_INSTANCE_NUMBER, and CURR_SERIAL_NUMBER — the current component at each tree node.
• POSITION and HGRID_NODE_PATH — the display position and the fully qualified grid navigation path used by the HGrid renderer (length 240).
• PATH_POSITION_ID, RELATIONSHIP_ID, and PARENT_REL_ID — structural links to path positions and component relationships.
• NODE_LEVEL and LEAF_NODE_FLAG — depth and terminal-node indicators for tree traversal.
• ITEM_GROUP_ID / ITEM_GROUP_NAME, MC_HEADER_ID, and VISIT_ID — grouping and visit context.
• MR_COUNT, TASK_COUNT, IS_VISIT_AVAILABLE, IS_WARRANTY_AVAILABLE, and IS_UNIT — aggregate and availability flags.

Common Use Cases and Queries

Typical scenarios include populating the visit workbench grid, validating an installed component tree prior to visit completion, and reporting on removal/replacement planning. Because the table is session-temporary, callers must insert and query within the same transaction. A common retrieval pattern orders rows by the hierarchy path:

• SELECT VISIT_IR_UC_ID, UNIT_NAME, CURR_ITEM_NUMBER, POSITION, NODE_LEVEL, HGRID_NODE_PATH FROM AHL.AHL_VISIT_IR_UC_DETAILS WHERE VISIT_ID = :visit_id ORDER BY HGRID_NODE_PATH;
• Filtering leaf nodes: WHERE LEAF_NODE_FLAG = 'Y';
• Counting tasks and maintenance requirements per instance using TASK_COUNT and MR_COUNT;
• Joining PATH_POSITION_ID to AHL_MC_PATH_POSITIONS to resolve the physical route path.

Related Objects

The following objects are referenced from this table and are the principal join targets:

• AHL.AHL_MC_PATH_POSITIONS — joined on PATH_POSITION_ID.
• AHL.AHL_ITEM_GROUPS_B — joined on ITEM_GROUP_ID.
• AHL.AHL_MC_HEADERS_B — joined on MC_HEADER_ID.
• AHL.AHL_VISITS_B — joined on VISIT_ID, providing the containing visit.
• Related AHL visit/hierarchy base objects that supply instance, item, and routing context consumed during grid population.