Search Results rcv_sub

Overview

APPS.PA_RCV_EXCEPTIONS_SUM_V is a Projects (PA) module reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents receiving-related expenditure exceptions that arise when receipt accounting activity cannot be added to a project as an expenditure item. The view brings together purchasing distribution data, receiving transaction data, receiving sub-ledger accounting entries, and Projects implementation settings to expose each exception with its reason and suggested corrective action.

The view is read-only and is used primarily for reporting, inquiry, and integration. It surfaces rows attributable to the RCV_HDR receiving shipment header, and its output is typically consumed by exception dashboards, reconciliation reports, and interfaces that notify project accountants of receipts that failed the automatic expenditure import process. Because it depends on the PA_EXCEPTION_REASONS_PUB messages, it delivers both a coded exception and human-readable explanatory text.

Underlying Base Objects

The view is defined over the following documented base objects:

• PO_DISTRIBUTIONS_ALL (SYNONYM) — provides project, task, expenditure organization, expenditure type, distribution number, and the accrue_on_receipt_flag.
• RCV_TRANSACTIONS (SYNONYM) — provides the receiving transaction, destination type, transaction type, PO references, and vendor.
• RCV_RECEIVING_SUB_LEDGER (SYNONYM) — provides the accounting entries (entered/accounted amounts, GL period, PA addition flag).
• RCV_SHIPMENT_HEADERS (SYNONYM) — supplies receiving shipment header context, matched previously by the user search term "rcv_hdr".
• PA_IMPLEMENTATIONS_ALL (SYNONYM) — links the expenditure organization to a set of books and PA/GL period comparison.
• PA_EXCEPTION_REASONS_PUB (PACKAGE) — returns EXCEPTION_REASON and CORRECTIVE_ACTION text.
• PA_EXPENDITURES_UTILS (PACKAGE) — returns the organization name via getorgtlname.
• PA_UTILS (PACKAGE) — derives PA_DATE and PERIOD_NAME.

Key Columns

• PROJECT_ID, TASK_ID — the project and task to which the receipt distribution relates.
• TRANSACTION_ID, SHIPMENT_HEADER_ID, PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID — purchasing and receiving identifiers.
• VENDOR_ID — supplier associated with the receipt.
• CURRENCY_CODE, ENTERED_DR, ACCOUNTED_DR, FUNCTIONAL_CURRENCY_CODE, CURRENCY_CONVERSION_DATE/TYPE/RATE — sub-ledger accounting amounts and currency conversion details.
• EXCEPTION_CODE — derived from RCV_SUB.PA_ADDITION_FLAG, restricted to 'N' or 'I'.
• EXCEPTION_REASON and CORRECTIVE_ACTION — text returned by PA_EXCEPTION_REASONS_PUB for exception type 'RECEIPT_EXCP'.
• EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE — project expenditure attributes.
• GL_DATE, PA_DATE, PERIOD_NAME, GL_PERIOD_NAME — GL transaction date, derived PA date, and PA/GL period names.
• ORG_ID, SET_OF_BOOKS_ID, SAME_PA_GL_PERIOD — operating unit, ledger, and PA/GL period alignment flag.
• The organization name returned by PA_EXPENDITURES_UTILS.getorgtlname.

Common Use Cases and Queries

The view is commonly used to list exception receipts for a project, expenditure organization, or ledger.

• Project exception listing:

  SELECT project_id, task_id, transaction_id,Exception_code, Exception_reason, Corrective_action FROM apps.pa_rcv_exceptions_sum_v WHERE project_id = :project_id;

• Exceptions by expenditure organization and PA period:

  SELECT expenditure_organization_id, period_name, exception_code, COUNT(*) FROM apps.pa_rcv_exceptions_sum_v GROUP BY expenditure_organization_id, period_name, exception_code;

• Receipt header drill-down (matching the "rcv_hdr" search):

  SELECT transaction_id, shipment_header_id, po_header_id, vendor_id,exception_reason FROM apps.pa_rcv_exceptions_sum_v WHERE shipment_header_id = :shipment_header_id;