Search Results accounting_event_type_code

Overview

The APPS.XLA_ACCT_PROG_SEQ_V view is a public reporting view within the Oracle E-Business Suite Subledger Accounting (XLA) module. It is defined against the APPS schema with FND Design Data reference XLA.XLA_ACCT_PROG_SEQ_V and holds a VALID status in release 12.1.1 and 12.2.2. Its principal function is to expose the completion-based sequence numbers that are assigned to subledger journal entries during a run of the accounting program. When the Create Accounting process executes, it generates accounting entries and must subsequently assign document sequence values in accordance with subledger sequencing rules. This view surfaces the association between each accounting entry header, its event context, and the assigned completion sequence identifier, version, and value.

Because it is a public view, Oracle documents it as suitable for custom reporting and integration requirements rather than as an internal-only repository object. Report developers, conversion specialists, and support analysts can query it directly to audit sequence assignment, reconcile subledger journal output, or feed downstream data warehouses without navigating the underlying transactional tables individually.

Underlying Base Objects

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

• XLA_AE_HEADERS — the subledger accounting entry header table, supplying accounting entry identifiers and the ledger, balance type, source, category, and date attributes.
• XLA_EVENTS_GT — a global temporary table populated during accounting program execution that carries the event context, including the accounting event type code.
• XLA_SUBLEDGERS — the subledger definition table, providing application-level metadata that qualifies the originating subledger.

The join across these objects correlates each accounting entry header with its originating event and subledger definition, while the sequence assignment columns are derived from the accounting program's completion sequencing logic. This design means row availability is tied to accounting program execution and, for the events global temporary table portion, to the session in which accounting was run.

Key Columns

• AE_HEADER_ID — Unique identifier of the accounting entry header, the primary link back to XLA_AE_HEADERS.
• LEDGER_ID — Identifier of the ledger for which the entry was created.
• BALANCE_TYPE_CODE — Indicates whether the entry is Actual, Budget, or Encumbrance.
• JE_SOURCE_NAME / JE_CATEGORY_NAME — General Ledger source and category names applied to the transferred journal entry.
• DOC_CATEGORY_CODE — Document sequence category used as part of the subledger journal entry sequencing criteria.
• ACCOUNTING_EVENT_TYPE_CODE — The event type code identifying the business event that generated the accounting entry; this is the column most often targeted by users searching for accounting_event_type_code.
• ACCOUNTING_ENTRY_TYPE_CODE — Classification of the accounting entry.
• GL_DATE / COMPLETION_DATE — The accounting date and the subledger journal entry completion date.
• COMPLETION_ACCT_SEQ_ASSIGN_ID — Identifier of the journal entry completion sequence assignment.
• COMPLETION_ACCT_SEQ_VERSION_ID — Identifier of the subledger journal entry creation sequence version.
• COMPLETION_ACCT_SEQ_VALUE — The actual sequence value assigned to the entry.
• APPLICATION_ID — Internal identifier of the owning application.

Common Use Cases and Queries

Typical usages include auditing document sequence gaps, reconciling completion sequence values against transfer to GL, and filtering entries by event type for a given ledger or accounting period. A representative query follows:

• SELECT ae_header_id, ledger_id, accounting_event_type_code, accounting_entry_type_code, completion_date, completion_acct_seq_value FROM apps.xla_acct_prog_seq_v WHERE ledger_id = :ledger_id AND accounting_event_type_code = :event_type ORDER BY completion_acct_seq_value;

Analysts may also aggregate by doc_category_code to identify duplicate or missing sequence values, or join ae_header_id to XLA_AE_HEADERS and XLA_AE_LINES for line-level drill-down. Because the view depends on execution-time sequencing data, results should be validated against the accounting program run in question.