Search Results ahl_config_status




Overview
Explore in AI Chat

Overview

The APPS.AHL_UNIT_CONFIG_HEADERS_V view presents header-level information for unit configurations within Oracle Enterprise Asset Management (eAM) and Complex Maintenance Repair and Overhaul (CMRO) modules. A unit configuration represents the hierarchical assembly of a physical asset (such as a serialized piece of equipment) and the associated master configuration model that governs its structure. This view consolidates attributes from the unit configuration header, the linked master configuration, the underlying CSI item instance, and the inventory item definition into a single queryable row.

The view is primarily used in reporting, integration, and operational queries where a flattened, human-readable representation of unit configurations is required. It joins lookup values to decode internal status codes into user-facing meanings, eliminating the need for downstream consumers to perform their own lookup resolution. This makes it well suited for Oracle Reports, BI Publisher datasets, OAF pages, and custom SQL used in data migration or interfaces.

Underlying Base Objects

The view is defined over a set of base and supporting objects. The central table is AHL_UNIT_CONFIG_HEADERS, aliased U, which holds the unit configuration header records, including status codes, parent-child relationships, and descriptive flexfield attributes (ATTRIBUTE1 through ATTRIBUTE15). The master configuration model is drawn from AHL_MC_HEADERS_B (M) and its translated name from AHL_MC_HEADERS_TL (MT), joined on the master configuration identifier and the session language.

Physical instance detail comes from CSI_ITEM_INSTANCES (C) and the related MTL_SYSTEM_ITEMS_KFV (I), providing instance number, serial number, lot number, and concatenated item segments. The AHL_MC_RELATIONSHIPS table (R) supplies the top-level position reference for the master configuration. A self-join on AHL_UNIT_CONFIG_HEADERS (PU) resolves the parent unit configuration, while CSI_II_RELATIONSHIPS (CR) exposes instance relationship data. Status meanings are resolved through four aliases of FND_LOOKUP_VALUES (UCSC, UASC, MCSC, MRSC) using lookup types such as AHL_CONFIG_STATUS. The ETRM metadata additionally lists INV_ORGANIZATION_INFO_V, MO_GLOBAL, and MTL_PARAMETERS as referenced objects that may participate through the item key flexfield view or organization security.

Key Columns

Common Use Cases and Queries

A frequent requirement is to report all unit configurations along with their decoded status. Because the view resolves the lookup internally, a simple select is sufficient:

SELECT unit_config_header_id, name, config_status_code, meaning FROM apps.ahl_unit_config_headers_v WHERE unit_config_status_code = 'ACTIVE';

Another common scenario is retrieving the master configuration context and physical instance attributes for a given asset:

SELECT u.name, u.master_config_id, u.instance_number, u.serial_number, u.active_start_date FROM apps.ahl_unit_config_headers_v u WHERE u.csi_item_instance_id = :instance_id;

Hierarchical reporting on parent-child unit configurations leverages the parent columns and the root-derivation subquery embedded in the view definition. Integration and migration programs also query this view to extract attribute flexfield values and effective dates when synchronizing unit configuration data with external maintenance systems. Because the view joins translated lookup values using USERENV('LANG'), query results are returned in the language of the executing session.