Search Results ahm_odf_tables

Overview

AHM_ODF_TABLES is a metadata repository table belonging to the Oracle Hosting Manager product family (AHM), which Oracle classifies as obsolete in release 12.1.1 and 12.2.2. The table stores table definitions that have been parsed from ODF (Oracle Definition File) files. ODF files are structured descriptor documents used during provisioning and hosting operations to declare the physical and logical schema objects that a managed application or service requires. When such a file is processed, the parsing logic extracts each table definition and persists a normalized record in AHM_ODF_TABLES, providing a queryable inventory of the tables described by the ODF rather than requiring the raw file to be re-parsed.

From a dimensional modeling perspective, the mined foreign key structure classifies AHM_ODF_TABLES as standalone, which corresponds to a satellite-style reference table that captures descriptive attributes keyed by a composite identifier. This classification is a heuristic modeling suggestion derived from the absence of outbound foreign key relationships, not a definitive statement of the physical design. The table should be treated as reference or staging metadata rather than transactional data. Because AHM is documented as "Not implemented in this database," the object may exist only as a seeded or historical definition with no active runtime population in a standard EBS 12.1.1 or 12.2.2 installation.

Key Information Stored

The documented structure exposes a small set of identity and descriptive columns:

• AOT_PK — the surrogate primary key of the row, uniquely identifying each parsed table definition.
• APPLICATION_ID — identifies the Oracle E-Business Suite application context to which the parsed definition belongs; also forms part of the primary key.
• TABLE_ID — the internal identifier of the table definition within the ODF content; also part of the primary key.
• PATCH_ID — identifies the patch or patch-set context under which the definition was loaded; also part of the primary key.

The composite primary key AOT_PK is documented as (APPLICATION_ID, TABLE_ID, PATCH_ID). This composite structure is significant: the same logical table can appear under multiple patches, and each application owns a distinct namespace of table definitions. No separate unique index or alternate business key is documented beyond this primary key, so the composite of the three business columns serves as the natural business key candidate while AOT_PK acts as the surrogate. Additional descriptive columns may exist physically but are not documented in the ETRM metadata and should not be relied upon.

Common Use Cases and Queries

The primary practical use is auditing and reconciliation: confirming which table definitions a given ODF declared for a specific application and patch level, and comparing that inventory against the objects actually created in the target schema. Typical access patterns filter on APPLICATION_ID and PATCH_ID, since these are the leading selectivity columns.

A representative query retrieves all definitions for a patch:

• SELECT application_id, table_id, patch_id FROM ahm_odf_tables WHERE patch_id = :patch_id ORDER BY application_id, table_id;
• SELECT table_id FROM ahm_odf_tables WHERE application_id = :app_id AND patch_id = :patch_id;

Because the product is obsolete, reporting against this table is generally limited to migration analysis, historical impact assessment, and cleanup validation during upgrades from 12.1.1 to 12.2.2. In a running database where the table is unimplemented, queries will return no rows, so any diagnostic logic that depends on it should degrade gracefully.

Related Objects

The metadata documents no foreign key relationships to or from AHM_ODF_TABLES, consistent with its standalone classification. Consequently, no FK-to-FK join columns can be asserted. Related objects are therefore limited to the surrounding AHM Hosting Manager metadata family and the ODF processing routines that produce these rows:

• Other AHM_ODF_* definition tables, which hold companion object types (columns, indexes, constraints) parsed from the same ODF files, joined on the APPLICATIONS_ID, TABLE_ID and PATCH_ID context.
• The ODF parsing and Hosting Manager provisioning concurrent programs that populate this table.
• FND_APPLICATION, referenced conceptually through APPLICATION_ID to resolve the owning application name.
• AD_PATCH and patch-history views, referenced conceptually through PATCH_ID to resolve patch identity.

Because the join columns above are not documented as enforced foreign keys, joins should be constructed explicitly on APPLICATION_ID and PATCH_ID and validated against the target release.