Results for “jtf_state_rules_tl”

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

Overview

JTF_STATE_RULES_TL is the translation table for JTF_STATE_RULES_B, the base table that stores state transition rules within the CRM Foundation (JTF) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. In the Oracle EBS multilanguage architecture, the "_B" suffix denotes the base table holding language-independent data, while the "_TL" suffix denotes the corresponding translation table holding the language-dependent, user-facing text. This table therefore supplies the translated rule names that are displayed to end users, while the structural definition of each rule resides in JTF_STATE_RULES_B.

The object is owned by the JTF schema and holds a VALID status. Its documented physical schema comprises 11 columns. Because translation tables are keyed by both a business entity identifier and a language code, the table is inherently dependent on its base table, and the ETRM heuristic Data Vault classification of "standalone" reflects that the mined foreign-key structure does not tie this table to other CRM transactional entities. From a modeling perspective, this is best treated as a satellite-like descriptive table attached to the JTF_STATE_RULES_B hub, since it carries attribute text (RULE_NAME) keyed by the parent entity identifier plus LANGUAGE.

Key Information Stored

The primary key is JTF_STATE_RULES_TL_PK, defined on the composite of RULE_ID and LANGUAGE. RULE_ID is the surrogate identifier inherited from the base table JTF_STATE_RULES_B, and LANGUAGE is the Oracle language code (for example, US for American English) selecting which translation row applies.

• RULE_ID — surrogate identifier of the parent rule record; the leading column of the composite primary key.
• LANGUAGE — language code qualifying the translated text; the second primary key column.
• RULE_NAME — the translated, user-visible name of the state rule, and the principal business attribute held in this table.
• SOURCE_LANG — the language from which the translation was derived, used during the translation and comparison process.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording creation and last modification of each translation row.
• SECURITY_GROUP_ID — the security group identifier; this table references FND_SECURITY_GROUPS through this column, supporting multiple-organization (multi-org) data isolation.
• ZD_EDITION_NAME — editioning column associated with the Oracle EBS online patching/editioning infrastructure in 12.2.x.

A unique index, JTF_STATE_RULES_TL_U1, is defined on RULE_ID, LANGUAGE, and ZD_EDITION_NAME, which acts as the business-key candidate; it extends the primary key with the editioning column to enforce uniqueness within an edition.

Common Use Cases and Queries

The principal use case is retrieving the display name for a state rule in the session or reporting language. A typical query joins the translation row to the base table on RULE_ID:

• SELECT b.rule_id, t.rule_name FROM jtf_state_rules_b b, jtf_state_rules_tl t WHERE b.rule_id = t.rule_id AND t.language = USERENV('LANG')
• Reporting on which rules have translations available versus missing, by comparing base rows to translation rows per LANGUAGE.
• Extracting all language variants of a single rule: SELECT language, rule_name FROM jtf_state_rules_tl WHERE rule_id = :rule_id.
• Auditing translation maintenance activity using LAST_UPDATED_BY and LAST_UPDATE_DATE.
• Filtering by SECURITY_GROUP_ID for multi-org aware extracts.

Because RULE_NAME is the only meaningful text attribute, most reporting queries project RULE_ID, LANGUAGE, and RULE_NAME, with occasional use of SOURCE_LANG to detect untranslated fallbacks.

Related Objects

• JTF_STATE_RULES_B — the base table; join on RULE_ID. All structural rule data lives here.
• FND_SECURITY_GROUPS — referenced by JTF_STATE_RULES_TL.SECURITY_GROUP_ID; join on SECURITY_GROUP_ID.
• JTF_STATE_RULES_TL_PK — the primary key constraint enforcing RULE_ID plus LANGUAGE uniqueness.
• JTF_STATE_RULES_TL_U1 — the unique index providing the business-key candidate.
• FND_LANGUAGES — the language reference table underpinning the LANGUAGE and SOURCE_LANG columns.
• FND_APPLICATION / JTF product entities — the CRM Foundation components that consume state rules for workflow and status display.

Queries against this object should always restrict on LANGUAGE and account for ZD_EDITION_NAME in 12.2.x environments to avoid duplicate rows across editions.