Results for “ahm_odf_tables_h”

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

Overview

AHM_ODF_TABLES_H is a history table within the Oracle E-Business Suite Hosting Manager module (product code AHM), which is documented as obsolete in EBS 12.1.1 and 12.2.2. The table stores historical definitions of database tables that were parsed from ODF (Oracle Data File / object definition file) files during the hosting management processes. Its purpose is to preserve a versioned audit trail of table metadata as it was extracted from ODF artifacts across patch applications and application processing cycles.

Because AHM is classified as obsolete, AHM_ODF_TABLES_H is not implemented in the current database, and the ETRM metadata explicitly notes "Not implemented in this database." The table remains part of the documented data model for reference and backward-compatibility purposes and may still exist in legacy environments that were upgraded from earlier AHM deployments.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This reflects the absence of documented foreign-key relationships to other objects in the ETRM metadata. In practice, the composite primary key that includes TABLE_ID, APPLICATION_ID, and PATCH_ID is consistent with a historical (type-2 style) satellite pattern, where the effective business key is the TABLE_ID/APPLICATION_ID combination and PATCH_ID represents the change context that drives versioning. Any dimensional or Data Vault implementation should treat this as a modeling suggestion rather than a documented constraint, given the limited relationship metadata.

Key Information Stored

The documented structure centers on the composite primary key AOTH_PK and the columns that make it up, with a small set of descriptive attributes. The most significant columns are:

• TABLE_ID — Identifier for the table definition parsed from the ODF file. Part of the primary key.
• APPLICATION_ID — Identifies the EBS application to which the parsed table definition belongs. Part of the primary key.
• PATCH_ID — Identifies the patch or patch context under which the table definition was captured. Part of the primary key and the principal versioning dimension.
• AOTH_PK — The named composite primary key constraint spanning TABLE_ID, APPLICATION_ID, and PATCH_ID.

The surrogate-versus-business-key distinction is important. The documented primary key is the composite AOTH_PK, which combines a probable business identifier (TABLE_ID plus APPLICATION_ID, uniquely identifying a parsed table within an application) with the versioning element (PATCH_ID). No single surrogate sequence column is documented for this table, meaning the composite key itself serves as the unique row identifier. Additional descriptive columns such as table name, column definitions, and datatype attributes are implied by the table's description ("table definitions parsed from ODF files") but are not individually named in the ETRM metadata, so they are not asserted here.

Common Use Cases and Queries

Despite its obsolete status, AHM_ODF_TABLES_H supports several historical and diagnostic scenarios, primarily in legacy environments or during migration assessment:

• Reconstructing the progression of a table definition across patch levels by grouping on TABLE_ID and APPLICATION_ID and ordering by PATCH_ID.
• Auditing which patches introduced or altered a given table definition parsed from ODF files.
• Comparing historical definitions against current data dictionary views to assess drift during upgrades.

A representative query pattern retrieves the version history for a specific table:

SELECT table_id, application_id, patch_id FROM ahm_odf_tables_h WHERE table_id = :p_table_id AND application_id = :p_app_id ORDER BY patch_id;

A second pattern counts distinct versions per application:

SELECT application_id, COUNT(DISTINCT table_id) FROM ahm_odf_tables_h GROUP BY application_id;

Because the object is not implemented in current EBS 12.1.1/12.2.2 instances, these queries are relevant mainly to archived or legacy schemas rather than active databases.

Related Objects

The ETRM metadata documents AHM_ODF_TABLES_H as standalone, with no foreign-key relationships to other tables, views, or APIs. Consequently, no join columns can be inferred from documented relationships. The table is logically associated, through its shared TABLE_ID, APPLICATION_ID, and PATCH_ID key components, with other AHM hosting-history objects that describe parsed ODF definitions, and potentially with its non-history counterpart, but such relationships are not confirmed by the provided metadata and should not be treated as documented dependencies. Any integration or join should be validated against the actual legacy schema before reliance.