Search Results xla_ledger_options_u1

Overview

XLA.XLA_LEDGER_OPTIONS is a configuration-level table within the Oracle E-Business Suite Subledger Accounting (XLA) schema. It stores the accounting options that govern how a given ledger (identified by LEDGER_ID) behaves with respect to subledger accounting processing and the subsequent transfer of journal entries to the General Ledger. Each row represents the accounting options defined for a specific application and ledger combination, making this the authoritative source for ledger-level subledger behavior at runtime.

The object is owned by the XLA schema and resides in the APPS_TS_TX_DATA tablespace, with its unique and non-unique indexes placed in APPS_TS_TX_IDX. The ETRM documentation classifies this object under a heuristic Data Vault modeling suggestion as standalone, indicating that it does not participate in a classic hub-link-satellite dependency chain in the mined FK structure, but instead functions as an independent configuration table keyed by APPLICATION_ID and LEDGER_ID. In practice, this object may be viewed as a satellite-style configuration store keyed on the ledger business key, though the metadata classifies it as standalone.

The primary key is XLA_LEDGER_OPTIONS_PK, defined on (APPLICATION_ID, LEDGER_ID). A unique index, XLA_LEDGER_OPTIONS_U1, covers the same two columns and serves as the business-key candidate matching the primary key. A non-unique index, XLA_LEDGER_OPTIONS_N1, exists on (LEDGER_ID, CAPTURE_EVENT_FLAG) to support filtered lookups by ledger and event-capture status.

Key Information Stored

The table contains fourteen documented columns. The most operationally significant columns are described below.

• APPLICATION_ID (NUMBER(15), mandatory) — part of the composite primary key; identifies the owning application.
• LEDGER_ID (NUMBER(15), mandatory) — part of the composite primary key; the ledger internal identifier.
• TRANSFER_TO_GL_MODE_CODE — indicates the summary mode for the transfer to the GL program; valid values are P (summarize by period), A (summarize by accounting date), and D (no summarization).
• ACCT_REVERSAL_OPTION_CODE (VARCHAR2(30)) — controls whether accounting reversals reverse the sides (SIDE) or reverse the amount signs (SIGN).
• CAPTURE_EVENT_FLAG — indicates whether accounting events may be created for the ledger: Y allows event creation, N suppresses it. This column is indexed via XLA_LEDGER_OPTIONS_N1.
• ENABLED_FLAG — standard EBS enabled/disabled indicator for the option row.
• ROUNDING_RULE_CODE — specifies the rounding rule applied when generating accounting entries.
• MERGE_ACCT_OPTION_CODE — controls account merging behavior for subledger journal lines.
• EFFECTIVE_PERIOD_NUM — the effective accounting period number associated with the options.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO columns recording row creation and last update audit information, with user references resolving to FND_USER.USER_ID.

Common Use Cases and Queries

This table is typically queried to determine how subledger journals will be summarized on transfer to GL, whether events are captured for a ledger, and how reversals are handled. A common reporting pattern joins the table to ledger and application lookup views to produce a readable accounting-options report.

• Retrieving options for a specific ledger: SELECT * FROM xla.xla_ledger_options WHERE ledger_id = :ledger_id;
• Identifying ledgers that suppress event capture: SELECT ledger_id, application_id FROM xla.xla_ledger_options WHERE capture_event_flag = 'N';
• Auditing the transfer-to-GL summary mode across ledgers by joining to GL_LEDGERS on LEDGER_ID.
• Reviewing recent changes to accounting options using LAST_UPDATE_DATE filters for compliance and change-management reporting.

Because the ETRM documentation marks this object as Oracle Internal Use Only, direct DML should be avoided; queries for reporting are the primary supported access path.

Related Objects

The most significant related objects, based on documented join columns and typical XLA usage, include:

• GL_LEDGERS — joined on LEDGER_ID to resolve the ledger name and chart of accounts.
• XLA_LEDGER_OPTIONS_U1 — the unique index enforcing the (APPLICATION_ID, LEDGER_ID) business key.
• XLA_LEDGER_OPTIONS_PK — the primary key constraint on the same columns.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY for WHO audit resolution.
• XLA_EVENTS — governed at runtime by CAPTURE_EVENT_FLAG; events are created only when the flag is Y.
• XLA_SUBLEDGER_ACCOUNTING_OPTIONS — companion configuration for subledger accounting method assignment.
• GL_JE_BATCHES and GL_JE_HEADERS — downstream targets of the transfer-to-GL process influenced by TRANSFER_TO_GL_MODE_CODE.
• XLA_ACCOUNTING_PROGRAM and the Create Accounting concurrent program — consume these options when generating and transferring entries.