Results for “rule_description”

50+ results




Overview
Explore in AI Chat

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

Overview

JTF_BRM_RULES_TL is the translation (language-dependent) table for business rules monitored by the Business Rule Monitor component of Oracle CRM Foundation (JTF). In Oracle E-Business Suite 12.1.1 and 12.2.2, business rules are defined once in the base table JTF_BRM_RULES_B and their user-facing text is stored per language in this _TL table, following the standard Oracle Applications MLS (Multi-Language Support) pattern. Each row pairs a rule identifier with a language code and carries the translated rule name and description.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is modeled as a link. It is not a standalone hub; it exists purely to join a rule in JTF_BRM_RULES_B to a specific language, and therefore materially depends on the base table for its identity. Modelers should treat the (RULE_ID, LANGUAGE) pair as the linking key rather than as an independent business entity.

Key Information Stored

The table is owned by the JTF schema and comprises 13 documented columns. The most significant are:

  • RULE_ID — Surrogate key inherited from the base table; identifies the business rule whose text is being translated.
  • LANGUAGE — The NLS language code for the stored text.
  • SOURCE_LANG — The language in which the rule text was originally authored, used for MLS translation tracking.
  • RULE_NAME — The translated display name of the rule.
  • RULE_DESCRIPTION — The translated descriptive text explaining the rule's purpose.
  • APPLICATION_ID — The application owning the rule, supporting product-scoped queries.
  • SECURITY_GROUP_ID — Security grouping reference; foreign key to FND_SECURITY_GROUPS, used for access partitioning.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard audit columns capturing who last changed the translated row and when.
  • CREATION_DATE / CREATED_BY — Row creation audit.
  • ZD_EDITION_NAME — Editioning column supporting Online Patching (Edition-Based Redefinition) in 12.2.2.

The primary key is JTF_BRM_RULES_TL_PK on (RULE_ID, LANGUAGE). A unique index, JTF_BRM_RULES_TL_U1 on (RULE_ID, LANGUAGE, ZD_EDITION_NAME), acts as the documented business-key candidate. Because rule text is language-sensitive, no translated column alone uniquely identifies a row.

Common Use Cases and Queries

Typical usage centers on join queries that resolve rule definitions into human-readable text in the session or reporting language. A standard pattern joins this table to the base table on RULE_ID:

  • Rule listings by language: SELECT b.RULE_ID, t.RULE_NAME, t.RULE_DESCRIPTION FROM JTF_BRM_RULES_B b, JTF_BRM_RULES_TL t WHERE b.RULE_ID = t.RULE_ID AND t.LANGUAGE = USERENV('LANG').
  • Missing-translation reporting: identify rules present in the base table with no row for a given LANGUAGE, supporting MLS completeness audits.
  • Rule maintenance screens: concurrent-program and CRM Administrator UI lookups retrieve RULE_NAME/RULE_DESCRIPTION through this table.
  • Translation impact analysis: filter on SOURCE_LANG and LAST_UPDATE_DATE to find rules whose default-language text changed after translation.

Reports should always constrain by LANGUAGE or via USERENV('LANG') to avoid returning duplicate rows across languages.

Related Objects

  • JTF_BRM_RULES_B — The base table; joined on RULE_ID, supplying language-independent rule attributes.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for access control partitioning.
  • FND_APPLICATION — Related via APPLICATION_ID to resolve the owning application.
  • Standard MLS views and DML APIs over JTF_BRM_RULES_TL and JTF_BRM_RULES_B, used by the Business Rule Monitor setup screens.
  • FND_LANGUAGES — Supports validation and reporting of LANGUAGE values.

Together these objects form the JTF Business Rule Monitor's configuration layer, enabling multi-language rule definition and evaluation.