Search Results jtf_r_rulesets_vl




Overview
Explore in AI Chat

Overview

The JTF_R_RULESETS_VL view is a language-specific (MLS) reporting view owned by the APPS schema within the JTF – CRM Foundation product of Oracle E-Business Suite. It exposes a "RuleSet" definition — the logical grouping of business rules used by CRM Foundation components such as Territory Manager, resource assignment, and lead/opportunity qualification — in the current session language of the querying user. In ETRM 12.1.1 and 12.2.2, the object is documented as a VALID view with the description "RuleSet language specific view."

Its principal role is to present translatable attributes of a ruleset (name and description) translated according to USERENV('LANG'), while retaining the single source-of-truth identifier RULESET_ID from the base table. This makes the view suitable for reporting, concurrent programs, and integration extracts that must display ruleset text in the runtime language without embedding translation joins in each query. Because it is an APPS-owned database view (not a form or API), it is consumed through SQL and BI Publisher, not through a maintenance UI.

Underlying Base Objects

ETRM documents the view as being defined over referred base objects:

  • JTF_R_RULESETS_B (SYNONYM) — the base table holding language-independent ruleset data and the RULESET_ID primary key.
  • JTF_R_RULESETS_TL (SYNONYM) — the translation table holding per-language name and description for each RULESET_ID.

The view joins them with an outer join condition on JRST.RULESET_ID(+) = JRSB.RULESET_ID and JRST.LANGUAGE(+) = USERENV('LANG'). The outer join ensures that a row is still returned even if no translation exists for the current language. It is the conventional _VL pattern: _B for base columns, _TL for translated columns, and _VL as the user-facing projection.

Key Columns

The view exposes the following columns:

  • RULESET_ID — Surrogate primary key identifying the ruleset; the primary join key to ruleset children and detail tables.
  • LANGUAGE — Language code of the translated _TL row (e.g., US, FR, DE).
  • NAME — Translated ruleset name; the primary human-readable label.
  • DESCRIPTION — Translated free-text description of the ruleset's purpose.
  • SOURCE_LANG — The language of the original (source) entry, used by MLS maintenance logic.
  • OBJECT_VERSION_NUMBER — Optimistic locking/versioning column used by the underlying tables.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit Who columns inherited from the base table.

Common Use Cases and Queries

Typical scenarios include listing rulesets for the current user's language, listing all rulesets for a reporting extract, and joining ruleset text to assignment or rule detail data. A basic lookup:

  • SELECT ruleset_id, name, description FROM jtf_r_rulesets_vl WHERE UPPER(name) LIKE '%TERRITORY%';
  • To filter by translated name while allowing for missing translations, use an outer join from JTF_R_RULESETS_B to this view.
  • For multi-language extracts, query JTF_R_RULESETS_TL directly, since _VL returns only the session language.

Because the view is read-only and depends on USERENV('LANG'), results vary with the session locale; this behaviour should be considered in reports run by multilingual users or batch jobs with fixed language settings.