Search Results pa_xla_bc_pkt_ap_header_v

Overview

The PA_XLA_BC_PKT_AP_HEADER_V view is a Projects (PA) module database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a Subledger Accounting (XLA) header staging view that exposes Accounts Payable (AP) related burden cost packets pending accounting, in a form suitable for the XLA accounting engine. The view is documented as VALID in the ETRM metadata repository and is classified as a Projects product object.

Its principal role is to surface the subset of PA burden-cost events that originate from AP documents and that still carry a status of "Incomplete" (STATUS_CODE = 'I'), forcing them through the XLA event model. The view returns a de-duplicated set of XLA events whose application is Payables (APPLICATION_ID = 200) and whose source document header matches a PA burden-cost packet header. Because it is defined over XLA_EVENTS_GT, a global temporary table populated during accounting program runs, the view is inherently transient and is invoked at runtime rather than queried for historical reporting.

Within the EBS architecture the view bridges the PA burden-cost packet staging tables with the XLA event queue, ensuring Accounts Payable invoice events tied to project burden costs are presented to the Create Accounting process. It is therefore an integration artifact rather than a user-facing report view.

Underlying Base Objects

The documented referenced base objects are two synonyms registered in the APPS schema:

• PA_BC_PACKETS (SYNONYM) — the persistent PA burden-cost packet table holding document-level staging records. Relevant attributes include DOCUMENT_HEADER_ID, BC_EVENT_ID, BURDEN_COST_FLAG, DOCUMENT_TYPE, and STATUS_CODE.
• XLA_EVENTS_GT (SYNONYM) — the XLA subledger events global temporary table populated transiently by the Subledger Accounting program.

The view text joins these on XEV.APPLICATION_ID = 200 (Payables), XEV.SOURCE_ID_INT_1 = PBC.DOCUMENT_HEADER_ID, and XEV.EVENT_ID = PBC.BC_EVENT_ID. It filters on BURDEN_COST_FLAG = 'N', DOCUMENT_TYPE = 'AP', and STATUS_CODE = 'I', and applies SELECT DISTINCT to eliminate duplicate event rows. Because it depends on a global temporary table, the view is only meaningful during an active XLA accounting cycle.

Key Columns

The ETRM documentation lists three exposed column names. These map to the XLA/AP header context:

• EVENT_ID — the XLA event identifier from XLA_EVENTS_GT, uniquely identifying the subledger event to be processed.
• AI_INVOICE_ID — corresponding to XEV.SOURCE_ID_INT_1, the Payables invoice identifier used as the source document reference for the event. This is the column most commonly referenced by developers searching for ai_invoice_id in the context of this view.
• AID_ACCOUNTING_DATE — derived from XEV.EVENT_DATE, the accounting date associated with the XLA event.

The column alias naming reflects the AP invoice (AI) and accounting-date conventions used by the XLA event model.

Common Use Cases and Queries

Typical uses include diagnosing why an AP-linked burden-cost event is not being accounted, validating the source-to-XLA linkage, and confirming the invoice and accounting date carried into the accounting program.

A representative query follows:

• SELECT event_id, ai_invoice_id, aid_accounting_date FROM apps.pa_xla_bc_pkt_ap_header_v;
• Joining ai_invoice_id back to AP_INVOICES_ALL or AP_INVOICE_DISTRIBUTIONS_ALL to reconcile the payables source document.
• Filtering by aid_accounting_date to isolate events for a specific accounting period.

Because the view draws from a global temporary table, queries must be executed within the same session context in which the XLA event data is populated, typically during or immediately following the Create Accounting concurrent program.