Results for “distribution_num”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_RCV_EXCEPTIONS_DET_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to identify the receipts that prevent a Projects period from being closed. The view exposes receipt-level exception detail — including purchasing, vendor, project, task, currency, and accounting attributes — so that users can diagnose and resolve the receipt-related conditions blocking period-end close. It is a reporting and diagnostic object rather than a transactional table; it does not store data itself, but presents a joined, denormalized read of exception data already consolidated in the summary view PA_RCV_EXCEPTIONS_SUM_V.

Underlying Base Objects

The view is defined over PA_RCV_EXCEPTIONS_SUM_V, which supplies the exception and amount facts, joined to descriptive master and transaction tables to add readable identifiers. The documented base objects are: PA_RCV_EXCEPTIONS_SUM_V (VIEW); PA_PROJECTS_ALL, PA_TASKS, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and RCV_SHIPMENT_HEADERS (all SYNONYMs); PO_VENDORS (VIEW); and the packages PA_EXCEPTION_REASONS_PUB, PA_EXPENDITURES_UTILS, and PA_UTILS. The joins are: PROJECT_ID to PA_PROJECTS_ALL, TASK_ID to PA_TASKS, VENDOR_ID to PO_VENDORS, SHIPMENT_HEADER_ID to RCV_SHIPMENT_HEADERS, PO_HEADER_ID to PO_HEADERS_ALL, PO_LINE_ID to PO_LINES_ALL, and PO_LINE_LOCATION_ID to PO_LINE_LOCATIONS_ALL. This structure lets the view carry both the exception classification and the human-readable purchasing and project context.

Key Columns

The view exposes project and task identification (PROJECT_ID, PROJECT_NUMBER, TASK_ID, TASK_NUMBER), receipt and purchasing detail (RCV_TRANSACTION_ID, RECEIPT_NUMBER, PO_HDR.SEGMENT1, PO_LINE.LINE_NUM, PO_SHIP.SHIPMENT_NUM, DISTRIBUTION_NUM), and vendor attributes (VENDOR_ID, VENDOR_NUMBER, VENDOR_NAME). Expenditure context includes EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_TYPE, and OU_NAME. Two currency/amount pairs are important for reconciliation: DENOM_CURRENCY_CODE with DENOM_AMOUNT (entered/denominated amounts), and ACCT_CURRENCY_CODE with AMOUNT (accounted amounts), alongside ACCT_RATE_DATE, ACCT_RATE_TYPE, and ACCT_EXCHANGE_RATE. Date and period fields include PA_DATE, PERIOD_NAME, GL_DATE, GL_PERIOD_NAME, and the SAME_PA_GL_PERIOD flag. The exception itself is described by EXCEPTION_CODE, EXCEPTION_REASON, and CORRECTIVE_ACTION. The searched term "denom_amount" maps directly to the DENOM_AMOUNT column, which represents the receipt amount in the entered (denominated) currency.

Common Use Cases and Queries

Typical usage is period-close troubleshooting: listing unresolved receipts, grouping exceptions by reason, and reviewing denominated versus accounted amounts for currency reconciliation. Because DENOM_AMOUNT is frequently sought, a common query filters or aggregates on it.

• List exceptions for a project and period:

  SELECT project_number, task_number, receipt_number,
         denom_currency_code, denom_amount,
         acct_currency_code, amount,
         exception_code, exception_reason, corrective_action
  FROM   apps.pa_rcv_exceptions_det_v
  WHERE  period_name = :period
  AND    project_number = :project;

• Summarize denominated amounts by exception reason:

  SELECT exception_code, exception_reason,
         COUNT(*) cnt, SUM(denom_amount) total_denom
  FROM   apps.pa_rcv_exceptions_det_v
  GROUP  BY exception_code, exception_reason;

• Identify receipts with equivalent PA and GL periods and no corrective action:

  SELECT receipt_number, vendor_name, denom_amount, pa_date, gl_date
  FROM   apps.pa_rcv_exceptions_det_v
  WHERE  same_pa_gl_period = 'Y'
  AND    corrective_action IS NULL;

These queries support close monitoring and remediation of the receipt exceptions the view is designed to surface.