Search Results csi_mass_edit_entries_tl




Overview
Explore in AI Chat

Overview

The CSI_MASS_EDIT_ENTRIES_TL table is a translation table within the CSI (Install Base) product module of Oracle E-Business Suite. It stores the language-specific, translated content for mass edit transaction entries that are maintained in the corresponding base table, CSI_MASS_EDIT_ENTRIES_B. In the Oracle EBS multilingual architecture, the _TL suffix denotes a table that holds translated columns — typically the NAME and DESCRIPTION attributes — for each supported language. This design allows the same transactional entry to be presented in multiple installed languages without duplicating the non-translatable transactional data.

The object resides in the CSI schema and carries a status of VALID in release 12.2.2. Its Data Vault classification, derived heuristically from the foreign key structure, is standalone. In dimensional modeling terms, a standalone classification suggests the table does not function as a classic hub, link, or satellite carrying independent business keys for a Data Vault backbone; rather, it is best modeled as a dependent translation satellite attached to its base table. Analysts building a Data Vault or star schema should treat CSI_MASS_EDIT_ENTRIES_TL as a descriptive, language-scoped extension of the base entry record rather than an independent entity.

Key Information Stored

The table contains eleven documented columns. The most significant are:

  • ENTRY_ID — The surrogate and foreign reference to the base mass edit entry. Together with LANGUAGE it forms the primary key CSI_MASS_EDIT_ENTRIES_TL_PK.
  • LANGUAGE — The installed language code identifying which translation this row represents. It is part of the composite primary key.
  • SOURCE_LANG — Indicates the source language from which the translation was derived, supporting the standard Oracle MLS (Multi-Language Support) translation workflow.
  • NAME — The translated name of the mass edit entry. It participates in the unique index CSI_MASS_EDIT_ENTRIES_TL_U02 (NAME, LANGUAGE), a business-key candidate.
  • DESCRIPTION — The translated descriptive text of the entry.
  • SECURITY_GROUP_ID — References FND_SECURITY_GROUPS, restricting row visibility based on the security model in use.
  • CREATED_BY, CREATION_DATE — Standard audit columns capturing who created the translation row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Audit columns for the most recent modification, including the login that performed it.

The composite primary key uses the surrogate/business combination of ENTRY_ID and LANGUAGE, while the two unique indexes (U01 on ENTRY_ID and LANGUAGE, U02 on NAME and LANGUAGE) establish business-key candidates that enforce uniqueness of the translated name within a language.

Common Use Cases and Queries

Typical usage centers on multilingual reporting of mass edit transactions and on joining translated text back to the base and operational tables. Common scenarios include:

  • Reporting mass edit entries to users in their session language by filtering on LANGUAGE.
  • Auditing when translated names or descriptions were last changed.
  • Reconciling translation completeness across installed languages.

A representative query joining the translation to the base entry:

SELECT t.entry_id, t.name, t.description
FROM csi.csi_mass_edit_entries_tl t
WHERE t.language = USERENV('LANG')
ORDER BY t.name;

A query detecting missing translations:

SELECT b.entry_id
FROM csi.csi_mass_edit_entries_b b
WHERE NOT EXISTS (SELECT 1 FROM csi.csi_mass_edit_entries_tl t
  WHERE t.entry_id = b.entry_id AND t.language = 'US');

Related Objects

  • CSI_MASS_EDIT_ENTRIES_B — The base translation table; joined on ENTRY_ID to retrieve language-independent data.
  • CSI_MASS_EDIT_ENTRIES_TL_PK — The primary key constraint enforcing uniqueness of ENTRY_ID and LANGUAGE.
  • CSI_MASS_EDIT_ENTRIES_TL_U01 / _U02 — Unique indexes serving as business-key candidates.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for row-level security.
  • FND_LANGUAGES — Provides the installed language definitions resolving the LANGUAGE and SOURCE_LANG values.
  • Standard MLS and concurrent program APIs that populate translated columns through the base table's translation workflow.