Search Results xla_conditions_u2

Overview

XLA.XLA_CONDITIONS is a transactional configuration table within the Oracle E-Business Suite Subledger Accounting (XLA) schema. It stores the condition definitions that drive the Accounting Methods Builder (AMB), the rule-based engine that determines how subledger transactions are transformed into accounting entries. Each row represents a single condition or comparison element used within an accounting rule, describing the left-hand operand, the operator, and the right-hand operand against which journal line generation is evaluated.

This table sits at the heart of the rules engine that processes events from Payables, Receivables, Assets, and other subledgers. Because the conditions govern when and how accounting lines are created, changes to this table directly affect posted accounting for all downstream transactions. Oracle marks the object as Internal Use Only and does not support direct DML outside of standard applications programs; data should be maintained through the AMB setup UI or supported APIs.

Based on the mined foreign-key structure and the absence of strong FK composition into child entities, the heuristic Data Vault classification for this object is standalone. Where a formal model is required, it is best treated as a reference or lookup-style entity rather than a hub, link, or satellite, though the surrogate key and edition column support a satellite-style pattern if history tracking is needed.

Key Information Stored

• CONDITION_ID — the surrogate primary key (XLA_CONDITIONS_PK), an internal sequence number uniquely identifying each condition row.
• APPLICATION_ID — identifies the owning application (e.g., Payables, Receivables) whose transactions the condition applies to.
• ENTITY_CODE / EVENT_CLASS_CODE — the entity and event class that scope the condition to a specific subledger process.
• AMB_CONTEXT_CODE — the Accounting Methods Builder context under which the condition is evaluated.
• ACCOUNTING_LINE_TYPE_CODE / ACCOUNTING_LINE_CODE — the accounting line type and code the condition governs.
• SEGMENT_RULE_DETAIL_ID — foreign key to XLA_SEG_RULE_DETAILS linking the condition to a segment rule detail.
• DESCRIPTION_PRIO_ID — foreign key to XLA_DESC_PRIORITIES; controls the description priority applied when the condition is satisfied.
• USER_SEQUENCE — user-defined ordering for evaluating conditions within a rule.
• VALUE_TYPE_CODE — indicates whether the operand is a source value or a constant.
• SOURCE_APPLICATION_ID / SOURCE_TYPE_CODE / SOURCE_CODE — the left-hand source operand metadata.
• VALUE_SOURCE_APPLICATION_ID / VALUE_SOURCE_TYPE_CODE / VALUE_SOURCE_CODE — the right-hand source operand metadata when compared against a source.
• VALUE_CONSTANT — the literal value used when VALUE_TYPE_CODE indicates a constant comparison.
• BRACKET_LEFT_CODE / BRACKET_RIGHT_CODE — parentheses for grouping boolean expressions.
• LINE_OPERATOR_CODE / LOGICAL_OPERATOR_CODE — comparison and boolean connectors between operands.
• ZD_EDITION_NAME — editioning column supporting Online Patching (EBR) in EBS 12.2.

The unique index XLA_CONDITIONS_U2 acts as the principal business-key candidate, 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. XLA_CONDITIONS_U1 combines CONDITION_ID with ZD_EDITION_NAME. Supporting non-unique indexes (XLA_CONDITIONS_N1 through N4) cover source columns, DESCRIPTION_PRIO_ID, and SEGMENT_RULE_DETAIL_ID.

Common Use Cases and Queries

Typical scenarios include auditing which conditions apply to a given subledger entity, troubleshooting unexpected accounting entries, and migrating accounting setups between environments.

Locating conditions for a specific entity and event class:

• SELECT c.condition_id, c.user_sequence, c.source_code, c.line_operator_code, c.value_source_code, c.value_constant FROM xla_conditions c WHERE c.application_id = 200 AND c.entity_code = 'AP_INVOICES' AND c.event_class_code = 'INVOICE' ORDER BY c.user_sequence;

Joining to segment rule details to see the rule hierarchy:

• SELECT c.condition_id, s.segment_rule_detail_id, d.description_prio_id FROM xla_conditions c JOIN xla_seg_rule_details s ON c.segment_rule_detail_id = s.segment_rule_detail_id LEFT JOIN xla_desc_priorities d ON c.description_prio_id = d.description_prio_id;

Reporting all conditions referencing a particular source across subledgers helps impact analysis before changing a source definition. Because the table is EBR-enabled, queries in 12.2 should filter by ZD_EDITION_NAME where edition isolation is required.

Related Objects

• XLA_SEG_RULE_DETAILS — joined on SEGMENT_RULE_DETAIL_ID; the parent segment rule detail each condition qualifies.
• XLA_DESC_PRIORITIES — joined on DESCRIPTION_PRIO_ID; supplies description priority metadata.
• XLA_ACCOUNTING_RULES — the parent rule definition referencing conditions through rule details.
• XLA_LINE_DEFINITIONS — accounting line definitions that conditions help qualify.
• XLA_EVENT_CLASSES / XLA_ENTITY_TYPES — reference sources for ENTITY_CODE and EVENT_CLASS_CODE.
• XLA_CONDITION_TL (or attribute tables) — translations and additional descriptive attributes tied to CONDITION_ID.
• XLA_ACCOUNTING_PROGRAMS and the Create Accounting concurrent program — consume condition definitions at runtime.

Direct DML against XLA_CONDITIONS is not supported; changes flow through AMB setup forms and the associated XLA setup APIs.