Results for “csi_instance_id”

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

Overview

AHL_UC_HEADER_PATHS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AHL product family — Complex Maintenance Repair and Overhaul (CMRO). It is classified as VALID in the ETRM 12.1.1 / 12.2.2 documentation set. The view stores and exposes unit/subunit position, header, and instance information, presenting a flattened picture of the configuration hierarchy used to track complex assets and their component structure.

Functionally, the view answers the question: "For a given unit configuration header, what is its position within the master configuration, and what is the corresponding parent unit configuration (if any)?" It resolves both the unit-level and parent-level master configuration context — header, revision, master config ID, and version — alongside the relationship identifiers and position keys that define where the unit sits in the assembly. Because it joins across item-instance relationship data with date-effectivity filters, it surfaces only the currently effective component relationship for each unit at query time.

Its role in reporting and integration is to provide a denormalized join surface for CMRO configuration reporting, asset hierarchy traversal, and data extraction into external maintenance or ERP systems. Developers and report authors reference it rather than reconstructing the multi-table join themselves.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over four referenced base objects, all accessed through APPS synonyms:

• AHL_UNIT_CONFIG_HEADERS — aliased twice (U and PU) to represent the unit and its parent configuration header via the outer join on PARENT_UC_HEADER_ID.
• AHL_MC_HEADERS_B — aliased twice (CHDR and PHDR) to supply master configuration header, revision, master config ID, and version number for the unit and its parent.
• AHL_MC_RELATIONSHIPS — aliased twice (CREL and PREL). CREL supplies the primary relationship and position key where PARENT_RELATIONSHIP_ID IS NULL; PREL supplies the parent relationship context.
• CSI_II_RELATIONSHIPS — the CSI item-instance relationship table, outer-joined on subject ID with RELATIONSHIP_TYPE_CODE = 'COMPONENT-OF'.

The joins are predominantly outer joins, which allows the view to return unit records that lack a matching parent or effective CSI component relationship rather than dropping them.

Key Columns

• UC_HEADER_ID / NAME / CSI_INSTANCE_ID — identify the unit configuration header, its descriptive name, and the associated CSI item instance.
• MC_HEADER_ID / MC_REVISION / MC_ID / MC_VERSION_NUMBER — the master configuration header, revision, internal config ID, and version for the unit.
• RELATIONSHIP_ID / POSITION_KEY — the relationship record and the position key that locate the unit within its master configuration.
• PARENT_UC_HEADER_ID / PARENT_INSTANCE_ID — the parent unit configuration and parent item instance, enabling upward hierarchy traversal.
• PARENT_MC_HEADER_ID / PARENT_MC_ID / PARENT_VERSION_NUMBER — the parent's master configuration identity.
• PARENT_RELATIONSHIP_ID / PARENT_POSITION_KEY — the parent-side relationship and position key.

Common Use Cases and Queries

Typical scenarios include reporting the effective component path for a unit, reconciling parent-child assembly relationships, and extracting hierarchy data for integration.

SELECT uc_header_id, name, csi_instance_id,
       mc_id, mc_version_number, position_key,
       parent_uc_header_id, parent_position_key
FROM   apps.ahl_uc_header_paths_v
WHERE  uc_header_id = :p_uc_header_id;

To list all units that carry a resolved parent position:

SELECT uc_header_id, parent_uc_header_id, parent_position_key
FROM   apps.ahl_uc_header_paths_v
WHERE  parent_position_key IS NOT NULL;

Because the view applies TRUNC(SYSDATE) effectivity checks against CSI_II_RELATIONSHIPS.ACTIVE_START_DATE and ACTIVE_END_DATE, results always reflect the current effective component relationship. Queries should therefore not be relied upon for historical (as-of) reconstruction without adjusting that logic.