Search Results jtf_xml_inv_services_tl

Overview

JTF_XML_INV_SERVICES_TL is a translation (TL) table within the JTF – CRM Foundation product of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. Its stated purpose is to store invocations associated with XML-based inventory services exposed through the CRM Foundation layer. In a multi-language enabled EBS implementation, the "_TL" suffix designates a table whose rows carry a LANGUAGE column, allowing the same base entity to be represented in more than one installed language. The base (non-translated) attributes of each invocation service are held separately in JTF_XML_INV_SERVICES_B, to which this table is linked by a foreign key on INV_SERVICE_ID.

The ETRM data vault classification for this object is satellite-leaning, derived heuristically from its foreign key structure. This should be read as a modeling suggestion rather than an architectural directive: the table behaves like a satellite, holding descriptive, language-dependent attributes that hang off the business key maintained in the base table, rather than acting as a hub or a link between independent entities. In practical EBS terms, it is an auxiliary child table whose rows describe the translatable text of an invocation service definition.

The documented implementation note indicates this object is "Not implemented in this database" in the source environment from which the ETRM metadata was extracted. Consultants should therefore confirm actual dictionary presence in the target instance before relying on it, as the table may exist only where the corresponding CRM Foundation components or language installations are configured.

Key Information Stored

The metadata documents a compact structure centered on the translation relationship. The principal columns are:

• INV_SERVICE_ID — Identifier of the invocation service. This is the business-key component that ties each translation row back to its owning record in the base table.
• LANGUAGE — The language in which the translated content is held, following standard EBS language conventions.

Additional descriptive columns typically associated with an EBS "_TL" table — such as name, description, source language, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) — are populated as part of the translated text. However, these do not appear in the documented metadata and should be verified against the target data dictionary.

The surrogate primary key is defined by constraint JTF_XML_INV_SERVICES_TL_PK, which spans the composite of INV_SERVICE_ID and LANGUAGE. Because the ID component is itself the foreign key reference to the base table, the pair (INV_SERVICE_ID, LANGUAGE) functions as both the primary key and the effective business-key candidate: no additional unique index is documented. This design enforces exactly one translation row per service per language.

Common Use Cases and Queries

Because this is a translation table, the dominant access pattern is a two-way join between the base and translated tables, restricted to a single language. A representative pattern for retrieving localized service text is:

SELECT b.inv_service_id,
       t.language,
       t.name,
       t.description
FROM   jtf_xml_inv_services_b b,
       jtf_xml_inv_services_tl t
WHERE  b.inv_service_id = t.inv_service_id
AND    t.language = USERENV('LANG');

Operational queries commonly include auditing the set of available languages for a given invocation service, identifying base records that lack translation rows in a required language, and comparing source-language against translated text during multilingual rollout or upgrade verification. Reporting use cases are largely diagnostic and configuration-oriented: confirming that CRM Foundation XML service definitions are fully localized before users in a non-base language access them, and documenting which services exist for a given territory's language set.

Related Objects

The relationship data identifies the following dependencies and related structures:

• JTF_XML_INV_SERVICES_B — The base table holding non-translated invocation service attributes. It is the parent of this table via the foreign key JTF_XML_INV_SERVICES_TL.INV_SERVICE_ID → JTF_XML_INV_SERVICES_B, and is the primary join partner in all queries.
• JTF_XML_INV_SERVICES_TL_PK — The primary key constraint on (INV_SERVICE_ID, LANGUAGE) that governs uniqueness and drives index access plans.

Because the documentation records only a single foreign key, no other tables, views, or PL/SQL APIs are formally documented as referencing this object. Any wider set of dependents should be confirmed directly from the database catalog in the target EBS instance.