Results for “cs_cf_flows_tl”

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

Overview

CS_CF_FLOWS_TL is the translation (TL) table for CS_CF_FLOWS_B within the Service (CS) product of Oracle E-Business Suite. It is owned by the CS schema and is documented as VALID in both the 12.1.1 and 12.2.2 releases. Its sole functional purpose is to hold language-specific, translated attributes for the base configuration flow definitions persisted in CS_CF_FLOWS_B. A translation table in EBS is a standard companion to a base table: the base table stores language-independent rows, while the _TL table stores one row per base entity per installed language.

From a Data Vault modeling perspective, the relationship structure mined from this table's foreign keys suggests a link classification. This is a heuristic suggestion rather than a documented design intent: the table is identified by a composite key and joins the base entity (CS_CF_FLOWS_B) to the language dimension (FND_LANGUAGES), which is characteristic of a link construct associating two hubs.

Key Information Stored

The table contains 10 documented columns in the 12.2.2 physical schema. The most important are:

• FLOW_ID — the identifier of the associated configuration flow; it is the foreign key pointing to CS_CF_FLOWS_B. This is the language-independent link back to the base entity.
• FLOW_DISPLAY_NAME — the translated, language-specific display name of the flow. This is the principal translatable payload of the table.
• LANGUAGE — the target language of the translation row; it references FND_LANGUAGES.
• SOURCE_LANG — the source language of the translation, also referencing FND_LANGUAGES; it records the language from which the value was translated.
• ZD_EDITION_NAME — the editioning column used in the EBS 12.2 online patching architecture, which allows multiple editions of a row to coexist.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS "who/when" audit columns maintained on insert and update.

The surrogate primary key is CS_CF_FLOWS_TL_PK, defined over (FLOW_ID, LANGUAGE). Two unique indexes act as business-key candidates: CS_CF_FLOWS_TL_U1 on (FLOW_DISPLAY_NAME, LANGUAGE, ZD_EDITION_NAME) and CS_CF_FLOWS_TL_U2 on (FLOW_ID, LANGUAGE, ZD_EDITION_NAME). These enforce uniqueness of the translated name per language and of each base entity per language and edition.

Common Use Cases and Queries

The most common use is retrieving a translated flow display name for a given flow in the session language. A typical query joins the translation table to the base table and filters by the runtime language, for example:

• Resolving a display name: SELECT tl.flow_display_name FROM cs_cf_flows_tl tl WHERE tl.flow_id = :flow_id AND tl.language = :session_lang;
• Listing all translations of a flow: SELECT tl.language, tl.flow_display_name, tl.source_lang FROM cs_cf_flows_tl tl WHERE tl.flow_id = :flow_id ORDER BY tl.language;
• Detecting missing translations by comparing installed languages in FND_LANGUAGES against rows present here.

Reporting scenarios include multilingual extract files, translation completeness audits, and joined views over CS_CF_FLOWS_B combined with this table to present localized configuration flow names in service-setup screens.

Related Objects

• CS_CF_FLOWS_B — the base table; joined on CS_CF_FLOWS_TL.FLOW_ID = CS_CF_FLOWS_B.FLOW_ID.
• FND_LANGUAGES — referenced twice: via CS_CF_FLOWS_TL.LANGUAGE and CS_CF_FLOWS_TL.SOURCE_LANG, supplying language and source-language metadata.
• CS_CF_FLOWS_TL_PK — the primary key constraint on (FLOW_ID, LANGUAGE).
• Service configuration-flow APIs and concurrent programs that read base flows generally resolve names through this table rather than CS_CF_FLOWS_B directly.