Search Results csd_rule_conditions_tl




Overview
Explore in AI Chat

Overview

CSD_RULE_CONDITIONS_TL is the translation (TL) table for rule conditions in the Oracle E-Business Suite Depot Repair (CSD) module. In the EBS 12.1.1 and 12.2.2 data model, CSD_RULE_CONDITIONS stores the base definition of conditional logic used by the Depot Repair rules engine, while CSD_RULE_CONDITIONS_TL stores the language-specific, user-facing text associated with each rule condition. This separation allows Oracle EBS to support multiple installed languages (MLS) while maintaining a single, language-independent rule definition.

Each row in the translation table carries a language-specific NAME for a given RULE_CONDITION_ID, together with the standard Oracle Applications "Who" audit columns. The table resides in the CSD schema and holds 9 documented columns in the ETRM 12.2.2 schema. Because the metadata classifies the object as standalone through its FK structure, a Data Vault modeling suggestion would treat CSD_RULE_CONDITIONS_TL as a satellite-like descriptive table attached to the underlying rule-condition business key, rather than as a hub or link. It exists primarily to provide translated descriptive attributes and does not itself carry independent relationships to other entities.

Key Information Stored

The two columns that form the composite primary key, CSD_RULE_CONDITIONS_TL_PK1, are LANGUAGE and RULE_CONDITION_ID. Together they uniquely identify a translated row and prevent duplicate translations for the same condition.

  • RULE_CONDITION_ID — Surrogate/foreign key linking the translation back to the parent rule-condition record in CSD_RULE_CONDITIONS. This is the key join column for most business queries.
  • LANGUAGE — The installed language code (for example, US for American English) identifying which translation this row represents.
  • NAME — The translated, displayable name/description of the rule condition. This is the primary business-facing attribute.
  • SOURCE_LANG — The language of the source row from which this translation was derived; used by MLS to determine whether the row requires retranslation.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording who created the row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login context of that change.

The business-key candidate, where unique indexes are documented, is the (LANGUAGE, RULE_CONDITION_ID) combination enforced by the primary key. Together these columns let applications retrieve the correct translated name for any rule condition.

Common Use Cases and Queries

Typical usage involves resolving a rule condition's translated name for display in Depot Repair setup forms, reports, and inquiry screens. A common reporting pattern joins the translation table with its base table and restricts to the session language.

  • Translating a rule condition for a report: select NAME from CSD_RULE_CONDITIONS_TL where RULE_CONDITION_ID = :id and LANGUAGE = USERENV('LANG').
  • Joining base and translation: SELECT c.RULE_CONDITION_ID, t.NAME FROM CSD_RULE_CONDITIONS c, CSD_RULE_CONDITIONS_TL t WHERE c.RULE_CONDITION_ID = t.RULE_CONDITION_ID AND t.LANGUAGE = 'US'.
  • Auditing translations: identifying rows where SOURCE_LANG differs from the current language to flag stale translations.
  • Migration/conversion projects that extract condition names by language for data warehousing or documentation.

Because the table is MLS-managed, direct DML is generally discouraged; changes should be made through the application or the MLS translation APIs to keep SOURCE_LANG and audit columns consistent.

Related Objects

  • CSD_RULE_CONDITIONS — Base (non-translated) parent table; joined on RULE_CONDITION_ID. It holds the language-independent rule-condition definition.
  • CSD_RULE_CONDITIONS_TL — Self-referencing language rows for the same condition, distinguished only by LANGUAGE.
  • Related Depot Repair rules-engine tables such as rule headers and rule actions, which reference conditions keyed by RULE_CONDITION_ID.
  • MLS translation/inquiry APIs and concurrent programs used to maintain translated names.

Because the metadata classifies this object as standalone with no external FK dependencies, its principal relationship is the parent condition table; other references flow transitively through RULE_CONDITION_ID.