Search Results ahm_svc_role_map

Overview

AHM_SVC_ROLE_MAP is a table in the Oracle E-Business Suite Hosting Manager module (product code AHM). Its documented purpose is to store the roles associated to a service in context for the hosting master. In practical terms, the table functions as an association or cross-reference table that links a service definition to one or more role definitions that are meaningful within the hosting management model. The AHM product is flagged as obsolete in the ETRM metadata, and the implementation/DBA note states that the table is "Not implemented in this database." This means that in a standard Oracle EBS 12.1.1 or 12.2.2 instance, the object may either not exist or exist only as a legacy shell with no populated data and no active application code path referencing it.

From a modeling perspective, the ETRM metadata supplies a heuristic Data Vault classification of "satellite-leaning" for this table. Treated as a modeling suggestion rather than a declarative fact, this implies the table behaves like a descriptive attribute container that hangs off a parent business entity key rather than acting as a pure hub or link. Its single documented foreign key back to AHM_SLOT_TYPE_SERVICES reinforces that interpretation: the table carries attributes (role associations) that describe a service in its hosting context.

Key Information Stored

The documented metadata exposes only a small number of columns, and these are the ones that should be treated as authoritative:

• SVC_ROLE_MAP_ID — the surrogate primary key of the table, enforced through the constraint AHM_SVC_ROLE_MAP_PK. This is a system-generated identifier with no business meaning.
• SLOT_TYPE_SERVICE_ID — the foreign key column that references AHM_SLOT_TYPE_SERVICES. This is the most significant business-key candidate visible in the metadata, since it establishes the parent service context to which the roles are attached.
• Role association columns — although the excerpt does not enumerate them, the table description states that the table stores the roles associated to a service. By inference, the table contains one or more columns identifying the role or roles being mapped, most likely a role identifier or role code that pairs with SLOT_TYPE_SERVICE_ID to form the effective business key of a role-to-service assignment.

Because the primary key is a surrogate identifier and no unique index is documented in the excerpt, SLOT_TYPE_SERVICE_ID alone cannot be assumed unique. A composite of SLOT_TYPE_SERVICE_ID plus the role identifier is the most plausible business key candidate.

Common Use Cases and Queries

Given the obsolete status and the "not implemented" note, direct querying of this table in a production 12.1.1 or 12.2.2 environment is rarely productive. The realistic use cases are historical and analytical:

• Legacy audit and migration research, where analysts reconstruct which roles were historically attached to hosting services.
• Data model impact analysis before an upgrade or decommissioning exercise, to confirm whether any custom code references the table.
• Reverse-engineering the AHM hosting model in archived or cloned environments where the table was populated in an older release.

A representative query pattern joins the table to its documented parent:

• SELECT s.SLOT_TYPE_SERVICE_ID, m.SVC_ROLE_MAP_ID FROM AHM_SVC_ROLE_MAP m, AHM_SLOT_TYPE_SERVICES s WHERE m.SLOT_TYPE_SERVICE_ID = s.SLOT_TYPE_SERVICE_ID;

Before relying on the table, a DBA should verify existence with a query against ALL_TABLES and ALL_CONSTRAINTS, since the metadata explicitly indicates the object is not implemented in the reference database.

Related Objects

The documented foreign key relationship identifies the principal related object:

• AHM_SLOT_TYPE_SERVICES — the parent table. The join column is AHM_SVC_ROLE_MAP.SLOT_TYPE_SERVICE_ID referencing AHM_SLOT_TYPE_SERVICES.SLOT_TYPE_SERVICE_ID. This is the only FK relationship supplied in the metadata and is therefore the dominant dependency.
• AHM_SVC_ROLE_MAP_PK — the primary key constraint, referenced by any child tables or dependent constraints.

Other AHM hosting manager tables related to service and role definitions, as well as any legacy role definition tables in the Oracle Applications role model, may also participate indirectly, but the ETRM excerpt does not document these relationships. Consequently, the AHM_SLOT_TYPE_SERVICES link should be treated as the authoritative and primary relationship for this object.