Search Results hosted_svcs_id




Overview

The AHM_HOSTED_SVCS table belongs to the AHM (Hosting Manager) product family within Oracle E-Business Suite. In the documented metadata, the object is marked as obsolete ("AHM - Hosting Manager(Obsolete)") and is explicitly recorded as "Not implemented in this database." It is described as AHM_CUST_ONLINE_SERVICE_SEL, a table that stores a customer's online service selection. Its stated purposes are to (1) allow termination of an online service by the customer or the ASP administrator, and (2) store service status values such as Subscribed, Activated, and Hosted. Because AHM supported the hosted/ASP delivery model, this table would have functioned as the persistence layer for the subscription lifecycle of services a customer selected through the hosting portal.

From a modeling standpoint, the metadata identifies AHM_HST_SVC_PK as the primary key on HOSTED_SVCS_ID, and the heuristic Data Vault classification mined from the foreign-key structure is "standalone." This suggests treating the object as an independent hub-like structure rather than a link or satellite: it carries its own surrogate identity and does not participate in documented parent-child relationships. That classification should be viewed as a modeling suggestion, not a constraint, given the sparseness of the FK data.

Key Information Stored

The documented metadata exposes a limited but meaningful set of structural facts about the columns and keys:

  • HOSTED_SVCS_ID — The single documented column. It is the surrogate primary key that defines row identity for each hosted service selection record, and it is the access path referenced by the primary key definition AHM_HST_SVC_PK.
  • Primary key AHM_HST_SVC_PK — Defined over HOSTED_SVCS_ID; this is the row-level unique identifier.
  • Unique index AHS_ACOSS_UK — Documented as an additional primary-key-style constraint. This unique index name suggests a business key (a natural or composite uniqueness rule, likely scoped to customer and online service selection) that is distinct from the surrogate HOSTED_SVCS_ID.
  • Status attribute — Per the description, the table stores service status values including Subscribed, Activated, and Hosted. The exact column name is not documented, so status values should be treated as a semantic attribute of the row rather than a named column.
  • Termination semantics — The description ties the table to service termination activity initiated by either the customer or the ASP administrator, implying that termination state or date information is represented in the row.

Because the metadata does not enumerate the remaining columns, any additional attributes (dates, audit columns, customer references) must be confirmed directly against the physical dictionary when the table exists in an environment.

Common Use Cases and Queries

Reporting and remediation scenarios center on identifying which customers selected which online services and what lifecycle state those selections carry. A basic lookup by the searched identifier follows the primary key path:

  • SELECT * FROM AHM_HOSTED_SVCS WHERE HOSTED_SVCS_ID = :hosted_svcs_id;
  • SELECT HOSTED_SVCS_ID FROM AHM_HOSTED_SVCS WHERE ROWNUM <= 100; — inventory of hosted service selections for reconciliation.

Status-driven reporting, such as extracting all services in a Subscribed versus Activated versus Hosted state, supports provisioning audits and hosted-service SLA monitoring. Termination workflows originally used by the customer or ASP administrator map to queries that locate a service selection and then drive a status transition. Because the object is documented as obsolete and not implemented in the reference database, modern 12.1.1 and 12.2.2 instances typically use these queries only for historical migration validation or for confirming that no residual AHM data survives an upgrade.

Related Objects

The documented relationship data classifies this object as standalone, meaning no foreign keys were mined. Consequently, related objects cannot be asserted from FK metadata alone and must be inferred from the hosting model:

  • AHM_HST_SVC_PK — The primary key constraint on HOSTED_SVCS_ID; the defining structural dependency.
  • AHS_ACOSS_UK — The unique index that enforces a business-key rule on the table; it constrains the column set underlying customer online service selection.
  • AHM_CUST_ONLINE_SERVICE_SEL — The descriptive table name referenced in the metadata; functionally the same object as AHM_HOSTED_SVCS.
  • AHM hosting manager application tables — Other AHM tables holding customer, service catalog, and subscription context would join on the customer and service identifiers, though the exact column names are not present in the supplied metadata.
  • ASP administrator configuration objects — The ability of the ASP admin to terminate a service implies linkage to the hosting administration setup, again without documented join columns.

Any join written against this table should be validated against the live data dictionary, because the supplied metadata documents only the surrogate key and does not expose foreign-key columns for downstream relationships.