Results for “cn_rulesets_all_tl”

50+ results




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

Overview

CN_RULESETS_ALL_TL is the multi-lingual translation table for rulesets used in Oracle Incentive Compensation (CN) to classify revenue. In Oracle E-Business Suite 12.1.1 and 12.2.2, "TL" tables store the translatable descriptive attributes of a base entity, allowing the same business record to be presented in multiple installed languages. Here the translatable attribute is the ruleset NAME; the non-translatable structural and administrative attributes of a ruleset reside in the corresponding base table (CN_RULESETS_ALL_B).

The table is owned by the CN schema and holds one row per ruleset per language per operating unit. Its role is purely descriptive and referential: it does not drive calculation logic itself but provides the human-readable ruleset name displayed in setup forms, concurrent program parameters, and reports. The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning the table behaves as an independent reference/satellite-style structure rather than a classic hub or link. In modeling terms, it is best treated as a descriptive satellite keyed by the ruleset business key plus language, with SECURITY_GROUP_ID acting as a lightweight reference to security definition rather than a true parent link.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are:

  • RULESET_ID — surrogate identifier of the ruleset; part of the composite business key and the logical join back to the base ruleset table.
  • NAME — the translated ruleset name. This is the principal payload of the translation row and the value surfaced in the UI.
  • LANGUAGE — the language code of the translated NAME (for example US, ZHS, D). Part of the unique key.
  • SOURCE_LANG — the language from which the row was originally derived, used by the translation framework to track copy lineage.
  • ORG_ID — the operating unit (multi-org) discriminator; part of the business key.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling row-level security visibility.
  • ZD_EDITION_NAME — editioning column introduced with the 12.2 online patching (Edition-Based Redefinition) architecture; appears in the unique index CN_RULESETS_ALL_TL_U1.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns recording who created and last changed the row and when.

The documented primary key is CN_RULESETS_ALL_TL_UK on (RULESET_ID, ORG_ID, LANGUAGE). A second unique index, CN_RULESETS_ALL_TL_U1, extends that key with ZD_EDITION_NAME, reflecting the 12.2 editioning model. RULESET_ID alone is the surrogate identifier; the combination with ORG_ID and LANGUAGE constitutes the business-key candidate.

Common Use Cases and Queries

Typical usage centers on resolving a ruleset ID to a display name, filtering by language and operating unit, and auditing translation coverage. A representative query joins the translation back to the base table:

  • Resolving names: SELECT t.ruleset_id, t.name, t.language FROM cn.cn_rulesets_all_tl t WHERE t.language = USERENV('LANG') AND t.org_id = :p_org_id;
  • Detecting missing translations: compare distinct RULESET_ID values in the base table against those present in the TL table for a given LANGUAGE.
  • Reporting by business key: constrain on the CN_RULESETS_ALL_TL_UK columns (RULESET_ID, ORG_ID, LANGUAGE) for indexed access.
  • Security-scoped listings: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to honor row-level security when exposing ruleset names to restricted responsibilities.
  • Audit and lineage review: use CREATED_BY, LAST_UPDATED_BY, and SOURCE_LANG to trace when a translated name was introduced or copied from a source language.

Related Objects

The following objects are most significant to this table:

  • CN_RULESETS_ALL_B — the base (non-translatable) ruleset table; joins on RULESET_ID and ORG_ID.
  • FND_SECURITY_GROUPS — referenced by the SECURITY_GROUP_ID foreign key; join on SECURITY_GROUP_ID.
  • CN_RULESETS_ALL_VL — the translated view layered over the base and TL tables, typically the object queried by forms and reports.
  • FND_LANGUAGES — validates the LANGUAGE and SOURCE_LANG codes.
  • CN_RULES / CN_RULESETS rule-definition objects that consume the ruleset for revenue classification.
  • FND_APPLICATION and WHO audit views — supporting metadata for language and audit interpretation.