Search Results xla_launch_options




Overview
Explore in AI Chat

Overview

The XLA_LAUNCH_OPTIONS table is a Subledger Accounting (XLA) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the default accounting program launch options for a specific combination of application and ledger. Accounting programs in XLA — such as Create Accounting, Transfer Journal Entries to GL, and Post Journal Entries to GL — are typically initiated with a set of runtime parameters (accounting mode, summary reporting, transfer and posting flags). XLA_LAUNCH_OPTIONS persists the defaults that pre-populate these parameters, allowing users to avoid re-entering the same options on every run. For applications that support valuation method accounting, the table maintains separate default option sets for primary and secondary valuation methods.

From a dimensional modeling perspective, the ETRM metadata carries a heuristic Data Vault classification of standalone, meaning the table is not mined as a hub, link, or satellite through foreign key structure. This should be treated as a modeling suggestion only. Conceptually, the natural business key of (APPLICATION_ID, LEDGER_ID) behaves like a hub-like identifier, while the remaining attribute columns (flags, mode codes, limits) would map to satellite-style descriptive attributes in a Data Vault design. The table is owned by the XLA schema and is marked VALID.

Key Information Stored

The table is uniquely identified by the primary key constraint XLA_LAUNCH_OPTIONS_PK over the columns APPLICATION_ID and LEDGER_ID. A unique index, XLA_LAUNCH_OPTIONS_U1, also covers (APPLICATION_ID, LEDGER_ID), which serves as the business-key candidate — there is no separate surrogate system-generated key. Together, these two columns define the scope of each row: one set of launch defaults per application per ledger. The documented schema contains 18 columns; the most significant functional columns are:

The remaining columns are standard audit and concurrency attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Administrators and support analysts query this table to confirm the defaults applied when the Create Accounting or Transfer to GL programs are submitted. A typical retrieval for a single ledger looks like:

  • SELECT application_id, ledger_id, accounting_mode_code, error_limit, processes, processing_unit_size FROM xla.xla_launch_options WHERE ledger_id = :ledger_id;

Because the override flags govern user flexibility, a frequent diagnostic scenario is determining whether a discrepancy between expected and actual run parameters is caused by a disallowed override:

  • SELECT APPLICATION_ID, LEDGER_ID, ACCOUNTING_MODE_OVERRIDE_FLAG, SUMMARY_REPORT_OVERRIDE_FLAG FROM xla.xla_launch_options WHERE SUBMIT_TRANSFER_TO_GL_FLAG = 'Y';

Reporting use cases include auditing default process counts and error limits across ledgers, and identifying applications that have no configured launch options (i.e., rely solely on runtime user input). The table is also useful in upgrade or clone validation exercises, where comparing default options between source and target environments reveals configuration drift.

Related Objects

Although the metadata classifies this table as standalone (no mined foreign keys), it logically references foundational EBS entities and is referenced by downstream configuration. The most significant related objects include:

  • FND_APPLICATION — supplies the application name/description behind APPLICATION_ID.
  • GL_LEDGERS — resolves LEDGER_ID to the ledger name, chart of accounts, and currency.
  • XLA_ACCOUNTING_PROGRAMS (and the XLA accounting program definitions) — the programs whose defaults are stored here.
  • XLA_LAUNCH_OPTIONS itself is queried by the XLA post-accounting and transfer request submission logic.
  • FND_CONCURRENT_REQUESTS — used in tandem to compare stored defaults against the actual submitted request parameters.

Analysts should treat (APPLICATION_ID, LEDGER_ID) as the reliable join key when correlating this table with GL and application-level configuration.