Search Results xla_ledger_options_pk

Overview

XLA_LEDGER_OPTIONS is a configuration table owned by the XLA (Subledger Accounting) schema in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores ledger-level default setup information for a given application, meaning each row defines how a particular application (identified by APPLICATION_ID) applies Subledger Accounting (SLA) processing rules for a specific ledger (identified by LEDGER_ID). This includes operational preferences such as the mode of transfer to General Ledger, accounting reversal behavior, event capture enablement, rounding rules, and merging options. Because these parameters govern accounting outcomes consistently across all transactions processed in the ledger, this table is central to SLA configuration and to reconciling subledger-to-GL behavior.

From a Data Vault modeling perspective, the mined classification for this table is standalone. This suggests it is best modeled as a hub or configuration reference rather than a transactional link or satellite, since it holds setup/master-style data keyed by application and ledger rather than recording events or changing measures over time.

Key Information Stored

The table comprises 14 documented columns. The most operationally significant columns are:

• APPLICATION_ID — Identifies the subledger application (e.g., Payables, Receivables) to which the ledger options apply.
• LEDGER_ID — The ledger for which the default SLA setup is defined.
• TRANSFER_TO_GL_MODE_CODE — Controls whether and how subledger accounting entries are transferred to General Ledger (e.g., automatic, summary, or manual transfer modes).
• ACCT_REVERSAL_OPTION_CODE — Defines the default accounting reversal behavior applied to entries.
• CAPTURE_EVENT_FLAG — Indicates whether subledger accounting events are captured for this application/ledger combination.
• ROUNDING_RULE_CODE — Specifies the default rounding rule applied to generated entries.
• MERGE_ACCT_OPTION_CODE — Governs how accounting lines are merged when creating journal entries.
• EFFECTIVE_PERIOD_NUM — Indicates the effective accounting period associated with the setup.
• ENABLED_FLAG — Denotes whether the option set is currently enabled.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit/Who columns tracking record creation and modification.

The primary key, XLA_LEDGER_OPTIONS_PK, is the composite surrogate key (APPLICATION_ID, LEDGER_ID). A unique index, XLA_LEDGER_OPTIONS_U1, is defined on the same pair (APPLICATION_ID, LEDGER_ID), making that combination the business-key candidate and enforcing one option set per application per ledger.

Common Use Cases and Queries

Typical uses include verifying that event capture is enabled, auditing transfer-to-GL configurations, and confirming reversal and rounding defaults before period close. A simple retrieval query by application and ledger is:

• SELECT * FROM xla.xla_ledger_options WHERE application_id = :app AND ledger_id = :ledger;
• Checking capture status: SELECT ledger_id, capture_event_flag FROM xla.xla_ledger_options WHERE application_id = :app;
• Reviewing transfer configuration across ledgers: SELECT ledger_id, transfer_to_gl_mode_code, rounding_rule_code FROM xla.xla_ledger_options;

These queries support implementation validation, reconciliation reporting, and diagnostics when subledger journals are not being created or transferred as expected.

Related Objects

Because XLA_LEDGER_OPTIONS is the single source of ledger-level defaults, it is referenced across SLA setup and processing:

• XLA_LEDGERS / GL_LEDGERS — Joined on LEDGER_ID to resolve ledger names and attributes.
• XLA_APPLICATIONS / FND_APPLICATION — Joined on APPLICATION_ID for application identification.
• XLA_EVENTS — Event capture behavior governed by CAPTURE_EVENT_FLAG.
• XLA_ACCOUNTING_HEADERS / XLA_AE_HEADERS — Journal generation consistent with rounding/merge options.
• XLA_ACCOUNTING_OPTIONS / XLA_LEDGER_OPTION_ATTRS — Line-level and attribute-level SLA configuration related to these defaults.

Together these objects form the configuration and processing backbone that determines how subledger transactions are accounted for and posted to the General Ledger.