Search Results pa_ap_inv_exceptions_det_v




Overview
Explore in AI Chat

Overview

The PA_AP_INV_EXCEPTIONS_DET_V view is a Projects (PA) module reporting object that exposes the detailed list of Oracle Payables invoices which prevent a Projects accounting period from being closed. It complements the summary-level view, PA_AP_INV_EXCEPTIONS_SUM_V, by joining the summarized exception rows to descriptive master data such as project, task, and vendor attributes, producing a fully attributed, presentation-ready result set. This view is central to the period-closing workflow in Oracle Projects: before an accounting period can be closed, all outstanding Payables invoice exceptions must be identified and resolved, and this view is the principal mechanism through which those exceptions are surfaced to end users and to the exception reports that support the close process.

Underlying Base Objects

The view is defined over the summarized exception view PA_AP_INV_EXCEPTIONS_SUM_V, which supplies the core exception rows, joined to PA_PROJECTS_ALL, PA_TASKS, and PO_VENDORS to retrieve project number, task number, vendor number, and vendor name. A cross join to PA_IMPLEMENTATIONS_ALL provides the SET_OF_BOOKS_ID context. Supporting packages referenced by the definition include PA_EXCEPTION_REASONS_PUB, PA_EXPENDITURES_UTILS, PA_NL_INSTALLED, and PA_UTILS2, which drive exception reason derivation and installation-dependent logic. All objects reside in the APPS schema, with PA_PROJECTS_ALL, PA_TASKS, and PO_VENDORS referenced as synonyms or views.

Key Columns

The view exposes identifiers and descriptive attributes across four functional groups. Project and task data include PROJECT_ID, PROJECT_NUMBER, TASK_ID, and TASK_NUMBER. Invoice detail includes INVOICE_ID, INVOICE_NUMBER, INVOICE_DATE, INVOICE_LINE_NUMBER, INVOICE_DISTRIBUTION_ID, DISTRIBUTION_LINE_NUMBER, PAYMENT_NUM, and CHECK_NUMBER. Vendor data includes VENDOR_ID, VENDOR_NUMBER, and VENDOR_NAME. Expenditure and accounting data include EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_TYPE, QUANTITY, DENOM_CURRENCY_CODE, DENOM_AMOUNT, ACCT_CURRENCY_CODE, AMOUNT, ACCT_RATE_DATE, ACCT_RATE_TYPE, and ACCT_EXCHANGE_RATE. Period and status columns include PA_DATE, PERIOD_NAME, GL_DATE, GL_PERIOD_NAME, POSTED_FLAG, SAME_PA_GL_PERIOD, and the controlling EXCEPTION_CODE, EXCEPTION_REASON, and CORRECTIVE_ACTION fields. ORG_ID and SET_OF_BOOKS_ID provide multi-organization and ledger context.

Common Use Cases and Queries

The primary use case is diagnosing why a Projects period cannot be closed, using EXCEPTION_CODE and CORRECTIVE_ACTION to direct remediation. A typical query filters by period and project:

  • SELECT project_number, task_number, invoice_number, vendor_name, exception_code, exception_reason, corrective_action, period_name FROM pa_ap_inv_exceptions_det_v WHERE period_name = :period AND project_number = :project;
  • SELECT exception_code, COUNT(*) FROM pa_ap_inv_exceptions_det_v WHERE period_name = :period GROUP BY exception_code;
  • SELECT invoice_number, invoice_line_number, distribution_line_number, amount, acct_currency_code, gl_period_name, correctice_action FROM pa_ap_inv_exceptions_det_v WHERE posted_flag = 'N' AND org_id = :org_id;

These queries support periodic exception reporting, reconciliation of unposted Payables distributions against project expenditures, and audit of invoices whose GL and PA periods differ, as signaled by SAME_PA_GL_PERIOD.