Results for “cn_rules_all_tl”

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

Overview

CN_RULES_ALL_TL is a multi-lingual (TL) translation table in the CN (Incentive Compensation) product schema of Oracle E-Business Suite. It stores the translated rule names for revenue classification, functioning as an input to the revenue classification generator within the Incentive Compensation module. Revenue classification rules define how revenue is categorized for compensation purposes, and this table ensures that rule names can be presented in multiple languages to support global deployments.

In Oracle EBS, TL tables follow a standard pattern: a base table (typically CN_RULES_ALL_B) holds language-independent attributes, while the corresponding _TL table holds translatable columns such as NAME and SOURCE_LANG keyed by LANGUAGE. The _TL table is populated by the translation (MLS) infrastructure and is joined to the base table to resolve a display name for a given session language.

Based on the heuristic Data Vault classification mined from the foreign-key structure, this table is modeled as a standalone object rather than a hub, link, or satellite. This is a modeling suggestion only, reflecting the limited FK relationships documented for the object.

Key Information Stored

The table contains 13 documented columns. The most significant for querying and joins are:

• RULE_ID — Identifier of the revenue classification rule; part of the composite primary key and the join key back to the base rules definition.
• RULESET_ID — Identifier of the ruleset to which the rule belongs; also part of the composite primary key, scoping rules within the incentive plan structure.
• ORG_ID — Operating unit / organization identifier; participates in the primary key and enforces multi-org data segregation.
• LANGUAGE — The language code of the translated row; the fourth component of the primary key.
• NAME — The translated rule name presented to users in the given language.
• SOURCE_LANG — The source language from which the translation was derived, used by the MLS translation framework.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling row-level security access.
• ZD_EDITION_NAME — Editioning column used in the 12.2 online patching (Edition-Based Redefinition) architecture; appears in the unique index CN_RULES_ALL_TL_U1.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN / CREATION_DATE / CREATED_BY — Standard EBS audit columns tracking who created and last modified each translation row.

The documented primary key is CN_RULES_ALL_TL_UK on (RULE_ID, RULESET_ID, ORG_ID, LANGUAGE). The unique index CN_RULES_ALL_TL_U1 extends this with ZD_EDITION_NAME, making it the business-key candidate that supports editioned lookups. There is no separate single-column surrogate key; the identity of a row is the composite business key.

Common Use Cases and Queries

Typical usage involves retrieving the translated rule name alongside the rule definition, usually joined to the base table:

• Resolving a rule name in session language: join CN_RULES_ALL_B (or the base rules table) to CN_RULES_ALL_TL on RULE_ID, RULESET_ID, and ORG_ID, filtering LANGUAGE = USERENV('LANG').
• Multi-lingual reporting: select NAME across multiple LANGUAGE values to produce localized incentive compensation rule documentation.
• Translation completeness audits: identify RULE_ID/RULESET_ID combinations present in the base table with no matching _TL row for a required language.
• Security filtering: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict visible translations to the user's security group.

A representative pattern: SELECT tl.NAME FROM CN_RULES_ALL_TL tl WHERE tl.RULE_ID = :p_rule_id AND tl.RULESET_ID = :p_ruleset_id AND tl.ORG_ID = :p_org_id AND tl.LANGUAGE = USERENV('LANG');

Related Objects

• CN_RULES_ALL_B — The base (non-translated) rules table; joined on RULE_ID, RULESET_ID, and ORG_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID (documented foreign key); supplies security group metadata.
• Revenue Classification Generator — The CN process consuming rule names as input.
• Ruleset definition objects — Tables holding RULESET_ID definitions, joined to scope rules within a plan.
• FND_LANGUAGES — Provides valid LANGUAGE and SOURCE_LANG values for MLS resolution.
• CN_RULES_ALL_TL_UK / CN_RULES_ALL_TL_U1 — Primary key and unique indexes enforcing translation uniqueness.