Results for “pa_dr_exceptions_det_v”

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

Overview

The PA_DR_EXCEPTIONS_DET_V view is a Projects (PA) module reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes detailed information about Draft Revenue records that block the successful closing of an accounting period. The name itself reflects this purpose: "PA" (Projects), "DR" (Draft Revenue), and "EXCEPTIONS" — records that cannot be transferred or processed normally.

During period close, Draft Revenue must be transferred to Oracle Subledger Accounting or General Ledger. When a draft revenue fails validation or transfer, it becomes an exception that prevents the period from being closed. This view surfaces those exceptions at a detail level, joining summary exception data to the project master so that report developers and administrators can identify offending records and take corrective action. It is a read-only, APPS-owned, VALID view. The user search term "pa_date" corresponds directly to a column exposed by this view, which carries the accounting or project date associated with the draft revenue.

Underlying Base Objects

The view is defined with a two-table join:

• PA_DR_EXCEPTIONS_SUM_V — A summary view supplying the exception-level attributes: draft revenue number, project, PA_DATE, period name, agreement, amount, transfer rejection reason, exception reason, and corrective action.
• PA_PROJECTS_ALL — The Projects base synonym, joined on PROJECT_ID to retrieve the project number (SEGMENT1) and project currency code.
• PA_EXCEPTION_REASONS_PUB — A public package referenced by the underlying summary view, used to derive or resolve exception reason and corrective action text.

The join condition is PRJ.PROJECT_ID = SMRY.PROJECT_ID. The detail view adds the project number and project currency from the project master while preserving all exception attributes from the summary view.

Key Columns

• DRAFT_REVENUE_NUM — Identifier of the failing draft revenue.
• PROJECT_ID / PROJECT_NUMBER — Internal project identifier and the user-facing project number (SEGMENT1).
• PROJECT_CURRENCY_CODE — Currency of the affected project.
• PA_DATE — The date associated with the draft revenue; central to period determination and to the "pa_date" search.
• PERIOD_NAME — The accounting period that is blocked.
• AGREEMENT_ID — Funding agreement tied to the draft revenue.
• AMOUNT — Value of the exception draft revenue.
• TRANSFER_REJECTION_REASON — Why the transfer was rejected.
• EXCEPTION_REASON — Categorised reason the record is an exception.
• CORRECTION_ACTION — Recommended remediation step.

Common Use Cases and Queries

Typical scenarios include period-close diagnostics, exception resolution reporting, and integration with custom dashboards. A basic query lists exceptions for a period:

• SELECT project_number, draft_revenue_num, pa_date, period_name, amount, exception_reason, correction_action FROM pa_dr_exceptions_det_v WHERE period_name = :period;
• Filter by date window on PA_DATE to isolate revenue in a specific range.
• Filter by PROJECT_NUMBER to review exceptions for one project.

Administrators use the CORRECTION_ACTION text to guide remediation before reattempting the period close.