Search Results mc_id




Overview
Explore in AI Chat

Overview

The AHL_MC_HEADERS_B table is a core data object within the Oracle E-Business Suite (EBS) module for Complex Maintenance, Repair, and Overhaul (AHL). It serves as the master repository for defining and managing Master Configurations. A Master Configuration is a standardized, version-controlled template that defines the structure, components, and allowable configurations for a specific type of asset, such as an aircraft or complex piece of equipment. This table is foundational for creating and governing the specific Unit Configurations (AHL_UNIT_CONFIG_HEADERS) that represent individual physical instances of these assets throughout their lifecycle.

Key Information Stored

The table's primary identifier is the MC_HEADER_ID, a system-generated surrogate key. The data model enforces strict uniqueness through multiple unique keys, highlighting the critical business attributes. The MC_ID represents a unique identifier for the master configuration concept. The NAME and REVISION columns together define a specific, identifiable release of that configuration. The VERSION_NUMBER allows for tracking iterative changes or updates to a given NAME and REVISION combination. This structure supports complex configuration management, enabling the distinction between different models (MC_ID), their major releases (NAME/REVISION), and minor updates (VERSION_NUMBER).

Common Use Cases and Queries

This table is central to configuration lifecycle management. Common operational use cases include validating a configuration before creating a new unit, auditing configuration history, and generating master configuration catalogs. For reporting, a frequent requirement is to list all active master configurations with their latest version. A typical query pattern involves joining to the descriptive TL table (AHL_MC_HEADERS_TL) to retrieve translated names and descriptions.

  • Sample Query: Retrieving master configuration details for a specific asset type.
    SELECT mcb.mc_id, mcb.name, mcb.revision, mcb.version_number, mctl.description FROM ahl_mc_headers_b mcb, ahl_mc_headers_tl mctl WHERE mcb.mc_header_id = mctl.mc_header_id AND mctl.language = USERENV('LANG') AND mcb.name = '<Configuration_Name>';
  • Use Case: Identifying all unit configurations derived from a specific master configuration revision by joining to AHL_UNIT_CONFIG_HEADERS on MASTER_CONFIG_ID = MC_HEADER_ID.

Related Objects

The AHL_MC_HEADERS_B table has defined relationships with several key tables in the AHL schema, as documented in the ETRM metadata. These relationships are primarily established via foreign keys referencing its primary key (MC_HEADER_ID) or its unique key columns.

  • AHL_MC_CONFIG_RELATIONS: References AHL_MC_HEADERS_B via MC_HEADER_ID. This table defines hierarchical relationships and dependencies between different master configurations.
  • AHL_ROUTE_EFFECTIVITIES: References AHL_MC_HEADERS_B via MC_HEADER_ID. This links master configurations to specific maintenance routes and operational effectivities.
  • AHL_UC_HEADERS_H and AHL_UNIT_CONFIG_HEADERS: Both reference AHL_MC_HEADERS_B, using MASTER_CONFIG_ID to point to MC_HEADER_ID. This is the critical link where a physical unit's configuration (Unit Config) is instantiated from the template (Master Config).