Results for “ahl_mc_headers_b”

50+ results




Overview
Explore in AI Chat

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

Overview

AHL_MC_HEADERS_B is the master configuration header table within the AHL (Complex Maintenance Repair and Overhaul) product module of Oracle E-Business Suite, holding the base definition records for master configurations used throughout the MRO (Maintenance, Repair, and Overhaul) process. In EBS 12.1.1 and 12.2.2, this table represents the header-level entity that anchors a complete master configuration structure, encompassing its version, revision, and naming conventions. The table is owned by the AHL schema and carries a documented physical schema of 31 columns.

Based on the FK relationship structure, the Data Vault classification for this table is hub-leaning. This suggests a modeling approach in which AHL_MC_HEADERS_B acts as a central hub, with dependent tables such as AHL_MC_CONFIG_RELATIONS and AHL_ROUTE_EFFECTIVITIES functioning as link or satellite records that reference the hub via MC_HEADER_ID. The presence of a SECURITY_GROUP_ID foreign key to FND_SECURITY_GROUPS reflects standard EBS multi-org and data security integration.

Key Information Stored

The central surrogate key is MC_HEADER_ID, enforced by the primary key constraint AHL_MC_HEADERS_B_PK and also by unique index AHL_MC_HEADERS_B_U1. Several business-key candidates are documented through unique indexes: MC_ID combined with VERSION_NUMBER (AHL_MC_HEADERS_B_U2), and NAME combined with REVISION (AHL_MC_HEADERS_B_U3). Additional unique index AHL_MC_HEADERS_B_UK1 through UK4 further constrain combinations including MC_ID, VERSION_NUMBER, NAME, and REVISION. The most significant columns include:

  • MC_HEADER_ID — surrogate primary key uniquely identifying each master configuration header record.
  • MC_ID — business identifier for the master configuration; paired with version in unique constraints.
  • VERSION_NUMBER — version indicator for the configuration, central to the versioning scheme.
  • NAME — human-readable name of the master configuration.
  • REVISION — revision label, combined with NAME in unique index U3.
  • CONFIG_STATUS_CODE — lifecycle status of the configuration.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing data access.
  • MODEL_CODE — model classification code for the configuration.
  • SOURCED_FROM_ENIGMA_FLAG — indicates whether the record originated from external Enigma data.
  • OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column consistent with EBS standards.
  • Standard who-columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
  • Descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical use cases include retrieving the current active version of a named master configuration, reporting on configuration revisions, and resolving foreign key references from downstream routing or unit configuration records. A common query pattern joins the header to its related route effectivities:

SELECT h.MC_HEADER_ID, h.MC_ID, h.VERSION_NUMBER,
       h.NAME, h.REVISION, h.CONFIG_STATUS_CODE
FROM   AHL_MC_HEADERS_B h
WHERE  h.NAME = :name
AND    h.CONFIG_STATUS_CODE = 'ACTIVE';

To resolve unit configurations referencing a master configuration:

SELECT u.MASTER_CONFIG_ID, h.NAME, h.VERSION_NUMBER
FROM   AHL_UNIT_CONFIG_HEADERS u,
       AHL_MC_HEADERS_B h
WHERE  u.MASTER_CONFIG_ID = h.MC_HEADER_ID;

Reporting scenarios frequently filter by SECURITY_GROUP_ID for data segregation and use SOURCED_FROM_ENIGMA_FLAG to identify externally sourced configurations.

Related Objects

The following tables reference AHL_MC_HEADERS_B via documented foreign keys and are the most significant for dependency analysis and joins:

  • AHL_MC_CONFIG_RELATIONS — references AHL_MC_HEADERS_B through MC_HEADER_ID; defines relationships between master configurations.
  • AHL_ROUTE_EFFECTIVITIES — references AHL_MC_HEADERS_B through MC_HEADER_ID; holds routing effectivity data per configuration.
  • AHL_UC_HEADERS_H — references AHL_MC_HEADERS_B through MASTER_CONFIG_ID; stores unit configuration headers tied to master configurations.
  • AHL_UNIT_CONFIG_HEADERS — references AHL_MC_HEADERS_B through MASTER_CONFIG_ID; associates individual units with master configurations.
  • FND_SECURITY_GROUPS — referenced by AHL_MC_HEADERS_B.SECURITY_GROUP_ID; provides the security grouping used for access control.

These relationships establish AHL_MC_HEADERS_B as a foundational hub within the AHL master configuration data model, with unit configurations, routing effectivities, and configuration relations all depending on it.