Search Results xla_launch_options_u1

Overview

XLA.XLA_LAUNCH_OPTIONS is a Subledger Accounting (XLA) configuration table that stores the default accounting program launch parameters applied per application and ledger. Each row defines how the Create Accounting process, and its downstream transfer and posting steps, should behave for a given APPLICATION_ID and LEDGER_ID combination. The table is owned by the XLA schema, resides in the APPS_TS_TX_DATA tablespace, and is registered in FND Design Data as XLA.XLA_LAUNCH_OPTIONS. Oracle classifies the object as Internal Use Only; supported access is through standard Oracle Applications programs rather than direct DML.

The relationship metadata classifies this object heuristically as a standalone data vault entity. From a modeling perspective, the composite primary key (APPLICATION_ID, LEDGER_ID) means the table is best understood as a configuration or reference satellite keyed on the application-ledger pair, rather than as a true hub or link in a dimensional sense. No FK dependencies are recorded in the provided metadata; the table acts as a self-contained ledger-level settings store.

Key Information Stored

The physical primary key XLA_LAUNCH_OPTIONS_PK is defined on (APPLICATION_ID, LEDGER_ID). A separate unique index, XLA_LAUNCH_OPTIONS_U1, exists on the same column pair in APPS_TS_TX_IDX; it is the business-key candidate and is the index most commonly referenced when users search for the object. The columns of operational interest are:

• APPLICATION_ID — the subledger application (for example Payables, Receivables, Assets) to which the options apply.
• LEDGER_ID — the ledger internal identifier; may be a primary or secondary ledger where the application supports valuation methods.
• ACCOUNTING_MODE_CODE — controls the accounting mode: D for Draft, T for Test, F for Final.
• ACCOUNTING_MODE_OVERRIDE_FLAG — Y/N; permits the user to override the accounting mode at program submission time.
• SUMMARY_REPORT_FLAG — accounting report mode: S for Summary, D for Detail.
• SUMMARY_REPORT_OVERRIDE_FLAG — Y/N; allows override of the summary report option.
• SUBMIT_TRANSFER_TO_GL_FLAG — Y/N; whether transfer to General Ledger is submitted automatically after accounting entries are created.
• SUBMIT_TRANSFER_OVERRIDE_FLAG — Y/N; allows override of the transfer-to-GL submission option.
• SUBMIT_GL_POST_FLAG — Y/N; whether GL posting is submitted automatically.
• SUBMIT_GL_POST_OVERRIDE_FLAG — Y/N; allows override of the GL post option.
• ERROR_LIMIT — the maximum number of errors permitted during the accounting program run.
• PROCESSES and PROCESSING_UNIT_SIZE — concurrency control for parallel accounting program execution.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit trail columns.

Common Use Cases and Queries

The most frequent use case is diagnosing why Create Accounting runs in a particular mode or automatically submits transfer and posting. Administrators query this table to confirm settings before period-end close, and reporting extracts surface ledger-level defaults for audit documentation.

Retrieve the options for a specific application and ledger:

• SELECT * FROM xla_launch_options WHERE application_id = :app_id AND ledger_id = :ledger_id;

List non-default or override-enabled ledgers, useful for close checklists:

• SELECT application_id, ledger_id, accounting_mode_code, submit_transfer_to_gl_flag, submit_gl_post_flag FROM xla_launch_options WHERE submit_transfer_override_flag = 'Y' OR submit_gl_post_override_flag = 'Y';

Confirm that a specific index is present in a cloned or upgraded instance:

• SELECT index_name, uniqueness FROM dba_indexes WHERE table_name = 'XLA_LAUNCH_OPTIONS' AND owner = 'XLA';

Related Objects

Because the provided metadata records no foreign keys, the table is logically referenced by the applications it governs rather than physically dependent on other objects. Significant related objects include:

• XLA_LAUNCH_OPTIONS_PK / XLA_LAUNCH_OPTIONS_U1 — the primary and unique indexes on (APPLICATION_ID, LEDGER_ID).
• FND_APPLICATION — joins on APPLICATION_ID to resolve the application short name and description.
• GL_LEDGERS — joins on LEDGER_ID to resolve ledger name, chart of accounts, and ledger category.
• XLA_ACCOUNTING_PROGRAM — the concurrent program that consumes these launch options at submission time.
• XLA_EVENTS / XLA_AE_HEADERS / XLA_AE_LINES — downstream accounting artifacts created under the mode and limits defined here.

All access should be read-only and performed under the guidance of standard Oracle Applications programs, consistent with the Internal Use Only designation.