Results for “ahl_pc_headers_b”

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

Overview

AHL_PC_HEADERS_B is a base table in the AHL schema, owned by the Complex Maintenance Repair and Overhaul (CMRO) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information about Product Classification headers, which are the top-level definitions used to group repairable items, components, and assemblies throughout the CMRO product classification hierarchy. Each row represents a single classification header that anchors a tree of related classification nodes.

Under the heuristic Data Vault classification derived from its foreign key topology, this table leans toward a hub. In practice it behaves as the durable anchor of a classification hierarchy: it carries the natural business identity of a product classification together with its descriptive state attributes, while dependent tables such as AHL_PC_NODES_B hold the hierarchical detail.

Key Information Stored

• PC_HEADER_ID — surrogate primary key that uniquely identifies each product classification header and links it to all child nodes.
• NAME — the business name of the classification header; combined with STATUS, it forms the unique business key AHL_PC_HEADER_B_UK1 (also indexed as AHL_PC_HEADERS_B_U1).
• STATUS — lifecycle state of the classification header, forming the second half of the unique business key.
• PRODUCT_TYPE_CODE — identifies the product type to which the classification applies.
• PRIMARY_FLAG — indicates whether this header is the primary classification for the associated product.
• ASSOCIATION_TYPE_FLAG — controls how the classification associates to related items.
• DRAFT_FLAG — marks headers still under construction rather than released for use.
• LINK_TO_PC_ID — self-referencing link to a related product classification header.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces multi-org and data security partitioning in a multi-tenant implementation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Forms and OAF frameworks to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Who columns for auditing and incremental extraction.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF flexfield segment used for extension without schema change.

Common Use Cases and Queries

The most common reporting requirement is to list all active classification headers for a given security group, and to trace the node structure beneath each header. A simple pattern:

SELECT h.pc_header_id, h.name, h.status, h.product_type_code,
       h.draft_flag, h.primary_flag
FROM   ahl_pc_headers_b h
WHERE  h.status = 'ACTIVE'
AND    h.security_group_id = :p_security_group_id
ORDER  BY h.name;

To trace hierarchy membership, join to the dependent node table on the shared key:

SELECT h.name AS header_name, n.pc_node_id, n.pc_header_id
FROM   ahl_pc_headers_b h, ahl_pc_nodes_b n
WHERE  h.pc_header_id = n.pc_header_id
AND    h.draft_flag = 'N';

Incremental extracts for data-warehouse loads should filter on LAST_UPDATE_DATE and include OBJECT_VERSION_NUMBER for change detection. Because DRAFT_FLAG and STATUS drive end-user visibility, most functional reports filter on both before exposing classification data.

Related Objects

• AHL_PC_NODES_B — the child classification node table; joined via AHL_PC_NODES_B.PC_HEADER_ID = AHL_PC_HEADERS_B.PC_HEADER_ID.
• FND_SECURITY_GROUPS — referenced by AHL_PC_HEADERS_B.SECURITY_GROUP_ID, governing row-level access.
• FND_OBJECTS / FND_USER — indirectly referenced through the Who columns for audit reporting.
• AHL_PC_HEADERS_TL — the translated (language) table that is typically queried alongside the base table for localized names.
• CMRO product classification APIs and concurrent programs that create and maintain headers through the AHL product classification setup. As these records propagate through node, association, and link tables, they should be preserved through any migration or re-implementation.