Search Results css_def_phases_tl

Overview

CSS_DEF_PHASES_TL is a translatable (language-specific) table within the Oracle E-Business Suite CSS – Support module, which is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2. The table stores the translated, presentation-layer text for phase definitions used by CSS support-related configuration. As a "_TL" companion table in the Oracle EBS multi-language architecture, it holds one row per phase per installed or enabled language, allowing the same underlying phase record to be rendered in each supported locale without duplicating the base definition itself.

The ETRM metadata explicitly identifies the primary key as CSS_DEF_PHASES_TL_PK, defined over the columns PHASE_ID and LANGUAGE. The heuristic Data Vault classification supplied in the metadata is standalone, meaning the object participates in no documented foreign-key relationships to other tables. From a Data Vault modeling perspective, this would suggest treating CSS_DEF_PHASES_TL as a satellite-like structure keyed by a parent phase identifier plus a language discriminator; however, because the metadata classifies it as standalone, no hub or link association is documented. The metadata further states the table is "Not implemented in this database," indicating the object is a definition artifact rather than an actively deployed table in the referenced environment.

Key Information Stored

Only a narrow set of columns is documented for this object. The primary-key columns constitute the core of the structure:

• PHASE_ID — Surrogate identifier of the phase to which the translated text belongs. It is the first component of CSS_DEF_PHASES_TL_PK and links the translation back to its base phase record in the non-translated definition table.
• LANGUAGE — The language code for the translated row. It is the second component of CSS_DEF_PHASES_TL_PK, ensuring uniqueness of each phase-language combination and enabling locale-specific retrieval.

In the standard EBS _TL pattern, additional columns such as a source-language flag, translated name or description, and a "last updated by" audit field would normally be present. The documented metadata for CSS_DEF_PHASES_TL does not enumerate these, so they should be confirmed against the deployed dictionary if the object is re-implemented. The surrogate primary key is the (PHASE_ID, LANGUAGE) pair; no separate unique-index business keys are documented in the provided metadata.

Common Use Cases and Queries

Typical usage centers on presenting phase names and descriptions in the user's session language. A representative query pattern joins the translation table to its base definition and filters on the current language:

• Language-specific lookup: SELECT phase_id, language FROM css_def_phases_tl WHERE language = :p_lang;
• Join to base phase definitions using the shared PHASE_ID to obtain translated labels.
• Data-cleansing and audit scripts that detect phases missing a translation for an enabled language.
• Reporting extracts that must render phase text in multiple locales, iterating over the distinct LANGUAGE values.

Because the object is obsolete and marked "Not implemented in this database," such queries are primarily relevant for historical analysis, upgrade impact assessment, or dictionary reconciliation rather than live transactional processing.

Related Objects

The metadata documents no foreign-key relationships, so the following are the most plausible dependencies based on the standard EBS _TL pattern and the PHASE_ID join key rather than on formally documented constraints:

• CSS_DEF_PHASES_B — The base (non-translated) phase definition table, joined on PHASE_ID.
• The untranslated phase definition view or synonym that consumes both the base and _TL rows.
• Language registry tables such as FND_LANGUAGES, providing the valid LANGUAGE values.
• CSS support module configuration and setup forms that display phase text.
• Concurrent programs or APIs that populate phase translations at installation or upgrade.

Consumers should verify each relationship in the target environment, since CSS (Support) is obsolete and may be absent entirely from 12.1.1 or 12.2.2 deployments.