Search Results pa_ap_inv_exceptions_sum_v




Overview
Explore in AI Chat

Overview

PA_AP_INV_EXCEPTIONS_SUM_V is an Oracle Applications (APPS) schema view in the Projects (PA) product family. Its documented purpose is to identify the Payables invoices that prevent a Projects period from being closed. The view is registered as VALID in the ETRM repository and is available in both E-Business Suite 12.1.1 and 12.2.2.

The view sits at the boundary between Oracle Payables (AP) and Oracle Projects (PA). When a Projects period close is attempted, Payables invoice distributions that are candidates for project cost collection but have not yet been successfully imported or processed are flagged as exceptions. Each row of PA_AP_INV_EXCEPTIONS_SUM_V represents one such exception line, exposing the invoice, distribution, exception code, and descriptive exception text that explains why the period cannot close. It is therefore used as a diagnostic reporting view rather than a transactional or interface table.

Underlying Base Objects

The documented referenced base objects are AP_CHECKS_ALL, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_INVOICE_LINES_ALL, AP_INVOICE_PAYMENTS_ALL, AP_PAYMENT_HISTORY_ALL, AP_PAYMENT_HIST_DISTS, AP_SELF_ASSESSED_TAX_DIST_ALL, GL_LEDGERS, MTL_SYSTEM_ITEMS, PA_IMPLEMENTATIONS_ALL, PO_DISTRIBUTIONS, PO_DISTRIBUTIONS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_VENDORS, plus the PL/SQL packages PA_EXCEPTION_REASONS_PUB, PA_EXPENDITURES_UTILS, PA_NL_INSTALLED, and PA_UTILS2. All the Payables, Purchasing, Inventory, and General Ledger objects are referenced as synonyms.

AP_INVOICE_DISTRIBUTIONS_ALL is the driving table, supplying PROJECT_ID, TASK_ID, INVOICE_DISTRIBUTION_ID, AMOUNT, BASE_AMOUNT, EXCHANGE_RATE, ACCOUNTING_DATE, PERIOD_NAME, and PA_ADDITION_FLAG. AP_INVOICES_ALL and AP_INVOICE_LINES_ALL supply invoice-level and line-level attributes such as INVOICE_NUM, INVOICE_DATE, VENDOR_ID, and INVOICE_CURRENCY_CODE. The GL_LEDGERS synonym (aliased GLSOB) provides the set of books / ledger currency used to derive accounting currency columns. PA_IMPLEMENTATIONS_ALL (aliased IMP) contributes SAME_PA_GL_PERIOD and SET_OF_BOOKS. PO_DISTRIBUTIONS, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, AP_SELF_ASSESSED_TAX_DIST_ALL, and MTL_SYSTEM_ITEMS are joined to resolve purchasing and tax context. PA_EXCEPTION_REASONS_PUB, PA_UTILS2, and PA_EXPENDITURES_UTILS are invoked within the SELECT list to derive exception text, PA date profiles, period names, and organization names.

Key Columns

Common Use Cases and Queries

The primary use case is troubleshooting a blocked Projects period close. Because the view already resolves the exception reason and corrective action, users can query it directly to produce an actionable exception report without additional lookups to the reason tables.

Typical filter queries include isolating exceptions for a specific project or operating unit:

  • SELECT project_id, task_id, invoice_number, invoice_date, exception_code, exception_reason, corrective_action FROM pa_ap_inv_exceptions_sum_v WHERE project_id = :p_project_id;
  • SELECT invoice_number, vendor_id, denom_amount, gl_period_name, exception_reason FROM pa_ap_inv_exceptions_sum_v WHERE org_id = :p_org_id AND posted_flag IS NULL;
  • SELECT exception_code, COUNT(*) FROM pa_ap_inv_exceptions_sum_v GROUP BY exception_code; — to summarize exception volumes by cause.

The view is commonly embedded in custom period-close dashboards and in OTBI or Discoverer reports that alert project accountants to invoices that must be corrected, released, or transferred before the close can proceed. As with any APPS view, it should be accessed through a reporting responsibility with the appropriate Projects and Payables data grants.