Search Results csi_mass_edit_entries_tl_u01




Overview
Explore in AI Chat

Overview

CSI.CSI_MASS_EDIT_ENTRIES_TL is the translation (language) table for Mass Edit Entries within the Oracle E-Business Suite Customer Intelligence (CSI) product family. It stores the language-dependent descriptive attributes of mass edit transactions — specifically the user-facing NAME and DESCRIPTION — keyed by ENTRY_ID and LANGUAGE. The corresponding base table, CSI_MASS_EDIT_ENTRIES_B, holds the language-independent columns, while this _TL table carries the translatable text. Every translated row is additionally tagged with a SOURCE_LANG to identify the language from which the value originated, enabling the standard Oracle EBS multi-language (MLS) pattern.

In Data Vault modeling terms, this object is best classified heuristically as a satellite. Its grain is the mass edit entry (the hub business key) combined with the language code, and it carries descriptive, time-stamped attributes (NAME, DESCRIPTION) plus standard WHO audit columns. No foreign keys to subordinate tables are documented, giving this object a standalone dependency classification within the mined FK structure.

Key Information Stored

  • ENTRY_ID — Numeric identifier of the mass edit transaction. Part of the composite primary key CSI_MASS_EDIT_ENTRIES_TL_PK (ENTRY_ID, LANGUAGE) and the leading column of unique index CSI_MASS_EDIT_ENTRIES_TL_U01.
  • LANGUAGE — Language code of the translated row. The second component of the PK and of both unique indexes.
  • NAME — The translatable display name of the mass edit entry (VARCHAR2(50)). Together with LANGUAGE it forms business-key candidate CSI_MASS_EDIT_ENTRIES_TL_U02.
  • SOURCE_LANG — Language code from which the translation was derived; supports MLS translation workflows.
  • DESCRIPTION — Free-text description (VARCHAR2(2000)) used, per the metadata, for JTF Notes creation for all instances in the batch.
  • SECURITY_GROUP_ID — Security group identifier; documented FK to FND_SECURITY_GROUPS, enforcing multi-tenant row-level access.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing insert and update provenance.

The surrogate/primary key is the composite (ENTRY_ID, LANGUAGE). The business-key candidates surfaced by unique indexes are U01 (ENTRY_ID, LANGUAGE) and U02 (NAME, LANGUAGE), meaning a name must be unique within a given language.

Common Use Cases and Queries

Typical usage resolves the translatable name and description of a mass edit batch for display in the user's session language, or audits which languages a given entry has been translated into. A representative join to the base table on ENTRY_ID follows:

  • Retrieve all translations for an entry: SELECT entry_id, language, name, description FROM csi.csi_mass_edit_entries_tl WHERE entry_id = :p_entry_id;
  • Session-language lookup: filter WHERE language = userenv('LANG'), falling back to SOURCE_LANG when no translation exists.
  • Missing-translation report: outer-join the _B and _TL tables on ENTRY_ID and flag rows where _TL.LANGUAGE is null.
  • Security-scoped listing: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict rows to the caller's security group.

Related Objects

  • CSI.CSI_MASS_EDIT_ENTRIES_B — Base language-independent table; join on ENTRY_ID.
  • APPS.CSI_MASS_EDIT_ENTRIES_TL — The APPS synonym/view exposing this table to application code.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for row-level security.
  • JTF Notes objects — DESCRIPTION is populated to drive JTF Notes creation for batch instances.
  • CSI Mass Edit concurrent programs and PL/SQL APIs that insert/update entries and their translations by ENTRY_ID.