Search Results ai_invoice_currency_code




Overview
Explore in AI Chat

Overview

AP_PA_HEADER_REF_V is a Payables (AP) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a denormalized, header-level projection that joins invoice header data from AP_INVOICES_ALL to supplier and supplier site information and to the Trading Community Architecture (TCA) party model (HZ_PARTIES and HZ_PARTY_SITES). Its purpose is to expose a single flattened row per Payables invoice header, enriched with vendor, supplier site, party, and party site attributes that would otherwise require multiple joins.

The view is commonly consumed by Oracle Projects and related subledgers (the "PA" prefix in the name suggests Payables-to-Projects integration flows) as well as by custom reports, interfaces, and data extracts that need invoice reference information without traversing the full AP schema. It is a read-only object and carries no incremental logic; each execution reflects the current state of the underlying tables.

Underlying Base Objects

The view is defined over five documented base objects in the APPS schema, all referenced as synonyms in the ETRM metadata for 12.2.2:

The joins are inner joins driven from AP_INVOICES_ALL to AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL on VENDOR_ID/VENDOR_SITE_ID. The TCA lookups for party and party site names are implemented as scalar subqueries rather than joins, so an invoice header is only excluded if no matching supplier or supplier site row exists.

Key Columns

Common Use Cases and Queries

Typical uses include invoice reference extracts for Projects costing, vendor/party reconciliation reports, and integration payloads that require both AP supplier naming and TCA party naming. Because the view is header-level and excludes invoice lines and distributions, it is suitable for lightweight lookups rather than for amount-level reporting.

A representative query filtering by invoice date is:

  • SELECT ai_invoice_id, inv_transaction_number, ai_invoice_date, pov_vendor_name, pos_vendor_site_code, ai_party_name FROM apps.ap_pa_header_ref_v WHERE ai_invoice_date >= :p_from_date AND ai_invoice_date < :p_to_date + 1 ORDER BY ai_invoice_date, inv_transaction_number;
  • SELECT inv_transaction_number, ai_invoice_date, pov_vendor_name FROM apps.ap_pa_header_ref_v WHERE ai_party_id = :p_party_id;

Predicates should reference the exposed column names (for example, AI_INVOICE_DATE) rather than the underlying AP_INVOICES_ALL columns, and date range filtering should be sargable to allow effective use of indexes on the base invoice date column. As with all APPS views, querying requires the appropriate Payables and TCA read privileges, and any extract used for reconciliation should account for cancelled invoices via AI_CANCELLED_DATE.