Search Results ahl_visit_ir_uc_details

Overview

AHL_VISIT_IR_UC_DETAILS is a table owned by the AHL schema within the Oracle E-Business Suite product family AHL - Complex Maintenance Repair and Overhaul. It is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. The table supports visit-level unit configuration (UC) and item routing detail, providing a flattened, hierarchical snapshot of the maintenance visit structure relevant to a given visit, item group, and maintenance configuration header. It records each unit or position instance involved in a visit alongside routing, position, and material attributes, enabling downstream reporting and processing for complex MRO workflows.

The metadata classifies this object heuristically as standalone within a Data Vault model. In practice this suggests treating the table as neither a classic hub nor a link satellite, but rather as a denormalized detail structure. A modeling exercise would likely place VISIT_ID, MC_HEADER_ID, ITEM_GROUP_ID, and PATH_POSITION_ID as reference keys, with the remaining columns interpreted as descriptive attributes.

Key Information Stored

The table contains 44 documented columns. The surrogate primary key is VISIT_IR_UC_ID, which is also the business-key candidate identified by the unique index SYS_C001035567. Significant attributes include:

• VISIT_ID — FK to AHL_VISITS_B; ties the row to a specific maintenance visit.
• MC_HEADER_ID — FK to AHL_MC_HEADERS_B; links to the maintenance configuration header.
• ITEM_GROUP_ID / ITEM_GROUP_NAME — FK to AHL_ITEM_GROUPS_B, with descriptive name for reporting.
• PATH_POSITION_ID — FK to AHL_MC_PATH_POSITIONS; identifies the position within the configuration path.
• CURR_ITEM_ID, CURR_INSTANCE_ID, CURR_ITEM_NUMBER, CURR_INSTANCE_NUMBER, CURR_SERIAL_NUMBER — the current item and installed instance identity.
• PARENT_INSTANCE_ID, PARENT_REL_ID, NODE_LEVEL, LEAF_NODE_FLAG, HGRID_NODE_PATH — hierarchy and tree-mapping attributes.
• INST_ROUTING_ID, INST_ROUTING_CODE, INST_ROUTING_MEANING, INST_ROUTING_FLAG — routing decision metadata for the instance.
• QTY_PER_POSITION, INSTALLED_QTY, AVAILABLE_PARTS — quantity and availability metrics.
• IS_UNIT, IS_WARRANTY_AVAILABLE, IS_VISIT_AVAILABLE, IS_SB_RULE_AVAILABLE — boolean readiness flags.
• POSITION_IMAGE, POSITION, UNIT_NAME, UNIT_NHA — descriptive and image reference fields.

Common Use Cases and Queries

This table is typically queried to enumerate all unit configuration rows associated with a visit, to drive work-order planning, or to expose routing and hierarchical position detail for reporting. A common pattern retrieves visit details joined to descriptive headers:

• Selecting all routing details for a visit: SELECT * FROM AHL_VISIT_IR_UC_DETAILS WHERE VISIT_ID = :visit_id.
• Identifying leaf nodes and hierarchy level for a specific position: filtering on LEAF_NODE_FLAG = 'Y' or NODE_LEVEL.
• Reporting installed quantities versus quantity per position for a maintenance configuration: joining on MC_HEADER_ID and ITEM_GROUP_ID.
• Checking warranty and part availability: filtering on IS_WARRANTY_AVAILABLE, IS_VISIT_AVAILABLE, and AVAILABLE_PARTS.
• Extracting routing code meaning for defined instances via INST_ROUTING_CODE and INST_ROUTING_MEANING.

Related Objects

The FK relationships documented in the metadata identify the primary reference objects:

• AHL_VISITS_B — via VISIT_ID; the master visit header.
• AHL_MC_HEADERS_B — via MC_HEADER_ID; the maintenance configuration header.
• AHL_ITEM_GROUPS_B — via ITEM_GROUP_ID; item group definition.
• AHL_MC_PATH_POSITIONS — via PATH_POSITION_ID; configuration path position.
• Related child or dependent tables within the AHL visit and unit configuration schema typically include visit instance, routing, and work-order detail structures keyed by VISIT_ID and MC_HEADER_ID.

Together these objects form the backbone of AHL visit-based maintenance planning, with AHL_VISIT_IR_UC_DETAILS serving as the consolidated detail layer for unit configuration, routing, and position metadata.