Search Results xla_seg_rules_tl_u2

Overview

XLA.XLA_SEG_RULES_TL is the translation (TL) table for segment rules defined within the Oracle E-Business Suite Subledger Accounting (SLA) framework. Segment rules, configured through the Accounting Methods Builder (AMB), determine how account segments such as balancing, cost center, or natural account segments are derived when subledger transactions are converted into accounting entries. The underlying non-translated table, XLA_SEG_RULES_B, stores the base-language definition of each rule, while XLA_SEG_RULES_TL carries the language-specific name and description required for multilingual deployments.

From a Data Vault modeling perspective, the supplied relationship metadata classifies this object as standalone, meaning no foreign key relationships are mined from its structure. In heuristic terms, XLA_SEG_RULES_TL most closely resembles a satellite attached to the segment rule business key, where APPLICATION_ID, SEGMENT_RULE_TYPE_CODE, SEGMENT_RULE_CODE, and LANGUAGE form the natural identifier and the NAME and DESCRIPTION columns hold the descriptive, language-dependent attributes. This classification should be treated as a modeling suggestion rather than a documented constraint.

Key Information Stored

The table is keyed by the documented primary key XLA_SEG_RULES_TL_PK over (APPLICATION_ID, SEGMENT_RULE_TYPE_CODE, SEGMENT_RULE_CODE, LANGUAGE). Two unique indexes act as business-key candidates: XLA_SEG_RULES_TL_U1 enforces uniqueness across APPLICATION_ID, AMB_CONTEXT_CODE, SEGMENT_RULE_TYPE_CODE, SEGMENT_RULE_CODE, LANGUAGE, and ZD_EDITION_NAME, while XLA_SEG_RULES_TL_U2 enforces uniqueness across APPLICATION_ID, AMB_CONTEXT_CODE, SEGMENT_RULE_TYPE_CODE, NAME, LANGUAGE, and ZD_EDITION_NAME.

• APPLICATION_ID – identifies the owning application, typically the subledger application such as Payables or Receivables, that consumes the segment rule.
• AMB_CONTEXT_CODE – the Accounting Methods Builder context, scoping the rule to a specific accounting method configuration.
• SEGMENT_RULE_TYPE_CODE – categorizes the type of segment rule being defined.
• SEGMENT_RULE_CODE – the internal code uniquely identifying the segment rule within the context.
• LANGUAGE – the standard language code for this translated row.
• NAME – the translatable segment rule name, constrained by the U2 index.
• DESCRIPTION – the translatable description of the segment rule, limited to 240 characters.
• SOURCE_LANG – the language from which this translation was derived.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard who columns providing auditability of insert and update activity.
• ZD_EDITION_NAME – the editioning column supporting EBS online patching, appearing in both unique indexes.

Common Use Cases and Queries

Reporting on segment rules typically requires joining the translated table to XLA_SEG_RULES_B on the primary key to retrieve base definitions alongside language-specific text. A common pattern filters by language and context:

• Retrieve rule names and descriptions for a specific language and AMB context for documentation or configuration review.
• Audit rules created or modified within a date range using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Identify duplicate or conflicting rule names by querying XLA_SEG_RULES_TL_U2 columns, useful when diagnosing SLA account derivation failures.
• Support migration and upgrade validation by comparing rule catalogs across instances for a given APPLICATION_ID.
• Feed downstream reporting extracts that must present segment rule text in the user's language rather than the base language.

A representative query selects APPLICATION_ID, AMB_CONTEXT_CODE, SEGMENT_RULE_TYPE_CODE, SEGMENT_RULE_CODE, LANGUAGE, NAME, and DESCRIPTION, filtering on LANGUAGE and AMB_CONTEXT_CODE, exactly as documented in the ETRM query text.

Related Objects

The most significant related objects are the base table XLA_SEG_RULES_B, joined on (APPLICATION_ID, SEGMENT_RULE_TYPE_CODE, SEGMENT_RULE_CODE), and the language and application reference tables FND_LANGUAGES and FND_APPLICATION, joined on LANGUAGE and APPLICATION_ID respectively. The SLA account derivation and AMB configuration entities, including XLA_AMB_CONTEXTS_TL and the segment rule assignment structures, provide context for AMB_CONTEXT_CODE. The who columns reference FND_USER via CREATED_BY and LAST_UPDATED_BY, and FND_LOGINS via LAST_UPDATE_LOGIN.