Results for “ahl_item_groups_b_h”

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

Overview

The AHL_ITEM_GROUPS_B_H table is a history (audit) table within the AHL — Complex Maintenance Repair and Overhaul product of Oracle E-Business Suite. It preserves the full lifecycle of records maintained in the base item group table, AHL_ITEM_GROUPS_B, capturing each version of an item group as it is created, modified, or otherwise transitioned through its operational life. In EBS 12.1.1 and 12.2.2 the table resides in the AHL schema and is reported as VALID, with a documented physical schema of 32 columns.

The table is a date-tracked satellite of the base item group entity. Its purpose is to provide historical traceability for item group definitions, enabling reconstruction of an item group's state at any point in time. Each history row is tied to its parent item group through the ITEM_GROUP_ID column, and the primary key of the history row is a dedicated surrogate, ITEM_GROUP_H_ID. The unique index AHL_ITEM_GROUPS_B_H_U1 on ITEM_GROUP_H_ID guarantees one history record per surrogate identifier.

Key Information Stored

The most significant columns in this table are:

• ITEM_GROUP_H_ID — surrogate primary key of the history row (index AHL_ITEM_GROUPS_B_H_PK), unique via AHL_ITEM_GROUPS_B_H_U1.
• ITEM_GROUP_ID — foreign key to AHL_ITEM_GROUPS_B, identifying the base item group whose history the row records.
• NAME — the item group name as it existed at the time of the history entry.
• TYPE_CODE and STATUS_CODE — classification and lifecycle status of the item group in that version.
• SOURCE_ITEM_GROUP_ID — reference to a source item group from which this one was derived or copied.
• VERSION_NUMBER — the version sequence of the item group at the point the history row was written.
• TRANSACTION_DATE — the effective date/time of the recorded change.
• ACTION — the operation that produced the history row (for example, an insert or update event).
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling data security visibility.
• Standard audit columns: OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield (DFF) columns for the item group.

While ITEM_GROUP_H_ID is the single unique business-key candidate documented, combinations such as ITEM_GROUP_ID plus VERSION_NUMBER or TRANSACTION_DATE are conventionally used to locate a specific historical state.

Common Use Cases and Queries

Typical uses include audit reporting, as-of-date reconstruction, and change tracking. A common pattern joins the history table back to the base table on ITEM_GROUP_ID:

• Current-versus-historical comparison of an item group's NAME, STATUS_CODE, or TYPE_CODE.
• Point-in-time reporting: filter on TRANSACTION_DATE to obtain the latest history row at or before a given date.
• Change-trail extraction for compliance, using ACTION, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

A representative query joins AHL_ITEM_GROUPS_B_H h to AHL_ITEM_GROUPS_B b on h.ITEM_GROUP_ID = b.ITEM_GROUP_ID, applying an ORDER BY h.VERSION_NUMBER or h.TRANSACTION_DATE to sequence versions. Security-aware reports additionally constrain on SECURITY_GROUP_ID.

Related Objects

• AHL_ITEM_GROUPS_B — the base (non-history) item group table; joined via AHL_ITEM_GROUPS_B_H.ITEM_GROUP_ID = AHL_ITEM_GROUPS_B.ITEM_GROUP_ID.
• FND_SECURITY_GROUPS — referenced through AHL_ITEM_GROUPS_B_H.SECURITY_GROUP_ID.
• The AHL item group base table's own detail and association tables, which depend on the same ITEM_GROUP_ID parent key and are therefore logically linked to this history record.
• AHL Complex MRO concurrent programs and Oracle Forms that maintain item group definitions, which drive inserts into this history table.
• Standard EBS audit tooling and DFF value sets consuming ATTRIBUTE_CATEGORY and ATTRIBUTE1–15.