Search Results xla_acct_prog_seq_v




Overview
Explore in AI Chat

Overview

XLA_ACCT_PROG_SEQ_V is an APPS-owned view in the Oracle E-Business Suite Subledger Accounting (XLA) product. Its documented purpose is to assign completion-based sequence numbers to the journal entries generated during a run of an accounting program. In the Subledger Accounting architecture, the Create Accounting program generates accounting entries in XLA_AE_HEADERS and, when the "completion-based sequencing" option is enabled, assigns a sequential number to each completed journal entry. This view exposes the header-level attributes required to drive or report that assignment, joining the accounting headers to the set of events processed during the current run and to the subledger definition. Because it is a view rather than a table, it presents a normalized, run-scoped projection of accounting header data without persisting rows, making it suitable for both internal processing and reporting/integration queries that need the completion sequence context.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms:

  • XLA_AE_HEADERS (ALIAS AEH) — the primary source of journal entry header information, supplying the accounting header identifier, ledger, balance type, journal category, event type, accounting date, completion date, and the completion accounting sequence assignment, version, and value columns.
  • XLA_EVENTS_GT (ALIAS XEG) — a global temporary table holding the events being processed during the current accounting run; it scopes the view to the events of the active program execution and joins to headers on APPLICATION_ID and EVENT_ID.
  • XLA_SUBLEDGERS (ALIAS XSL) — the subledger definition, joined on APPLICATION_ID to supply the journal entry source name (JE_SOURCE_NAME).

The join conditions require AEH.APPLICATION_ID = XEG.APPLICATION_ID, AEH.EVENT_ID = XEG.EVENT_ID, and XSL.APPLICATION_ID = XEG.APPLICATION_ID. The view also filters on NVL(AEH.ZERO_AMOUNT_FLAG, 'N') = 'N', excluding zero-amount headers from sequence consideration. Because XLA_EVENTS_GT is a global temporary table, the view returns data only for the session and run in which events have been populated.

Key Columns

Common Use Cases and Queries

Typical uses include verifying completion sequence assignment for a run, auditing which entries received which sequence values, and integrating sequence data into downstream reporting. The view is run-scoped: meaningful results require the accounting program session to have populated XLA_EVENTS_GT.

Example: retrieve completion sequence values for a ledger.

  • SELECT ae_header_id, ledger_id, je_source_name, je_category_name, completion_acct_seq_value FROM xla_acct_prog_seq_v WHERE ledger_id = :p_ledger_id ORDER BY completion_acct_seq_value;

Example: confirm sequence assignment coverage by subledger application.

  • SELECT application_id, COUNT(*) entries, MIN(completion_acct_seq_value) min_seq, MAX(completion_acct_seq_value) max_seq FROM xla_acct_prog_seq_v GROUP BY application_id;

Example: list completed entries with accounting and completion dates.

  • SELECT ae_header_id, accounting_date, completed_date, completion_acct_seq_assign_id FROM xla_acct_prog_seq_v WHERE completed_date IS NOT NULL ORDER BY completed_date;

Because zero-amount headers are excluded and the event set is limited to the active run, queries should not be treated as a complete historical archive of all accounting entries; for historical analysis, the base XLA_AE_HEADERS table remains the authoritative source.