Results for “jtf_xml_invocations_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_XML_INVOCATIONS_TL is a translation (TL) table within the JTF – CRM Foundation product of Oracle E-Business Suite, documented in ETRM as a repository for XML Services Events. It stores the language-dependent, translated content associated with XML service invocation records. Its design follows the standard Oracle EBS multi-language pattern, in which a base table holds language-independent attributes and a companion _TL table holds the translatable text columns keyed by both the base entity identifier and a LANGUAGE code. Because this object carries descriptive text attributes that qualify a parent invocation record, the metadata's heuristic Data Vault classification of "satellite-leaning" is a reasonable modeling suggestion: the table behaves as a descriptive satellite attached to the base invocation entity rather than as an independent hub or an association link.

The ETRM metadata records "Not implemented in this database," indicating that in the reference environment where this documentation was mined, the object was not physically present. This is common for CRM Foundation XML services tables, which are created only when the relevant XML service functionality is licensed and configured. The object should therefore be confirmed as deployed in any target instance before being queried directly.

Key Information Stored

The documented structure is deliberately narrow, and the essential columns are the following:

• INV_ID – The invocation identifier. This is the foreign key to JTF_XML_INVOCATIONS_B and forms the component that ties each translated row to its base invocation record. It is also part of the composite primary key.
• LANGUAGE – The language code identifying the locale of the translated content. It is the second component of the composite primary key.
• Translatable text columns – The TL table exists to hold the language-specific descriptive elements of the XML service event (for example, names or descriptions surfaced in the XML services framework). The ETRM excerpt does not enumerate these individually.
• WHO columns – Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) are conventionally present on such tables, though they are not itemized in the documented metadata.

The surrogate primary key is JTF_XML_INVOCATIONS_TL_PK, defined over (INV_ID, LANGUAGE). This is a composite key that combines the foreign-key surrogate (INV_ID) with the language discriminator. The documented metadata does not list any separate unique index; the primary key itself enforces the one-row-per-language-per-invocation business rule. There is no documented unique index offering an alternative business key.

Common Use Cases and Queries

The primary practical use is retrieving the translated descriptive text for a given XML service invocation, joined to the base table for language-independent detail and filtered by the session or reporting language:

• Translation lookup – join JTF_XML_INVOCATIONS_TL to JTF_XML_INVOCATIONS_B on INV_ID and filter LANGUAGE = userenv('LANG') to return the correct locale's text.
• Language completeness reporting – group by LANGUAGE and count rows to identify invocations missing translations in a given locale.
• Base-plus-translation reporting – a two-table join returning base invocation attributes alongside localized text for operational or audit reporting on XML services events.
• Duplicate detection – since the PK guarantees uniqueness of (INV_ID, LANGUAGE), any query returning more than one row per pair indicates data corruption or an incomplete deployment.

A representative pattern is SELECT b.*, tl.* FROM jtf_xml_invocations_b b, jtf_xml_invocations_tl tl WHERE b.inv_id = tl.inv_id AND tl.language = userenv('LANG'). Confirm object existence first, given the "not implemented" note in the metadata.

Related Objects

• JTF_XML_INVOCATIONS_B – The base table; JTF_XML_INVOCATIONS_TL.INV_ID references JTF_XML_INVOCATIONS_B. This is the principal join partner and the only documented foreign key.
• JTF_XML_INVOCATIONS_TL_PK – The composite primary key constraint on (INV_ID, LANGUAGE).
• XML Services framework APIs – The JTF XML service layer that writes and reads invocation events and their translations; the supported access path rather than direct DML.
• FND_LANGUAGES – The repository of installed languages referenced indirectly by the LANGUAGE column for locale validation and reporting.
• JTF_XML_* sibling TL/B pairs – Other CRM Foundation XML services base and translation tables that share the same design convention and are typically queried together in framework reporting.

These objects collectively form the XML services event data model, with JTF_XML_INVOCATIONS_B as the parent entity and JTF_XML_INVOCATIONS_TL as its language-dependent satellite.