Search Results ahm_apps_configurations_v

Overview

AHM_APPS_CONFIGURATIONS_V is a reporting view shipped with the Oracle E-Business Suite Hosting Manager module (product code AHM). In EBS 12.1.1 and 12.2.2 the product is classified as obsolete, and the ETRM repository records the view as "Not implemented in this database." Its documented purpose is to filter the base configuration table by SLOT_TYPE_ID, thereby allowing different global and local application definitions to coexist within the same database instance. This design supports multi-tenant or multi-slot hosting arrangements, where each slot represents an isolated configuration context.

The view is a thin projection rather than an aggregation or join: it exposes the columns of AHM_APPS_CONFIGURATIONS while constraining the result set to a particular slot. Because AHM is deprecated, the view is not normally present in a standard EBS 12.2.2 installation, but it remains relevant when analyzing legacy customizations, archived hosting metadata, or upgrade projects that reference the AHM schema.

Underlying Base Objects

The view is defined over a single documented base object, AHM_APPS_CONFIGURATIONS. ETRM lists no additional referenced objects. The view text is a straightforward SELECT of the base table's columns, with the filtering predicate applied on SLOT_TYPE_ID at query time. Conceptually, the relationship is one-to-many from slot to configuration row: each row in AHM_APPS_CONFIGURATIONS carries a slot identifier, and the view narrows the visible rows to the slot in effect for the current session or deployment. Where a slot type is passed as a bind or filter, the calling application sees only the definitions belonging to its own hosting slot.

Key Columns

• SLOT_TYPE_ID — The discriminating column; identifies the hosting slot, enabling multiple global/local definitions per database.
• APPLICATION_ID — Oracle Applications identifier of the owning application.
• OWNER — Schema or owner associated with the configuration entry.
• REQUEST_ID — Concurrent request that generated or last touched the row.
• TABLE_ID / TABLE_NAME / TABLE_CATEGORY — Identify the configuration table targeted by the definition.
• OBJECT_VERSION_NUMBER — Optimistic locking/version stamp used by the framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context that last modified the row.

Common Use Cases and Queries

Typical usage involves inspecting which application configurations belong to a given slot, or auditing the configuration inventory of a legacy hosting deployment. A representative query filters explicitly on the slot identifier:

SELECT application_id, owner, slot_type_id, table_name,
       table_category, last_update_date
  FROM ahm_apps_configurations_v
 WHERE slot_type_id = :slot_type_id
 ORDER BY application_id, table_name;

Because the view already restricts rows by slot, queries that supply the slot value align with its intended filtering behavior. Analysts migrating off AHM may compare rows across slots to detect duplicate or conflicting definitions, or join the view to concurrent program and application metadata to reconstruct the original configuration model. In environments where the view is absent, the base table AHM_APPS_CONFIGURATIONS should be queried directly with an equivalent SLOT_TYPE_ID predicate.