Search Results pa_cc_exceptions_sum_v




Overview
Explore in AI Chat

Overview

PA_CC_EXCEPTIONS_SUM_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. It exposes cross charge distributions that prevent an accounting period from being closed. Cross charges arise when costs incurred by one organization are shared with, or transferred to, another organization within the enterprise; when a cross charge distribution carries a transfer status of Pending, Rejected, or an equivalent non-final state, the resulting distribution blocks period close. This view isolates exactly those blocking rows so that period close reports and reconciliation processes can surface them to the user.

Because the view aggregates exception-relevant attributes from distribution, expenditure, project, and organization data, it serves as a consolidated reporting surface. Rather than requiring the report to join the underlying transactional tables itself, the view pre-assembles project identity, receiving organization, expenditure detail, distribution amount, and human-readable exception text. This makes it suitable both for the standard period close exception reports and for ad hoc diagnostics during the close cycle. The object is documented as VALID in the ETRM 12.2.2 metadata and is intended for read-only query access.

Underlying Base Objects

The view is defined over several synonym-backed base tables and one PL/SQL package. The documented referenced objects are PA_CC_DIST_LINES_ALL (the cross charge distribution lines driving exception status), PA_EXPENDITURE_ITEMS_ALL (the expenditure item detail), PA_EXPENDITURES_ALL (the expenditure header), PA_PROJECTS (project number and organization), HR_ALL_ORGANIZATION_UNITS_TL (receiving organization name, joined in translation), XLA_EVENTS, and the PA_EXCEPTION_REASONS_PUB package. The distribution lines are joined to expenditure items on EXPENDITURE_ITEM_ID, expenditure items to expenditures on EXPENDITURE_ID, and distributions to projects on PROJECT_ID. The receiving organization is resolved through a non-enforcing outer join to HR_ALL_ORGANIZATION_UNITS_TL, with a language predicate aligning the translation row to the session language.

Critically, the view filters the distribution lines on TRANSFER_STATUS_CODE IN ('P','R','X'), which is what restricts the result set to distributions that block period close. The exception reason and corrective action columns are not stored values; they are produced by calling PA_EXCEPTION_REASONS_PUB.GET_EXCEPTION_TEXT with the exception context 'CC_EXCP', the TRANSFER_REJECTION_CODE, and a mode indicator of 'R' (reason) or 'A' (action).

Key Columns

Common Use Cases and Queries

The primary use case is the period close exception report: identifying every cross charge distribution that must be resolved before a period can be closed. A user may also run targeted queries by project or organization to investigate a specific hold.

  • List all blocking exceptions for a period:
    SELECT project_number, task_id, recvr_org_name, expenditure_item_date, amount, exception_reason, corrective_action FROM pa_cc_exceptions_sum_v WHERE period_name = :period;
  • Filter to a single project:
    SELECT * FROM pa_cc_exceptions_sum_v WHERE project_number = :project_number;
  • Summarize exceptions by receiving organization:
    SELECT recvr_org_name, COUNT(*), SUM(amount) FROM pa_cc_exceptions_sum_v GROUP BY recvr_org_name;

Because the view already filters to non-final transfer statuses, queries need not repeat the status predicate, though callers may add one on EXCEPTION_CODE for finer control. All access should be read-only through the APPS schema.