Search Results ahm_slot_type_svc_resp_map

Overview

The AHM_SLOT_TYPE_SVC_RESP_MAP table belongs to the AHM – Hosting Manager module in Oracle E-Business Suite. Per Oracle's ETRM documentation, this module carries an (Obsolete) designation, meaning it was superseded in later functionality and is not actively implemented in current database instances. The table's stated purpose is to store the responsibilities included in a service in context for the hosting master.

Functionally, this table operates as a mapping (association) table that links a "slot type service" to a set of Oracle EBS responsibilities. It allows a hosting master configuration to declare which responsibilities are applicable within a given service context — a common pattern in hosting-oriented provisioning where a service defines a bundle of functional access rights.

Based on the heuristic Data Vault classification mined from its foreign key structure, this table is satellite-leaning. In Data Vault modeling terms, a satellite captures descriptive attributes that change over time and hang off a hub or link. Here, the mapping rows (keyed by a surrogate ID and pointing to AHM_SLOT_TYPE_SERVICES) behave as dependent descriptive records rather than independent business entities. This is a modeling suggestion only and should be validated against actual usage before adopting a Data Vault architecture.

Key Information Stored

The documented metadata identifies a limited set of columns. The most significant are:

• SLOT_TYPE_SVC_RESP_MAP_ID — The surrogate primary key, enforced by the constraint AHM_SLOT_TYPE_SVC_RESP_MAP_PK. This uniquely identifies each mapping row.
• SLOT_TYPE_SERVICE_ID — The foreign key column referencing AHM_SLOT_TYPE_SERVICES. This is the primary business-key candidate linking the mapping to its parent service definition.
• Responsibility column(s) — The table stores the responsibilities themselves, described as "the responsibilities included in service in context for the hosting master." The specific responsibility identifier columns are not enumerated in the available metadata excerpt.

The ETRM metadata does not document a unique index or alternate key beyond the primary key, so SLOT_TYPE_SERVICE_ID combined with the responsibility attribute(s) is the likely natural composite business key. No additional columns are named in the source documentation, so column-level enumeration beyond these would be speculative.

Common Use Cases and Queries

Given the obsolete status, practical use cases center on auditing legacy configurations and migrating hosting assignments. A typical query retrieves all responsibilities mapped to a given service:

• Joining the mapping table to AHM_SLOT_TYPE_SERVICES on SLOT_TYPE_SERVICE_ID to resolve service context for each responsibility.
• Reporting which hosting masters expose which responsibilities, useful during impact analysis before decommissioning.
• Reconciling mapping rows against current responsibility definitions in FND_RESPONSIBILITY to detect orphaned or stale links.

A representative SQL pattern is a two-table join between AHM_SLOT_TYPE_SVC_RESP_MAP and AHM_SLOT_TYPE_SERVICES keyed on SLOT_TYPE_SERVICE_ID, filtered by service name or date range. Because the table is marked "Not implemented in this database," queries should first confirm table existence in the target instance before relying on results.

Related Objects

The following objects are most significant based on the documented foreign key relationship and module context:

• AHM_SLOT_TYPE_SERVICES — The parent table referenced via SLOT_TYPE_SERVICE_ID; the primary dependency for this mapping.
• AHM_SLOT_TYPES — Defines the slot types underlying the services associated with these mappings.
• AHM_SLOT_TYPE_SVC_RESP_MAP_PK — The primary key constraint on SLOT_TYPE_SVC_RESP_MAP_ID.
• FND_RESPONSIBILITY — Standard EBS responsibility repository; resolves the responsibility identifiers stored in this map.
• FND_RESPONSIBILITY_VL — The translatable view used to display responsibility names in host/reporting joins.
• FND_USER_RESP_GROUPS — Relates users to responsibilities and is relevant when validating provisioning outcomes.

Together these objects trace the path from hosting slot configuration to the responsibilities ultimately granted to users.