Search Results ahl_nr_profile_headers

Overview

AHL_NR_PROFILE_HEADERS is a table in the AHL schema, owned by the Complex Maintenance Repair and Overhaul (AHL) module of Oracle E-Business Suite. It functions as the header-level container for non-recurring (NR) profile definitions used in the maintenance and overhaul of complex assemblies, particularly in aerospace, defense, and heavy-equipment environments where fixed configuration numbers, serialization rules, and identity sequences must be tracked against individual maintenance events.

The table holds 28 documented columns in ETRM 12.2.2 and is flagged as VALID. Because the metadata exposes only one foreign key relationship—SECURITY_GROUP_ID referencing FND_SECURITY_GROUPS—the heuristic Data Vault classification suggests this object behaves as a standalone construct, functioning as a hub candidate rather than a link or satellite. In practice, the surrogate key anchors header-level profile identity, while dependent detail and attribute data would reside in related NR profile tables that the mined FK structure did not expose.

Key Information Stored

The primary surrogate key is NR_PROFILE_HEADER_ID, which uniquely identifies each NR profile header row. Business-identifying information is carried primarily by MR_TITLE (the maintenance/repair profile title) and STATUS_CODE, which governs lifecycle state across the profile record. Two sequence attributes—IDENT_SEQ_THIRD and IDENT_SEQ_FOURTH—support identity sequencing logic for profile identification, typically applied where third- and fourth-level identity components require deterministic numbering.

Standard EBS WHO columns are present and operationally important for auditing and concurrency: OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. Multi-tenant and function-security isolation is provided by SECURITY_GROUP_ID, which references FND_SECURITY_GROUPS. The remaining ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 columns constitute the standard DFF/flexfield extension area, allowing customers to store site-specific profile metadata without schema modification.

Common Use Cases and Queries

Typical reporting scenarios include listing active NR profiles, auditing profile creation and last-update history, and validating security-group assignment. A basic profile listing looks like:

• SELECT NR_PROFILE_HEADER_ID, MR_TITLE, STATUS_CODE, LAST_UPDATE_DATE FROM AHL.AHL_NR_PROFILE_HEADERS WHERE STATUS_CODE = 'ACTIVE';
• Audit trace: SELECT MR_TITLE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM AHL.AHL_NR_PROFILE_HEADERS ORDER BY LAST_UPDATE_DATE DESC;
• Security reconciliation: SELECT h.NR_PROFILE_HEADER_ID, h.MR_TITLE, g.SECURITY_GROUP_NAME FROM AHL.AHL_NR_PROFILE_HEADERS h, FND_SECURITY_GROUPS g WHERE h.SECURITY_GROUP_ID = g.SECURITY_GROUP_ID;
• Flexfield reporting: query ATTRIBUTE_CATEGORY and the relevant ATTRIBUTE1..15 columns to surface descriptive flexfield values configured by the customer.

Because the table is surfaced through AHL module APIs and forms, direct DML is discouraged; modifications should be performed through the corresponding maintenance/overhaul profile maintenance UI or public API to preserve concurrency control via OBJECT_VERSION_NUMBER.

Related Objects

The most significant documented relationship is to FND_SECURITY_GROUPS, joined on SECURITY_GROUP_ID, which enforces security-group partitioning. The surrogate primary key NR_PROFILE_HEADER_ID is expected to be referenced by dependent NR profile detail tables within the AHL schema, though the mined FK data did not enumerate those children. Practically, the header is consumed alongside AHL maintenance/overhaul profile definitions, the standard WHO audit views sourced from FND_USER, and the DFF metadata stored in FND_DESCRIPTIVE_FLEXS when flexfield values are validated. When integrating or extracting, join the header to these companion objects using NR_PROFILE_HEADER_ID, SECURITY_GROUP_ID, and the audit WHO columns to assemble a complete, secure, and auditable profile view.