Search Results ahm_hosted_svcs_tl

Overview

AHM_HOSTED_SVCS_TL is the translation (language) table associated with the base table AHM_HOSTED_SVCS_B in the Oracle E-Business Suite Hosting Manager module. Its documented purpose is to hold the language-specific, translated attribute values — principally the user-facing name and description — for each hosted service record defined in the base table. In the standard Oracle EBS multilingual architecture, a "_TL" table exists wherever a business entity carries translatable descriptive text, so that the same underlying transactional or setup row can be presented in multiple installed languages. The base table AHM_HOSTED_SVCS_B stores language-independent attributes and the primary key, while AHM_HOSTED_SVCS_TL stores the per-language text keyed by that same identifier plus a LANGUAGE and SOURCE_LANG qualifier.

The product designation in the metadata is AHM - Hosting Manager (Obsolete), and the implementation note states that the object is not implemented in this database. Consequently, in Oracle EBS 12.1.1 and 12.2.2 environments where the Hosting Manager module is not licensed or has been removed, AHM_HOSTED_SVCS_TL will not appear in the data dictionary, and any query referencing it will fail with an ORA-00942 error. The heuristic Data Vault classification derived from the foreign-key structure is satellite-leaning. In Data Vault modeling terms this is best treated as a descriptive satellite attached to the hosted-service hub/entity, because it holds context-dependent, language-scoped descriptive attributes (name and description) rather than acting as a hub or a many-to-many link.

Key Information Stored

The metadata documents the cardinal columns as follows. HOSTED_SVC_ID is the join key that carries the surrogate/business identifier into the base table; it is the column through which the translation row is associated with its base record. LANGUAGE and SOURCE_LANG are the standard Oracle language qualifiers: LANGUAGE identifies the language of the translated text in that row, while SOURCE_LANG records the language in which the text was originally entered. The translated descriptive attributes — the hosted service NAME and DESCRIPTION — are the payload of this table, though their exact physical column names are not enumerated in the supplied metadata. The row is uniquely identified by the combination of HOSTED_SVC_ID and LANGUAGE (the surrogate primary key is effectively that composite), while HOSTED_SVC_ID in isolation behaves as the foreign key to AHM_HOSTED_SVCS_B. Where a unique index is documented it constrains the (HOSTED_SVC_ID, LANGUAGE) pair; the business-key candidate remains HOSTED_SVC_ID.

Common Use Cases and Queries

Because this is a translation table, the dominant use case is a language-joined lookup that presents the hosted service in the session's preferred language. A typical pattern joins the base and translation tables on the shared identifier and constrains LANGUAGE to the user's environment:

• Lookup in a single language: SELECT t.name, t.description FROM ahm_hosted_svcs_tl t WHERE t.hosted_svc_id = :id AND t.language = USERENV('LANG')
• Base-to-translation join: SELECT b.*, t.name 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')
• Multilingual completeness audit: compare the count of translation rows per HOSTED_SVC_ID against the number of installed languages to find untranslated services.
• Reporting and extract programs that must emit localized labels for hosted service setup data.

All such queries are conditional on the module being present; where AHM is obsolete or not implemented, these statements are non-executable and must be guarded or removed from custom code.

Related Objects

The primary and, per the supplied metadata, only documented relationship is the foreign key from AHM_HOSTED_SVCS_TL.HOSTED_SVC_ID to AHM_HOSTED_SVCS_B.HOSTED_SVC_ID. That base table is the master entity for hosted services and is the object most tightly coupled to this translation table. In broader EBS terms, custom concurrent programs, reports, and BI Publisher templates that reference hosted service names will depend jointly on AHM_HOSTED_SVCS_B and AHM_HOSTED_SVCS_TL, while any dependent "_TL" lookups follow the same LANGUAGE-driven join convention. Analysts working in 12.1.1 or 12.2.2 should verify the module's installation status via the ETRM before relying on any of these objects, since the metadata explicitly records AHM_HOSTED_SVCS_TL as not implemented in the reference database.