Search Results aid_accounting_date




Overview
Explore in AI Chat

Overview

APPS.PA_XLA_BC_PKT_AP_HEADER_V is a database view owned by the APPS schema within Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. It is classified in the ETRM repository as an internal view (View Type: Internal) and carries the explicit Oracle warning that it is for Oracle Internal Use Only and is not supported for direct customer access except through standard Oracle Applications programs. The view participates in the Subledger Accounting (XLA) and Project Accounting (PA) boundary-packet processing infrastructure, specifically the component that assembles and validates Payables (AP) header level information before accounting events are generated for project-related transactions. Its name segments reflect this role: "XLA" for Subledger Accounting, "BC" for boundary/accounting component, "PKT" for packet, and "AP_HEADER" for the Payables invoice header grain. The view is designed to be consumed by internal concurrent programs and validation engines rather than exposed as an end-user reporting object, and its FND Design Data reference is PA.PA_XLA_BC_PKT_AP_HEADER_V.

Underlying Base Objects

Per the documented dependency metadata, PA_XLA_BC_PKT_AP_HEADER_V references two database objects, both accessed through APPS schema synonyms:

  • PA_BC_PACKETS — the Project Accounting boundary packet structure that stores the payload of data captured for a business event, including the identifiers that link a packet to its originating event and transaction sources.
  • XLA_EVENTS_GT — a Subledger Accounting global temporary table that the accounting engine populates at runtime with the set of events being processed in the current session. Joining to this global temporary table scopes the view to the events actively being accounted, rather than the full historical event population.

The ETRM metadata records that APPS.PA_XLA_BC_PKT_AP_HEADER_V is not referenced by any other database object, confirming that it is a top-level consumer component with no downstream database-level dependents. It therefore functions as a terminal access point in the packet validation chain: data flows into it from the packet and event structures, and out to calling application code.

Key Columns

The view exposes a deliberately narrow projection of three columns, each documented with a NUMBER(15) or DATE datatype:

  • EVENT_ID (NUMBER(15)) — the Subledger Accounting event identifier. This is the primary correlation key tying the row back to the XLA_EVENTS_GT population and to the accounting event being processed.
  • AI_INVOICE_ID (NUMBER(15)) — the Accounts Payable invoice identifier. This is the key column matched by users searching on "ai_invoice_id," and it links the accounting event to the Payables invoice header originated in the AP module.
  • AID_ACCOUNTING_DATE (DATE) — the accounting date associated with the transaction or event, used in period determination and accounting date validation.

The combination of event identifier and AP invoice identifier makes the view a bridging structure between the Payables invoice domain and the Project Accounting accounting-event domain.

Common Use Cases and Queries

Because the view is internal and unsupported for direct access, its published query text is provided primarily for diagnostic and research purposes, for example when an accounting event for a project-related AP invoice must be traced back to its source. The documented query is:

  • SELECT EVENT_ID, AI_INVOICE_ID, AID_ACCOUNTING_DATE FROM APPS.PA_XLA_BC_PKT_AP_HEADER_V;

A typical targeted diagnostic filters by invoice, for example SELECT EVENT_ID, AI_INVOICE_ID, AID_ACCOUNTING_DATE FROM APPS.PA_XLA_BC_PKT_AP_HEADER_V WHERE AI_INVOICE_ID = :invoice_id;, which is the form implied by the user search term. Such queries are generally executed to confirm that a packet was constructed for a given invoice and to inspect the accounting date being carried forward. Any such access should be performed with Oracle Support guidance, since the object's contents are populated only within the context of the accounting engine session and are not guaranteed outside standard processing.