Search Results ahm_svc_group_map

Overview

AHM_SVC_GROUP_MAP is a table belonging to the Oracle E-Business Suite product AHM – Hosting Manager, which is documented as obsolete in the ETRM repository. Its stated purpose is to store the groups that are associated to a service in context for the hosting master. In other words, the table functions as an association store linking a service definition to one or more group records that apply to it within the hosting domain. Because the product is obsolete and the table is marked "Not implemented in this database," it does not appear as a physical object in standard installations of Oracle EBS 12.1.1 or 12.2.2. It persists in the data dictionary as a legacy artifact and may still surface in upgrade scripts, historical DDL, or pre-existing customizations.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. This suggests the table behaves as a descriptive, context-bearing structure attached to a parent entity rather than as an independent hub or a pure many-to-many link. The classification is a modeling suggestion only, derived from the single documented foreign key, and should be validated against actual lineage where the product was once deployed.

Key Information Stored

The documented metadata identifies a limited but meaningful set of columns:

• SVC_GROUP_MAP_ID – the surrogate primary key, enforced through the AHM_SVC_GROUP_MAP_PK constraint. This column uniquely identifies each row in the table and is the standard intersection point for parent-child relationships and reporting joins.
• SLOT_TYPE_SERVICE_ID – a foreign key column referencing AHM_SLOT_TYPE_SERVICES. It ties each group mapping record to a specific slot type service definition, establishing the service context referenced in the table description.

The distinction between the surrogate key and any business-key candidates is important here. SVC_GROUP_MAP_ID is purely a system-generated identifier; no unique index or alternate business key is documented in the metadata. The actual business meaning of a row is conveyed by the combination of SLOT_TYPE_SERVICE_ID and the associated group reference, which is implied by the table name and description but not enumerated as a distinct column in the supplied documentation. Any columns holding the group identifier itself, effective dates, or status flags are not documented and should be confirmed from the original DDL before being used in queries. This limitation reflects the fact that the object is obsolete and the ETRM extract is intentionally minimal.

Common Use Cases and Queries

Because the table is not implemented in current databases, use cases are largely historical, migration-oriented, or investigative. Typical scenarios include:

• Reconstructing which groups were mapped to which slot type services during legacy Hosting Manager deployments.
• Auditing pre-upgrade data before decommissioning AHM objects.
• Mapping legacy associations to replacement structures in current modules.

A representative join pattern uses the documented foreign key:

SELECT m.svc_group_map_id, m.slot_type_service_id, s.*
FROM ahm_svc_group_map m, ahm_slot_type_services s
WHERE m.slot_type_service_id = s.slot_type_service_id;

Reporting queries should be guarded with a check against the data dictionary, since the table will not exist in most environments. A defensive pattern is to query ALL_TABLES for AHM_SVC_GROUP_MAP before executing any runtime SQL, ensuring scripts degrade gracefully on 12.1.1 and 12.2.2 instances where the obsolete product has been removed.

Related Objects

The most significant relationship documented is the foreign key from AHM_SVC_GROUP_MAP.SLOT_TYPE_SERVICE_ID to AHM_SLOT_TYPE_SERVICES, making that parent table the primary related object. The following objects are the most relevant in analysis:

• AHM_SLOT_TYPE_SERVICES – parent table referenced by SLOT_TYPE_SERVICE_ID; the principal join target.
• AHM_SVC_GROUP_MAP_PK – the primary key constraint object on SVC_GROUP_MAP_ID.
• AHM_SVC_GROUP_MAP itself appears in ETRM relationship data as both the owning table and the referencing table for the single documented FK, reflecting the legacy definition.
• Additional AHM hosting master tables, such as group definition and service definition tables within the same obsolete product family, are likely siblings, though their exact names are not present in the supplied metadata.

Because no views, APIs, or downstream dependents are documented beyond the single FK, integration analysis should rely on the source DDL and any surviving Hosting Manager documentation rather than on the ETRM extract alone.