Search Results xla_accounting_errors




Overview
Explore in AI Chat

Overview

The XLA_ACCOUNTING_ERRORS table is a Subledger Accounting (XLA) repository that stores errors encountered during execution of the Accounting Program — the concurrent process responsible for generating subledger journal entries from source transactions. When the Create Accounting process fails to process a specific event, accounting batch, or event entity, the diagnostic information is written to this table rather than surfacing only in the log file, giving implementers a persistent, queryable record of failure conditions.

Under the Data Vault classification heuristic mined from its foreign key structure, XLA_ACCOUNTING_ERRORS resolves as standalone, meaning the model does not exhibit the hub, link, or satellite topology typical of core transaction tables. The table functions more as a diagnostic log anchored by its own primary key than as a participant in a dimensional network. It is owned by the XLA schema and is present and VALID in both EBS 12.1.1 and 12.2.2, where it exposes 20 documented columns.

Key Information Stored

The table's identity is established by ACCOUNTING_ERROR_ID, which serves as the PRIMARY KEY via the XLA_ACCOUNTING_ERRORS_PK constraint. A unique index, XLA_ACCOUNTING_ERRORS_U1, is also defined on ACCOUNTING_ERROR_ID, confirming it as the sole documented business-key candidate. Although the surrogate key is the technical anchor, the table is best understood as a many-to-one child of the underlying accounting event.

Common Use Cases and Queries

The principal practical application is diagnosing Create Accounting failures without parsing raw log output. A common pattern joins the error table to the ledger to surface recent failures:

  • SELECT ae.*, gl.name FROM xla_accounting_errors ae, gl_ledgers gl WHERE ae.ledger_id = gl.ledger_id AND ae.creation_date > SYSDATE - 1;
  • SELECT accounting_error_id, event_id, error_source_code, message_number FROM xla_accounting_errors WHERE accounting_batch_id = :batch_id;
  • SELECT COUNT(*), error_source_code FROM xla_accounting_errors GROUP BY error_source_code;

Reporting scenarios include building an exception dashboard for period-end close, tracking error recurrence by source application, and reconciling failed events against the source subledger. The table should not be purged during investigation, as records are the audit trail for failed accounting runs.

Related Objects

  • GL_LEDGERS — joined on XLA_ACCOUNTING_ERRORS.LEDGER_ID; the documented foreign key relationship.
  • XLA_EVENTS — source of EVENT_ID; identifies the transaction that failed.
  • XLA_AE_HEADERS / XLA_AE_LINES — referenced via AE_HEADER_ID and AE_LINE_NUM.
  • XLA_ACCOUNTING_PROGRAMS — defines the accounting program whose execution produced the error.
  • FND_CONCURRENT_REQUESTS — correlates REQUEST_ID to the concurrent request.
  • XLA_ERRORS and the Create Accounting concurrent programs — APIs that populate this table.