Results for “csf_dc_queries_tl”

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

Overview

CSF_DC_QUERIES_TL is a translation (TL) table owned by the CSF schema, which supports Oracle EBS Field Service and the broader Enterprise Technical Reference Model (ETRM) diagnostics infrastructure. In Oracle EBS 12.1.1 and 12.2.2, a "_TL" table stores language-specific (translatable) descriptive attributes — such as NAME and DESCRIPTION — for a corresponding base entity, keyed by language. CSF_DC_QUERIES_TL holds the multilingual query definitions used by the Diagnostic Center / data collection framework, allowing a stored query definition (identified by QUERY_ID) to present localized names and descriptions to users in each installed language.

The metadata records a Data Vault classification of "standalone," which is a modeling suggestion rather than a strict requirement. Because the table carries descriptive text (NAME, DESCRIPTION) rather than pure intersection or transactional data, it functions conceptually as a satellite attached to the QUERY_ID hub. The absence of documented foreign keys reinforces treating QUERY_ID as a logical reference to the base query entity rather than a hard-enforced relationship.

Key Information Stored

CSF_DC_QUERIES_TL contains eleven documented columns. The most significant are:

• QUERY_ID — Surrogate identifier of the parent query definition; the primary linking attribute to the base query.
• LANGUAGE — The language code for the translated row; part of the composite key.
• SOURCE_LANG — The language in which the source text was originally authored, used by the translation framework to derive localized strings.
• NAME — The language-specific display name of the query.
• DESCRIPTION — The language-specific descriptive text explaining the query's purpose.
• ZD_EDITION_NAME — Editioning metadata introduced with the 12.2 Online Patching (ADOP) architecture; supports edition-based redefinition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO (audit) columns tracking who created and last modified each row.

The primary key is CSF_DC_QUERIES_TL_PK (QUERY_ID, LANGUAGE), which uniquely identifies a query's translation for a single language. The unique index CSF_DC_QUERIES_TL_U1 (QUERY_ID, LANGUAGE, ZD_EDITION_NAME) is the documented business-key candidate, extending the primary key with the edition discriminator to accommodate 12.2 editioning.

Common Use Cases and Queries

Typical usage centers on joining the translation table to the base query table and resolving a specific language at runtime. A standard pattern is:

• Localized query lookup: SELECT q.query_id, t.name, t.description FROM csf.csf_dc_queries_tl t WHERE t.query_id = :query_id AND t.language = USERENV('LANG');
• Fallback reporting: use SOURCE_LANG where a translated row is missing for the requested language.
• Multi-language catalog reports: group by QUERY_ID and pivot NAME across LANGUAGE values to compare translations.
• Data quality audit: identify queries lacking a translation for an installed language by comparing against the base table.
• Change tracking: query LAST_UPDATE_DATE and LAST_UPDATED_BY to report recently modified query descriptions for governance.

In 12.2 environments, edition-aware queries should filter on ZD_EDITION_NAME to avoid returning rows across editions.

Related Objects

Although the mined metadata reports CSF_DC_QUERIES_TL as standalone (no enforced foreign keys), functional dependencies follow the translation framework pattern:

• CSF_DC_QUERIES — the base (non-translated) query table, joined on QUERY_ID.
• CSF_DC_QUERIES_TL_PK / CSF_DC_QUERIES_TL_U1 — indexes enforcing uniqueness on (QUERY_ID, LANGUAGE) and the edition-extended business key.
• Other CSF_DC_* tables (e.g., data collection query steps and parameters) sharing the QUERY_ID lineage.
• FND_LANGUAGES — validates the LANGUAGE and SOURCE_LANG codes.
• Standard WHO audit views and localization frameworks that consume TL rows.