Search Results rev_excp




Overview
Explore in AI Chat

Overview

APPS.PA_GL_DR_EXCEPT_SUM_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that surfaces summarized draft revenue distribution exceptions encountered during the transfer of revenue to Oracle General Ledger. The view consolidates draft revenue records that were rejected or otherwise flagged during the interface process and presents them alongside human-readable exception descriptions. Its primary purpose is to support the diagnostics of failed or held revenue-to-GL transfers, allowing users to identify why specific draft revenue batches did not reach the general ledger.

The name and the embedded call to PA_EXCEPTION_REASONS_PUB.GET_EXCEPTION_TEXT('REV_EXCP', ...) establish the view's connection to the "rev_excp" (revenue exception) reference category. The literal REV_EXCP passed as the exception category argument is the exact token for which the object was searched. The view functions as the data source behind revenue exception reporting and is tightly coupled to the revenue transfer workflow that moves Project Accounting draft revenue into GL_INTERFACE and subsequently into GL_JE_BATCHES and GL_JE_HEADERS.

Underlying Base Objects

The view is defined over several Project Accounting and General Ledger objects. The documented ETRM metadata lists the following referenced base objects:

  • PA_DRAFT_REVENUES_ALL (alias DR) — the primary draft revenue header record, supplying draft revenue number, project, GL date, agreement, transfer status, rejection reason, and org identifier.
  • PA_DRAFT_REVENUE_ITEMS (alias DRI) — the line-level revenue items whose amounts are aggregated via SUM(DRI.AMOUNT).
  • PA_IMPLEMENTATIONS_ALL (aliases IMP, IMP1) — supplies the implementation flags, same-PA-GL-period indicator, set of books identifier, and the INTERFACE_REVENUE_TO_GL_FLAG used to filter active organizations.
  • GL_PERIOD_STATUSES (alias PRD) — the GL accounting period definition, joined on the GL date between period start and end dates with APPLICATION_ID = 8721 (the General Ledger application identifier) and ADJUSTMENT_PERIOD_FLAG = 'N'.
  • PA_EXCEPTION_REASONS_PUB — the package whose GET_EXCEPTION_TEXT procedure resolves the numeric rejection code into readable exception-reason and corrective-action text.
  • PA_EXPENDITURES_UTILS — supplies getorgtlname to resolve the operating unit name from the org_id.
  • GL_INTERFACE, GL_JE_CATEGORIES, GL_JE_SOURCES — GL interface and journal-entry reference objects documented against the view set.

Key Columns

Common Use Cases and Queries

The view is used to build revenue exception reports that correlate rejected draft revenues with the reasons and corrective actions documented against the "rev_excp" reference category. The underlying query filters to transfer status codes of 'P', 'R', 'X', and 'T' and excludes rows where GENERATION_ERROR_FLAG = 'Y', so it isolates transfer-stage exceptions rather than generation failures.

SELECT draft_revenue_num,
       project_id,
       period_name,
       exception_reason,
       corrective_action,
       amount,
       ou_name
  FROM apps.pa_gl_dr_except_sum_v
 WHERE org_id = :p_org_id
 ORDER BY period_name, draft_revenue_num;

Users typically filter by operating unit and accounting period to isolate revenue that failed to interface, then use the corrective-action text to determine whether the transfer must be re-run, corrected, or released manually. Because the view depends on PA_IMPLEMENTATIONS_ALL with INTERFACE_REVENUE_TO_GL_FLAG = 'Y', it only returns data for organizations enabled for revenue-to-GL interfacing, making it a dependable operational diagnostic tool for the Project Accounting revenue transfer cycle.