Search Results ahm_subscribed_svcs




Overview
Explore in AI Chat

Overview

The AHM_SUBSCRIBED_SVCS table belongs to the AHM (Hosting Manager) product family within Oracle E-Business Suite. Its documented description identifies it as the "customers online service selection" table, intended to record which online services each customer has elected to receive. In functional terms, it operates as a service-subscription header: the parent entity that groups the individual subscribed service line items held in AHM_SUBSCRIBED_ITEMS.

The ETRM metadata records that this object is not implemented in the reference database, and the AHM product itself is flagged as obsolete. It therefore appears in EBS 12.1.1 and 12.2.2 primarily as a legacy or dormant schema object rather than an actively maintained one. Customers migrating from earlier hosting-oriented releases may still encounter it during upgrades or schema comparisons, but no operational data should be expected in a standard installation.

The Data Vault classification mined heuristically from the foreign-key structure is satellite-leaning. As a modeling suggestion, this implies that AHM_SUBSCRIBED_SVCS behaves as a descriptive attribute carrier attached to a hub of subscribed services, rather than as an independent business hub or an associative link. The classification should be treated as a structural observation only, since the table is not populated in the delivered database.

Key Information Stored

The documented structure is narrow. The principal columns are:

  • SUBSCRIBED_SVC_ID — the surrogate primary key of the table, enforced by constraint AHM_SUB_SVC_PK. It uniquely identifies each customer service subscription record and serves as the parent reference for downstream line items.
  • HOSTED_SVC_ID — a foreign-key column linking the subscription back to the underlying hosted service definition. It represents the business-level service being subscribed to.

The metadata does not document additional descriptive columns such as status, effective dates, or audit fields. Where the ETRM extract is silent, no specific column names should be assumed. The surrogate key SUBSCRIBED_SVC_ID is the only documented unique identifier; no alternate unique index or natural business key is recorded for this object. Practically, HOSTED_SVC_ID functions as the principal business-key candidate, since subscriptions are conceptually keyed by customer and service, but the metadata does not confirm a uniqueness constraint on that column.

Common Use Cases and Queries

Because the table is obsolete and unpopulated, the realistic use cases are diagnostic and analytical rather than transactional. Typical patterns include:

  • Schema auditing during an upgrade from 12.1.1 to 12.2.2, to confirm whether AHM objects were carried forward or dropped.
  • Reverse-engineering legacy hosting data models when integrating third-party or custom hosting extensions.
  • Impact analysis before patching or repurposing the AHM schema namespace.

A representative query joins the subscription header to its line items:

  • SELECT s.subscribed_svc_id, s.hosted_svc_id, COUNT(i.subscribed_svc_id) items FROM ahm_subscribed_svcs s JOIN ahm_subscribed_items i ON i.subscribed_svc_id = s.subscribed_svc_id GROUP BY s.subscribed_svc_id, s.hosted_svc_id;

To verify whether the object exists and is populated in a given environment, a simple existence check is sufficient:

  • SELECT COUNT(*) FROM ahm_subscribed_svcs; — a zero result confirms the "not implemented" note in the metadata.

Related Objects

The FK metadata establishes a parent-child relationship with one dependent table and a reference to a service master entity:

  • AHM_SUBSCRIBED_ITEMS — the most significant dependent object. It references AHM_SUBSCRIBED_SVCS.SUBSCRIBED_SVC_ID via its own SUBSCRIBED_SVC_ID column, forming the header-to-line relationship.
  • AHM_SUBSCRIBED_SVCS.HOSTED_SVC_ID — the outbound foreign key to the hosted service definition, documented as pointing to a target rendered as "%" in the metadata extract. The precise foreign table name is not confirmed and should be validated against the data dictionary.

Given the table's obsolete status, no documented views, PL/SQL APIs, or concurrent programs reference it in the supplied metadata. Any additional dependencies should be confirmed through DBA_DEPENDENCIES and DBA_CONSTRAINTS queries against the specific instance in scope.