Search Results pa_dr_exceptions_sum_mrc_v




Overview

PA_DR_EXCEPTIONS_SUM_MRC_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that identifies Draft Revenue records which prevent an accounting period from being retrofitted. In the context of Oracle EBS 12.1.1 and 12.2.2, "retrofit" refers to the process by which adjustments to a project's revenue or billing setup are applied backward to prior periods; when unprocessed or rejected Draft Revenues exist for a period, the retrofit cannot proceed cleanly, and this view surfaces exactly those blocking records.

The view is documented as multi-reporting-currency (MRC) aware, as indicated by the _MRC_V suffix and its use of the PA_MC_DRAFT_REVS_ALL and PA_DRAFT_REVENUE_ITEMS_MRC_V objects. It aggregates Draft Revenue Item amounts and presents descriptive exception reasons and corrective actions for each blocking Draft Revenue, making it a diagnostic tool for project accounting specialists and for concurrent programs that validate period-retrofit eligibility.

Underlying Base Objects

Although the supplied metadata lists no separately documented referenced base objects, the view text itself defines the sources. It joins the following objects:

The WHERE clause restricts results to Draft Revenues with TRANSFER_STATUS_CODE IN ('P','R','X'), corresponding to pending, rejected, or otherwise unprocessed transfer states. Two result sets are combined with UNION ALL.

Key Columns

  • SET_OF_BOOKS_ID — the ledger for which the MRC Draft Revenue applies.
  • DRAFT_REVENUE_NUM / PROJECT_ID — identify the offending Draft Revenue and its project.
  • PA_DATE / PERIOD_NAME — the revenue date and the accounting period it falls into, tying the exception to the period that cannot be retrofitted.
  • AGREEMENT_ID — the project agreement associated with the revenue.
  • AMOUNT — the summed Draft Revenue Item amount, indicating the financial magnitude of the blocking entry.
  • TRANSFER_STATUS_CODE — the underlying status driving the exception.
  • TRANSFER_REJECTION_REASON — the stored reason the transfer was rejected.
  • EXCEPTION_REASON — derived via PA_EXCEPTION_REASONS_PUB.GET_EXCEPTION_TEXT('REV_EXCP', ...) with mode 'R', giving a readable explanation.
  • CORRECTIVE_ACTION — the same function with mode 'A', supplying the recommended resolution text.
  • ORG_ID — the operating unit of the implementation and revenue.

Common Use Cases and Queries

The primary use is diagnosing why a period cannot be retrofitted. A typical query lists all blocking exception revenues for a project or period:

  • SELECT project_id, draft_revenue_num, period_name, amount, exception_reason, corrective_action FROM pa_dr_exceptions_sum_mrc_v WHERE project_id = :project_id ORDER BY period_name;
  • Filtering by ledger: ... WHERE set_of_books_id = :sob_id to isolate exceptions for a specific reporting currency set of books.
  • Summarizing total blocked amounts: SELECT period_name, SUM(amount) FROM pa_dr_exceptions_sum_mrc_v GROUP BY period_name;
  • Targeting unresolved statuses: ... WHERE transfer_status_code = 'R' to focus on rejected revenues requiring correction.

Because it exposes both EXCEPTION_REASON and CORRECTIVE_ACTION, the view supports troubleshooting workflows and can feed custom reports or validation logic that pre-checks retrofit eligibility before period close.