Search Results xla_conditions




Overview
Explore in AI Chat

Overview

XLA_CONDITIONS is a Subledger Accounting (XLA) repository table in Oracle E-Business Suite 12.1.1 and 12.2.2 that persists the conditional logic used by the Subledger Accounting engine when deriving accounting lines, header attributes, and segment values. Each row defines a condition that the accounting program evaluates at runtime to determine whether a given accounting line type, account derivation rule detail, or description priority applies to a particular transaction. In this capacity the table forms part of the configuration layer that drives the Create Accounting process, sitting between the application accounting definitions defined by the user and the actual journal entries generated in the GL interface.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. That classification is a modeling suggestion only: XLA_CONDITIONS functions primarily as a descriptive satellite of the accounting definition it qualifies, with foreign key dependencies outward to XLA_SEG_RULE_DETAILS and XLA_DESC_PRIORITIES rather than serving as a pure hub or link. The ZD_EDITION_NAME column indicates the table participates in the editioning framework used for upgrade and multi-edition support in Release 12.2.

Key Information Stored

The table contains 31 documented columns. The most operationally significant are:

Two unique indexes document business-key candidates: XLA_CONDITIONS_U1 (CONDITION_ID, ZD_EDITION_NAME) and XLA_CONDITIONS_U2, the fuller natural key spanning APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, AMB_CONTEXT_CODE, ACCOUNTING_LINE_TYPE_CODE, ACCOUNTING_LINE_CODE, SEGMENT_RULE_DETAIL_ID, DESCRIPTION_PRIO_ID, USER_SEQUENCE, and ZD_EDITION_NAME.

Common Use Cases and Queries

Typical use cases include auditing account derivation rule logic, troubleshooting why a segment value was not derived, migrating accounting definitions between environments, and building reporting on condition hierarchies.

  • Locate all conditions for a segment rule: SELECT CONDITION_ID, USER_SEQUENCE, SOURCE_CODE, LINE_OPERATOR_CODE, VALUE_CONSTANT FROM XLA.XLA_CONDITIONS WHERE SEGMENT_RULE_DETAIL_ID = :p_detail_id ORDER BY USER_SEQUENCE;
  • Retrieve conditions for a given entity and event class: SELECT * FROM XLA.XLA_CONDITIONS WHERE APPLICATION_ID = :app AND ENTITY_CODE = :entity AND EVENT_CLASS_CODE = :eventclass;
  • Join to segment rule details to see which segment a condition feeds: SELECT c.CONDITION_ID, d.SEGMENT_RULE_DETAIL_ID FROM XLA.XLA_CONDITIONS c, XLA.XLA_SEG_RULE_DETAILS d WHERE c.SEGMENT_RULE_DETAIL_ID = d.SEGMENT_RULE_DETAIL_ID;
  • Join to description priorities to review line description logic: SELECT c.CONDITION_ID, p.DESCRIPTION_PRIO_ID FROM XLA.XLA_CONDITIONS c, XLA.XLA_DESC_PRIORITIES p WHERE c.DESCRIPTION_PRIO_ID = p.DESCRIPTION_PRIO_ID;

Related Objects

  • XLA_SEG_RULE_DETAILS — referenced by SEGMENT_RULE_DETAIL_ID; the parent rule detail each condition qualifies.
  • XLA_DESC_PRIORITIES — referenced by DESCRIPTION_PRIO_ID; governs line description selection.
  • XLA_ACCOUNTING_LINES / XLA_AE_LINES — resulting accounting lines whose derivation depends on these conditions.
  • XLA_EVENT_CLASSES / XLA_LINE_DEFINITIONS — define the event class and line context scoping each condition.
  • XLA_ACCOUNTING_DEFINITIONS — the accounting definition layer that consumes the condition logic.
  • XLA_CONDITIONS_TL (where present) — translated descriptions and text attributes.

Because these rows are configuration data (not transaction data), direct DML is not supported; use the Subledger Accounting setup pages or the supported APIs to create and maintain conditions.