Search Results exception_reason




Overview
Explore in AI Chat

Overview

PA_DR_EXCEPTIONS_DET_MRC_V is a reporting view within the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to surface the detail-level Draft Revenue records that block a project accounting period from being retrofitted. In the Projects revenue recognition cycle, draft revenues must be transferred before a period can be retrofitted; when a transfer fails or is rejected, the affected period remains locked in the current state. This view isolates the offending records so that the revenue accountant or interfacing application can identify precisely which draft revenue entries require correction, reversal, or manual intervention.

The "MRC" suffix indicates that the view is part of the Multi-Reporting Currency (MRC) reporting layer. It therefore exposes reporting-currency-aware data rather than single-ledger columns, and it is intended for use where multiple sets of books are configured. The view is documented in ETRM as "Not implemented in this database," meaning it exists as a seeded database object definition but may not be instantiated in every environment; its availability depends on the deployment of the underlying MRC summary view.

Underlying Base Objects

The ETRM metadata for this view does not document any referenced base tables. The view text itself, however, reveals its construction. It is defined as a join between two sources:

  • PA_DR_EXCEPTIONS_SUM_MRC_V — the MRC summary view supplying draft revenue number, project, amount, period, and exception attributes aliased as SMRY.
  • PA_PROJECTS_ALL — the transactional project definition table, aliased as PRJ, joined on PROJECT_ID to supply the project number and project currency code.

The relationship is a simple equijoin on PROJECT_ID (PRJ.PROJECT_ID = SMRY.PROJECT_ID). Because the view is defined over a summary MRC view, it inherits the reporting-currency context from that summary and adds only the project-level descriptive columns. No direct link to the underlying draft revenue tables appears in the documented metadata, as those are reached through the summary view.

Key Columns

  • SET_OF_BOOKS_ID — the set of books (ledger) in whose reporting currency the amounts are expressed.
  • DRAFT_REVENUE_NUM — the draft revenue document number, the primary identifier of the offending record.
  • PROJECT_ID / PROJECT_NUMBER — the project key and its concatenated segment value from PA_PROJECTS_ALL.
  • PROJECT_CURRENCY_CODE — the functional currency of the project, useful for reconciling project versus ledger amounts.
  • PA_DATE — the document date associated with the draft revenue summary, the field most often filtered when tracing period activity; the user query "pa_date" maps directly here.
  • PERIOD_NAME — the accounting period that cannot be retrofitted because of this record.
  • AGREEMENT_ID — the contract or agreement under which the revenue was drafted.
  • AMOUNT — the draft revenue amount in the reporting-currency context of the set of books.
  • TRANSFER_REJECTION_REASON / EXCEPTION_REASON — textual diagnostics explaining why the transfer was rejected or flagged.
  • CORRECTION_ACTION — the recommended corrective action to clear the exception.

Common Use Cases and Queries

The primary use case is diagnosing a failed period retrofit. Before retrofitting, the revenue accountant queries this view to enumerate every blocking draft revenue. A typical query filters by period and mode of books:

  • List all exceptions for a given period: SELECT project_number, draft_revenue_num, pa_date, amount, exception_reason FROM pa_dr_exceptions_det_mrc_v WHERE period_name = :p_period ORDER BY project_number;
  • Trace a specific document date range: SELECT draft_revenue_num, pa_date, correction_action FROM pa_dr_exceptions_det_mrc_v WHERE pa_date BETWEEN :from_date AND :to_date;
  • Drive a correction interface that extracts TRANSFER_REJECTION_REASON and CORRECTION_ACTION to route items to the appropriate revenue adjustment workflow.

Because the view is MRC-scoped, queries should always account for SET_OF_BOOKS_ID when multiple ledgers are defined. Combined with PA_DR_EXCEPTIONS_SUM_MRC_V, it forms the diagnostic layer used to clear exceptions before period-end retrofitting.