Search Results aac_pk

Overview

AHM_APPS_CONFIGURATIONS is a configuration registry table belonging to the AHM - Hosting Manager module within Oracle E-Business Suite. The module is documented as obsolete in both the 12.1.1 and 12.2.2 releases, and the table carries a status of "Not implemented in this database" in the reference ETRM environment. Despite this status, the object definition remains catalogued because Hosting Manager was once used to manage multi-tenant hosting scenarios, where a single Oracle Applications instance served multiple operating units, legal entities, or hosted customers with differing data visibility requirements.

The table serves as a mapping between individual Oracle Applications database tables, identified through TABLE_ID against FND_TABLES, and the hosting slot or configuration context in which those tables are deployed. Its central purpose is to classify each table as Global, Local SEED, or Local Transactional, thereby telling the hosting layer which data is shared across all hosted tenants and which data is partitioned per tenant. This classification drives data separation, cloning, and provisioning logic in hosted deployments.

From a data modeling perspective, the supplied FK metadata classifies this object heuristically as standalone. In Data Vault terms it would therefore be treated as an independent satellite or reference structure rather than a hub or link, since no outgoing foreign key relationships to other hubs were mined. This classification is a modeling suggestion only and should be validated against the physical model in any implementation where the table is actually populated.

Key Information Stored

The documented column set is compact, reflecting the table's narrow role as a classification lookup:

• TABLE_NAME — the physical name of the Oracle Applications table being configured, forming part of the composite primary key.
• TABLE_ID — the numeric identifier that joins to FND_TABLES, linking the configuration record to the Applications Data Dictionary entry for the same table.
• SLOT_TYPE_ID — the hosting slot type that the table configuration applies to; this is the second component of the composite primary key.
• TABLE_CATEGORY — the classification value indicating whether the table is Global, Local SEED, or Local Transactional, which determines tenant visibility and provisioning behavior.

The primary key is documented as AAC_PK, defined over the column pair (TABLE_NAME, SLOT_TYPE_ID). TABLE_NAME plus SLOT_TYPE_ID therefore constitutes the business key: a given table may appear multiple times, once per slot type, and uniqueness is enforced only in combination. TABLE_ID is an alternate join key to the Data Dictionary but is not part of the primary key. No separate unique indexes beyond AAC_PK are documented.

Common Use Cases and Queries

In hosted or multi-tenant EBS environments, the primary use case is determining how a specific table must be treated during provisioning, cloning, or data refresh. A DBA or hosting administrator can query the classification for a given table and slot:

SELECT table_name, table_id, slot_type_id, table_category
FROM   ahm_apps_configurations
WHERE  table_name = :table_name
AND    slot_type_id = :slot_type_id;

A second common pattern is inventory reporting: listing all tables classified as Global, Local SEED, or Local Transactional to plan extraction and synchronization jobs, or to audit which tables are exempt from per-tenant partitioning. Joining to FND_TABLES via TABLE_ID allows enrichment with the Data Dictionary description and application ownership:

SELECT a.table_name, f.application_id, f.table_type, a.table_category
FROM   ahm_apps_configurations a,
       fnd_tables f
WHERE  a.table_id = f.table_id
AND    a.slot_type_id = :slot_type_id
ORDER BY a.table_name;

Because the table is documented as not implemented in the reference database, queries against it may return no rows in standard single-tenant installations; its practical relevance is confined to sites that historically operated Hosting Manager.

Related Objects

• FND_TABLES — the primary related object; joined on TABLE_ID to resolve the Applications Data Dictionary definition of each registered table.
• FND_APPLICATION — reachable through FND_TABLES.APPLICATION_ID, providing the owning product for each configured table.
• FND_TABLES.TABLE_NAME — provides an alternate join path matching AHM_APPS_CONFIGURATIONS.TABLE_NAME, useful when TABLE_ID is not populated.
• AHM slot type definition tables — the parent of SLOT_TYPE_ID; the slot type master defines the hosting contexts referenced by this table's primary key.
• Other AHM_% configuration tables — any Hosting Manager tables following the same slot-type partitioning pattern and sharing SLOT_TYPE_ID as a join column.

Given the standalone classification and absence of documented foreign keys, these relationships are logical joins rather than enforced referential constraints, and any integration should verify cardinality against the physical schema.