Search Results ahm_hosted_svcs_b

Overview

AHM_HOSTED_SVCS_B is a base (B) table within the Oracle E-Business Suite Hosting Manager module (AHM). It stores the services offered by an Application Service Provider (ASP), capturing the details of the hosted services catalogued under the Hosting Manager product family. The "B" suffix in EBS naming conventions denotes the base table of a translated entity, holding language-independent attribute data, while the corresponding "_TL" table stores the translatable, language-dependent descriptive columns. The ETRM metadata classifies the product module as obsolete, and the implementation status is explicitly recorded as "Not implemented in this database," indicating the table is generally dormant in most 12.1.1 and 12.2.2 environments but remains part of the shipped schema and is available for reference or legacy compatibility.

From a dimensional modeling perspective, the mined Data Vault classification for this object is heuristic "hub-leaning." This suggests it functions as a hub entity: the central, stable repository of unique hosted-service business entities, keyed by a single surrogate identifier, around which descriptive satellites (such as the translatable text) are organized.

Key Information Stored

The table's principal documented column is the surrogate primary key, HOSTED_SVC_ID, which uniquely identifies each hosted service record. The primary key constraint AHM_HOSTED_SVCS_B_PK is defined on this column, making it the authoritative identifier used throughout the AHM schema to reference a service.

• HOSTED_SVC_ID — The system-generated surrogate primary key (AHM_HOSTED_SVCS_B_PK). This is the sole column explicitly documented in the ETRM metadata excerpt and serves as the unique identifier for each hosted service.

Beyond the surrogate key, the metadata does not enumerate additional attribute columns. In typical EBS base-table designs of this pattern, the remaining descriptive fields reside in the companion translation table (AHM_HOSTED_SVCS_TL), whose columns carry the language-specific names and descriptions. Consequently, AHM_HOSTED_SVCS_B should be understood as a thin hub holding identity and language-independent attributes, with the substantive business descriptions drawn from the _TL sibling. No business-key unique index is documented in the provided metadata; the documented uniqueness is confined to the surrogate PK on HOSTED_SVC_ID.

Common Use Cases and Queries

Because the object is marked obsolete and not implemented, primary use cases center on legacy data inspection, schema lineage analysis, and upgrade impact assessment rather than active transaction processing. A typical query joins the base table to its translation child to retrieve the localized service name and description:

SELECT b.hosted_svc_id,
       t.hosted_svc_name,
       t.description
FROM   ahm_hosted_svcs_b b,
       ahm_hosted_svcs_tl t
WHERE  b.hosted_svc_id = t.hosted_svc_id
AND    t.language = USERENV('LANG');

Reporting scenarios include enumerating the catalogue of ASP-offered services for historical or audit purposes and validating referential integrity between base and translation rows. A row-count or orphan-verification script can confirm whether any base record lacks a matching translation entry:

SELECT b.hosted_svc_id
FROM   ahm_hosted_svcs_b b
WHERE  NOT EXISTS
       (SELECT 1 FROM ahm_hosted_svcs_tl t
        WHERE t.hosted_svc_id = b.hosted_svc_id);

These patterns are useful during EBS migrations to 12.2.x, where obsolete Hosting Manager objects are commonly reviewed for retention or archiving decisions.

Related Objects

The documented relationship data identifies the translation table as the primary dependent object, joined through the shared HOSTED_SVC_ID column.

• AHM_HOSTED_SVCS_TL — The translation (language-dependent) table. It references AHM_HOSTED_SVCS_B via the foreign key column HOSTED_SVC_ID (AHM_HOSTED_SVCS_TL.HOSTED_SVC_ID → AHM_HOSTED_SVCS_B). This is the principal child and the object most frequently joined for descriptive reporting.
• AHM_HOSTED_SVCS_B_PK — The primary key constraint on HOSTED_SVC_ID, governing uniqueness on the base table.

Additional Hosting Manager tables, such as hosting service assignments and provisioning configuration objects, may reference HOSTED_SVC_ID in fully implemented environments; however, the ETRM FK metadata documents only the _TL relationship. Any further dependencies should be confirmed against the live data dictionary before being relied upon, given the obsolete status of the module.