Search Results jts_configurations_tl




Overview

JTS_CONFIGURATIONS_TL is a translation (TL) table within the JTS schema, which supports CRM Self Service Administration in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-dependent descriptive text that accompanies configuration records created and maintained through the CRM Self Service Administration module. In Oracle EBS multilingual implementations, this table works in conjunction with its base table (JTS_CONFIGURATIONS_B) to provide translated descriptions for each configuration defined in the system.

The table resides in the JTS schema and carries the status VALID in the documented environment. It contains 10 columns in the ETRM 12.1.1 physical schema. Based on the heuristic Data Vault classification mined from its foreign key structure, this table is identified as standalone, suggesting that it functions independently within the modeled relationship graph and does not participate in a classic hub-link-satellite pattern. This classification reflects its role as a translation satellite that references a parent entity but does not itself act as a central hub or linking entity.

Key Information Stored

The table's structure centers on a composite business key and a set of standard EBS audit columns. The most significant columns include:

  • CONFIGURATION_ID — The foreign key reference to the parent configuration record in the base table. Combined with LANGUAGE, this forms the unique business key.
  • LANGUAGE — The NLS language code identifying the translation. Along with CONFIGURATION_ID, it constitutes the unique index JTS_CONFIGURATIONS_TL_U1.
  • SOURCE_LANG — The source language from which the translation was derived, used by the EBS translation framework (such as the Translation Synchronization or "Translate" concurrent programs).
  • DESCRIPTION — The translated descriptive text for the configuration. This is the primary payload of the TL table.
  • SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS, which enforces data access isolation across operating units or security groupings (relevant in Multi-Org or data security enabled environments).
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO columns that capture audit trail information for insert and update operations.

The unique index JTS_CONFIGURATIONS_TL_U1 on (CONFIGURATION_ID, LANGUAGE) is the documented business-key candidate, distinguishing this from a purely surrogate key. The surrogate identity in Oracle EBS TL patterns is typically ROWID-based or derived through the combination of the parent ID and language.

Common Use Cases and Queries

Typical scenarios include retrieving translated configuration descriptions for a given language, auditing missing translations, and building multilingual reports over CRM Self Service configurations.

To fetch the translated description for a specific configuration in a target language:

  • SELECT t.CONFIGURATION_ID, t.LANGUAGE, t.DESCRIPTION FROM JTS.JTS_CONFIGURATIONS_TL t WHERE t.CONFIGURATION_ID = :id AND t.LANGUAGE = USERENV('LANG');

To identify configurations that lack a translation in a required language (a common NLS gap analysis):

  • SELECT b.CONFIGURATION_ID FROM JTS.JTS_CONFIGURATIONS_B b WHERE NOT EXISTS (SELECT 1 FROM JTS.JTS_CONFIGURATIONS_TL t WHERE t.CONFIGURATION_ID = b.CONFIGURATION_ID AND t.LANGUAGE = 'FR');

For reporting, join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to respect data security, and consider that in 12.2.2 online patching (ADOP) may temporarily maintain multiple editions of the JTS schema. Use the apps synonym or the editioning view rather than hard-coding the physical schema for cross-release compatibility.

Related Objects

The most significant related objects are:

  • JTS_CONFIGURATIONS_B — The base (non-translated) table; join on CONFIGURATION_ID.
  • FND_SECURITY_GROUPS — Referenced through the SECURITY_GROUP_ID foreign key for data security partitioning.
  • JTS_CONFIGURATIONS_TL itself, through its unique index JTS_CONFIGURATIONS_TL_U1 (CONFIGURATION_ID, LANGUAGE), which governs the allowed cardinality of translations per configuration.
  • FND_LANGUAGES — Logically related to the LANGUAGE column, providing the set of installed languages available for translation.
  • FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — Contextual dependencies for the JTS product installation.
  • CRM Self Service Administration concurrent programs (e.g., translation synchronization) that populate and maintain this table.

Because the ETRM metadata marks this object as standalone, no additional foreign keys beyond SECURITY_GROUP_ID are documented; integrators should treat the parent-child link to the base table as the principal dependency.