Search Results pa_dr_exceptions_sum_v




Overview
Explore in AI Chat

Overview

PA_DR_EXCEPTIONS_SUM_V is an APPS-owned reporting view within the Oracle E-Business Suite Projects (PA) module. Its documented purpose is to identify Draft Revenues that prevent an accounting period from being closed. In the period-close workflow for Projects, unreleased or rejected draft revenue records can block the transfer of revenue to General Ledger and, consequently, the closing of the associated GL period. This view surfaces exactly those blocking entries, so that finance and project accounting staff can locate and resolve them before attempting to close.

The view is not a transactional object; it is a query-only construct intended for diagnostics, reporting, and exception monitoring. It presents one summarized row per draft revenue document, project, period, and agreement combination, aggregating the constituent item amounts. Critically, it also derives human-readable exception text and corrective-action guidance through a call to the PA_EXCEPTION_REASONS_PUB package, mapping the internal transfer status and rejection reason codes into explanatory messages.

Underlying Base Objects

The view is defined over a set of base tables and supporting objects, exposed to APPS through synonyms:

  • PA_DRAFT_REVENUES — the header-level draft revenue records, supplying draft revenue number, project, date, agreement, transfer status, and rejection reason.
  • PA_DRAFT_REVENUE_ITEMS — the detail lines whose amounts are summed.
  • PA_PERIODS — used to derive the accounting period name by bracketing the draft revenue date between the period start and end dates.
  • PA_IMPLEMENTATIONS — filters the view to instances where the revenue-to-GL interface flag is enabled.
  • GL_INTERFACE, GL_JE_CATEGORIES, GL_JE_SOURCES — referenced in the second branch of the UNION, used to detect draft revenues whose related journal lines remain unposted in the GL interface.
  • XLA_EVENTS — part of the subquery logic that determines whether an entry is genuinely blocking period close.
  • PA_EXCEPTION_REASONS_PUB — a PL/SQL package that converts status codes into readable exception reason and corrective-action text.

The view joins headers to items on draft revenue number and project, and to periods on date. Its two-branch UNION combines revenues that are blocked by transfer status with those still pending in the GL interface.

Key Columns

  • DRAFT_REVENUE_NUM — identifier of the draft revenue document.
  • PROJECT_ID — the project to which the draft revenue belongs.
  • PA_DATE — the accounting date used to resolve the period.
  • PERIOD_NAME — the accounting period the draft revenue falls within, the period at risk of being blocked.
  • AGREEMENT_ID — the associated agreement or contract.
  • AMOUNT — the summed amount across draft revenue items.
  • TRANSFER_REJECTION_REASON — the coded reason the transfer was rejected.
  • EXCEPTION_REASON — decoded explanatory text derived via PA_EXCEPTION_REASONS_PUB.
  • CORRECTIVE_ACTION — the recommended resolution for the exception.

Common Use Cases and Queries

The primary use case is pre-close diagnostics: run the view for a target period to list all draft revenues that will block close, then act on the exception reason and corrective action.

  • Identify all blocking draft revenues for a period.
  • Report aggregated blocked amounts by project.
  • Drive a workflow or alert that notifies project accountants of unresolved exceptions.

Sample query:

  • SELECT period_name, project_id, draft_revenue_num, amount, exception_reason, corrective_action FROM pa_dr_exceptions_sum_v WHERE period_name = :period ORDER BY project_id;
  • SELECT project_id, SUM(amount) blocked_amount FROM pa_dr_exceptions_sum_v WHERE period_name = :period GROUP BY project_id;

Because the view summarizes items, it is well suited to exception dashboards and to validating that no blocking draft revenues remain before the period-close process proceeds.