Search Results pa_gl_dr_except_det_v




Overview
Explore in AI Chat

Overview

PA_GL_DR_EXCEPT_DET_V is an Oracle EBS Projects (PA) view owned by the APPS schema. It is a diagnostic reporting object whose purpose is to identify the specific draft revenue records that prevent a Projects accounting period from being closed. When the period-close process determines that draft revenues have not been interfaced to Oracle General Ledger, PA_GL_DR_EXCEPT_DET_V supplies the line-level detail behind that exception, allowing the root cause to be investigated and remediated.

The view sits at the intersection of the Projects and General Ledger integration flows. It exposes the draft revenue number, the associated project, the GL date and period, the amount, and — most importantly for remediation — the exception reason and the corrective action. The presence of CORRECTION_ACTION (aliased from the underlying CORRECTIVE_ACTION column) is what makes this view actionable rather than merely informational: the user searching on "correction_action" is looking for the guidance text that tells them how to resolve each blocking draft revenue.

The view is read-only and derived; it does not store data itself. Its status in the ETRM repository is VALID, and it is documented for both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over two primary sources joined on project and operating unit:

  • PA_GL_DR_EXCEPT_SUM_V — the summary exception view supplying draft revenue number, project, currency, GL date, period, agreement, amount, transfer rejection reason, exception reason, corrective action, operating unit, the same-period indicator, and set of books.
  • PA_PROJECTS_ALL (referenced as a synonym) — the project master, used to retrieve SEGMENT1 as the project number.

The ETRM metadata additionally lists two package dependencies: PA_EXPENDITURES_UTILS, whose GETORGTLNAME function resolves the operating unit name, and PA_EXCEPTION_REASONS_PUB, which supports the exception reason and corrective action logic. The join condition is PRJ.PROJECT_ID = SMRY.PROJECT_ID combined with a null-safe operating unit match: NVL(PRJ.ORG_ID,-99) = NVL(SMRY.ORG_ID,-99), which ensures projects are matched to the correct operating unit even when ORG_ID is null.

Key Columns

  • DRAFT_REVENUE_NUM — the draft revenue identifier, the primary key for remediation.
  • PROJECT_ID / PROJECT_NUMBER / PROJECT_CURRENCY_CODE — project identifiers and the project's functional currency.
  • GL_DATE / PERIOD_NAME — the GL accounting date and period associated with the draft revenue.
  • AGREEMENT_ID / AMOUNT — the funding agreement and the draft revenue amount.
  • TRANSFER_REJECTION_REASON / EXCEPTION_REASON — why the revenue failed to transfer to GL.
  • CORRECTION_ACTION — the recommended corrective action to clear the exception, the column of principal interest here.
  • ORG_ID / OU_NAME — the operating unit identifier and its resolved name.
  • SAME_PA_GL_PERIOD — indicates whether the PA and GL periods coincide, a relevant factor in transfer eligibility.
  • SET_OF_BOOKS_ID — the ledger to which the revenue would be interfaced.

Common Use Cases and Queries

The primary use case is investigating why a period will not close. A typical query lists all blocking draft revenues with their corrective actions:

  • Period-close blockage report: 
    SELECT draft_revenue_num, project_number, period_name,
       amount, exception_reason, correction_action
FROM   apps.pa_gl_dr_except_det_v
WHERE  period_name = :p_period;
  • Filter by operating unit using ORG_ID or OU_NAME to scope the investigation to a single business unit.
  • Focus on a specific project via PROJECT_ID or PROJECT_NUMBER to isolate unresolved revenues for that project.
  • Identify same-period conflicts by testing SAME_PA_GL_PERIOD where PA and GL periods do not align.
  • Group exceptions by reason — SELECT exception_reason, COUNT(*) FROM apps.pa_gl_dr_except_det_v GROUP BY exception_reason — to prioritize corrective actions across a period.

Because the view derives from PA_GL_DR_EXCEPT_SUM_V, it is intended for reporting and diagnosis only. Any corrective action must be applied through standard Projects revenue-interface and period-close processes, not written back to the view.