Search Results source_id_int_2

Overview

XLA_POST_ACCTG_EVENTS_V is a Subledger Accounting (XLA) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes accounting event records that are eligible for the post-accounting stage of subledger processing, namely those whose PROCESS_STATUS_CODE equals D (draft or completed, pending further action) or P (processed/posted). The view is registered as VALID in the ETRM metadata and is intended for reporting and integration purposes, allowing developers and analysts to query pending or processed accounting events without directly accessing the underlying Global Temporary Table (GTT).

The view presents a flat, denormalized projection of event header information, the identifiers that tie an event back to its source subledger transaction, and four parallel sets of generic reference columns (numeric, character, and date). This structure supports ad-hoc reporting, diagnostics of stuck or unposted events, and integration with external systems.

Underlying Base Objects

The view is defined solely over XLA_EVENTS_GT, which is documented as a SYNONYM referencing the global temporary table used internally by the Subledger Accounting engine. Because XLA_EVENTS_GT is a GTT, its contents are session-scoped: rows are materialized only during the subledger accounting program run for the current session. Consequently, XLA_POST_ACCTG_EVENTS_V exposes data only within an active processing session and does not persist as a stable repository between runs. The view definition applies a row filter (WHERE PROCESS_STATUS_CODE IN ('D','P')) but performs no joins, aggregation, or column transformation.

Key Columns

• ENTITY_ID, ENTITY_CODE, TRANSACTION_NUMBER — Identify the source subledger entity and its human-readable transaction number, linking the event back to a specific business document.
• SOURCE_ID_INT_1 through SOURCE_ID_INT_4 — Four generic integer identifier slots populated by the source application. In many subledger implementations, SOURCE_ID_INT_1 holds the primary key of the source transaction (for example, an invoice, receipt, or journal line), which is why it is the most frequently searched column for this view.
• SOURCE_ID_CHAR_1 through SOURCE_ID_CHAR_4 — Character equivalents used when the source key is alphanumeric or when supplementary values are needed.
• EVENT_ID, EVENT_CLASS_CODE, EVENT_TYPE_CODE, EVENT_NUMBER, EVENT_DATE — Core accounting event identity: the event's unique ID, its class (for example, AP_INVOICES), its type, the sequential event number, and the accounting event date.
• EVENT_STATUS_CODE, PROCESS_STATUS_CODE — Track lifecycle state. PROCESS_STATUS_CODE determines view membership and indicates whether the event is in a draft/processed (D) or posted (P) state.
• REFERENCE_NUM_1..4, REFERENCE_CHAR_1..4, REFERENCE_DATE_1..4 — Twelve generic reference slots whose semantics are defined by the source subledger, commonly used to carry document numbers, currency codes, or accounting dates for downstream reconciliation.

Common Use Cases and Queries

Typical scenarios include diagnosing events that have not been transferred to the General Ledger, reconciling posted subledger activity to GL balances, and extracting event data for integration. Because the view draws on a GTT, queries must execute within a session where the subledger accounting program has populated XLA_EVENTS_GT.

Locate events by source transaction using the integer source identifier:

SELECT event_id, entity_code, transaction_number, event_date, process_status_code
FROM   apps.xla_post_acctg_events_v
WHERE  source_id_int_1 = :p_source_id_int_1;

List all draft or processed events for a ledger and event class:

SELECT event_number, event_type_code, event_status_code, process_status_code, reference_num_1
FROM   apps.xla_post_acctg_events_v
WHERE  ledger_id = :p_ledger_id
AND    event_class_code = 'AP_INVOICES';

Reconcile by accounting date:

SELECT transaction_number, event_date, event_created_by, reference_date_1
FROM   apps.xla_post_acctg_events_v
WHERE  reference_date_1 BETWEEN :p_from_date AND :p_to_date;