Search Results css_def_priorities_tl

Overview

CSS_DEF_PRIORITIES_TL is the translatable child table of the Oracle E-Business Suite Support (CSS) module, which is itself flagged as obsolete in the ETRM repository. The table stores language-specific (translated) textual attributes for defect priority definitions used by the Support application. Each row represents a single priority definition rendered in one of the installed languages in the EBS instance, allowing the same logical priority to be displayed in multiple locales.

In Oracle EBS Release 12.1.1 and 12.2.2, translatable (_TL) tables follow a standardized pattern: a base table holds language-independent attributes keyed by a surrogate identifier, while the corresponding _TL table carries the user-facing name, description, and other linguistic content keyed by the surrogate ID plus LANGUAGE. The ETRM metadata documents the primary key as CSS_DEF_PRIORITIES_TL_PK on the columns (PRIORITY_ID, LANGUAGE), and classifies the object as standalone under the heuristic Data Vault analysis. From a data-modeling perspective, this suggests treating the table as a standalone satellite-like structure rather than a hub or link: it carries descriptive, translation-dependent attributes and dependencies rather than representing a business key in its own right.

It is important to note that the ETRM implementation data states "Not implemented in this database." In any deployment where the Support product is not installed (or where this object has been removed as part of the obsolescence of CSS), the table will not exist, and any code referencing it will raise an ORA-00942. Analysts should confirm existence in ALL_TABLES before writing dependent SQL.

Key Information Stored

The documented metadata exposes only a narrow set of columns, but they define the functional identity of the table:

• PRIORITY_ID — Surrogate numeric identifier that links the translated row back to the base (language-independent) priority definition. It is the first component of the composite primary key and represents the business-key candidate used in joins.
• LANGUAGE — The language code (for example, US for American English) in which the translated attributes are stored. It is the second component of CSS_DEF_PRIORITIES_TL_PK.

Although ETRM's excerpt lists only the two key columns, the standard translatable-table pattern in EBS implies that additional linguistic columns such as a translated name and a translated description accompany the key. Where present, the base table typically also stores a SOURCE_LANG column indicating the language of the original seed data, and the _TL row with LANGUAGE = SOURCE_LANG serves as the canonical version. Consumers should query the data dictionary to confirm the exact column list in their specific instance, since ETRM explicitly declines to enumerate all columns.

Common Use Cases and Queries

Translation tables are primarily used by the application's multilingual presentation layer and by reporting that must render priority labels in the user's session language. A typical lookup pattern joins the base priority table to the _TL child restricted to the current language, with a fallback to the source language if no translation exists:

• Resolving a priority label for a defect or bug record: select the translated name from CSS_DEF_PRIORITIES_TL where PRIORITY_ID = :p_id and LANGUAGE = userenv('LANG').
• Detecting missing translations for a specific locale by comparing the set of PRIORITY_ID values present in the base table against those present in the _TL table for that language.
• Listing all available language variants for a given priority, useful when auditing translation completeness or building language-selection reports.
• Populating lookup/extract feeds for data warehouses, where priority labels are denormalized into fact tables for defect-resolution reporting.

Because the object is documented as standalone and not implemented in the reference database, production queries should be guarded and should rely on the composite key (PRIORITY_ID, LANGUAGE) to guarantee uniqueness.

Related Objects

The ETRM relationship data classifies this table as standalone, meaning no foreign keys were mined from its FK structure in the reference database. Logical relationships nevertheless exist through convention:

• CSS_DEF_PRIORITIES_B (or equivalent base table) — joined on PRIORITY_ID; supplies language-independent priority attributes.
• CSS_DEF_PRIORITIES_VL — the standard EBS view layer that unions the base and translated tables, joined on PRIORITY_ID and LANGUAGE, and is the recommended interface for the application.
• FND_LANGUAGES — provided by the Application Object Library; referenced via LANGUAGE to obtain language names, ISO codes, and installation status.
• CSS_DEF_LOOKUPS / CSS_DEF_PRIORITY_LEVELS (or similarly named CSS lookup entities) — consume PRIORITY_ID as a lookup value in defect classification.
• Defect and bug fact tables in the Support module — resolve priority labels through PRIORITY_ID for reporting and display.

Developers extending or migrating away from the obsolete CSS module should treat CSS_DEF_PRIORITIES_TL as a legacy translation object, prefer the _VL view for reads, and validate its presence before use in 12.1.1 or 12.2.2 environments.