Search Results po_line




Overview
Explore in AI Chat

Overview

APPS.PA_RCV_EXCEPTIONS_DET_V is a Projects (PA) reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes receiving exceptions detected against project-related purchase order receipts. It is the detail-level companion to PA_RCV_EXCEPTIONS_SUM_V, resolving the summary view's foreign keys into descriptive attributes drawn from Projects, Purchasing, and Receiving. The view surfaces exception records together with project number, task number, vendor number and name, receipt number, PO number, PO line number, shipment number, distribution number, expenditure organization, expenditure type, and the original accounting amounts and currency. Because the view joins receipt, PO, vendor, and project data in a single query, it is the primary source for operational reporting and corrective-action workflows that need to trace why a receiving transaction failed project validation, such as a missing or invalid expenditure type, an unmatched project or task, or a mismatch between the receiving and GL periods. The view is owned by APPS and is intended for read-only reporting and integration rather than transaction entry.

Underlying Base Objects

The view is defined over one view, eight synonyms, and supporting PL/SQL packages as documented in ETRM 12.2.2. The driving object is PA_RCV_EXCEPTIONS_SUM_V, which supplies the exception rows, project and task identifiers, vendor identifier, shipment header identifier, PO header identifier, PO line identifier, PO line location identifier, expenditure organization and type, denominations, amounts, accounting rate data, period names, exception code, reason, and corrective action. The join targets are PA_PROJECTS_ALL, PA_TASKS, and PO_VENDORS, resolved through the PROJECT_ID, TASK_ID, and VENDOR_ID keys to return project number, task number, vendor number, and vendor name. Purchasing and receiving detail is obtained through PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and RCV_SHIPMENT_HEADERS, linked by po_header_id, po_line_id, po_line_location_id, and shipment_header_id respectively, providing the PO number (po_hdr.segment1), line number (po_line.line_num), shipment number (po_ship.shipment_num), distribution number, and receipt number. The referenced packages PA_EXCEPTION_REASONS_PUB, PA_EXPENDITURES_UTILS, and PA_UTILS underpin the logic used to populate the summary view.

Key Columns

Common Use Cases and Queries

Typical usage includes locating exceptions by PO line, reviewing unresolved exceptions by project or vendor, and validating period alignment between PA and GL. The following example retrieves exception detail for a specific PO line:

  • SELECT project_number, task_number, receipt_number, segment1, line_num, shipment_num, exception_code, exception_reason, corrective_action FROM apps.pa_rcv_exceptions_det_v WHERE segment1 = :po_number AND line_num = :po_line;
  • SELECT project_number, vendor_name, SUM(denom_amount) FROM apps.pa_rcv_exceptions_det_v WHERE exception_code IS NOT NULL GROUP BY project_number, vendor_name;
  • SELECT * FROM apps.pa_rcv_exceptions_det_v WHERE same_pa_gl_period = 'N';

These queries support exception monitoring, period-close reconciliation, and downstream integration into corrective-action reporting.