Results for “ahl_unit_config_headers_v”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The AHL_UNIT_CONFIG_HEADERS_V view is a reporting and integration construct in the Oracle E-Business Suite (EBS) AHL – Complex Maintenance Repair and Overhaul (CMRO) module. It exposes a denormalized, human-readable representation of unit configuration headers, master configuration headers, and the hierarchical relationships that link a unit configuration (UC) to its parent UC, root UC, and parent item instance. Unit configurations represent the as-maintained structure of a serialized or lot-controlled asset, so this view is the primary access point for reporting on asset configuration state without requiring callers to reconstruct the AHL and CSI base-table joins themselves. Because the object is owned by the APPS schema and has a status of VALID, it is intended for direct querying by operational reports, BI Publisher data templates, OAF/ADF integration layers, and custom concurrent programs. The descriptive lookup meanings (config status, active status, position reference) are resolved inline, which removes the need for downstream consumers to join FND_LOOKUP_VALUES. The view is available in both EBS 12.1.1 and 12.2.2, and the documented metadata set is present in the ETRM repository for 12.2.2.
Underlying Base Objects
The view is defined over the AHL and CSI transactional tables, with supporting joins to inventory and lookup infrastructure. The documented referenced base objects are:
- AHL_UNIT_CONFIG_HEADERS (synonym) — the driving table, aliased U; supplies the unit configuration header record and self-references through PARENT_UC_HEADER_ID to build the hierarchy.
- AHL_MC_HEADERS_B / AHL_MC_HEADERS_TL (synonyms) — master configuration header and its translations, joined via MASTER_CONFIG_ID to return the master config name, revision, status, and description.
- AHL_MC_RELATIONSHIPS (synonym) — master configuration hierarchy relationship, filtered to the root relationship (PARENT_RELATIONSHIP_ID IS NULL) to yield the position reference and active dates.
- CSI_ITEM_INSTANCES (synonym) — the item instance (asset) record, joined on CSI_ITEM_INSTANCE_ID to INSTANCE_ID, providing instance number, serial number, and lot number.
- CSI_II_RELATIONSHIPS (synonym) — instance relationship data that anchors the configuration to a parent instance.
- MTL_SYSTEM_ITEMS_KFV (synonym) — key flexfield view supplying the concatenated item segments for the configured item.
- FND_LOOKUP_VALUES_VL (synonym, used multiple times) — decodes UNIT_CONFIG_STATUS_CODE, ACTIVE_UC_STATUS_CODE, CONFIG_STATUS_CODE, and POSITION_REF_CODE into lookup meanings.
- MTL_PARAMETERS, INV_ORGANIZATION_INFO_V, MO_GLOBAL — supporting inventory/organization context objects referenced in the full view definition.
Key Columns
- UNIT_CONFIG_HEADER_ID — primary key of the unit configuration header; the value most commonly used as a query predicate and foreign key.
- NAME — unit configuration name; also exposes the master configuration NAME, REVISION, and DESCRIPTION.
- MASTER_CONFIG_ID — link to the master configuration header record.
- CSI_ITEM_INSTANCE_ID plus CONCATENATED_SEGMENTS, INSTANCE_NUMBER, SERIAL_NUMBER, LOT_NUMBER — identify the physical asset or lot the configuration describes.
- PARENT_UC_HEADER_ID and the derived root column (the scalar subquery returning the top-level UNIT_CONFIG_HEADER_ID) — define hierarchy position: parent UC and root UC.
- CONFIG_STATUS_CODE / MCSC.MEANING and UNIT_CONFIG_STATUS_CODE / UCSC.MEANING, ACTIVE_UC_STATUS_CODE / UASC.MEANING — decoded configuration and activation states.
- ACTIVE_START_DATE / ACTIVE_END_DATE (unit configuration, item instance, and master relationship) — effective-dating for the configuration and its relationships.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns for customer-extended reporting.
- Template/audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.
Common Use Cases and Queries
Typical scenarios include listing all configurations attached to a serialized asset, reporting active versus inactive configurations, and traversing the UC hierarchy to identify the root configuration for a given child. The following query retrieves active configurations with their asset and master configuration context:
SELECT unit_config_header_id, name, instance_number, serial_number,
master_config_id, unit_config_status_code, active_start_date
FROM apps.ahl_unit_config_headers_v
WHERE active_uc_status_code = 'ACTIVE';
To locate a specific configuration and its hierarchy anchors, the primary key predicate is applied directly:
SELECT unit_config_header_id, name, parent_uc_header_id
FROM apps.ahl_unit_config_headers_v
WHERE unit_config_header_id = :p_unit_config_header_id;
Because the view already resolves lookup meanings and the root UC, it is well suited to BI Publisher extract views, concurrent-program report queries, and integration staging that must publish configuration state to external maintenance or asset systems without duplicating join logic.
-
This view includes all the information related to unit configuration headers, master configuration headers, and the hierarchy of uc and its parent UC, root UC and parent instance.
APPS.AHL_UNIT_CONFIG_HEADERS_V·↳ AHL_MC_HEADERS_B·↳ AHL_MC_HEADERS_TL·↳ AHL_MC_RELATIONSHIPS·Explore AHL module →
-
This view includes all the information related to unit configuration headers, master configuration headers, and the hierarchy of uc and its parent UC, root UC and parent instance.
APPS.AHL_UNIT_CONFIG_HEADERS_V·↳ AHL_MC_HEADERS_B·↳ AHL_MC_HEADERS_TL·↳ AHL_MC_RELATIONSHIPS·Explore AHL module →
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1