Search Results cc_excp




Overview
Explore in AI Chat

Overview

APPS.PA_CC_EXCEPTIONS_SUM_V is a reporting view in Oracle E-Business Suite that consolidates cross-charging distribution lines that have failed or are pending processing between expenditure subsystems and Oracle Projects. The view surfaces the exceptions generated during the cross-charge transfer process, together with the reasons for the rejection and the recommended corrective action. It draws from distribution lines whose transfer status code falls within the pending, rejected, or error range, and it is intended to give users a single consolidated picture of every applicable transaction that could not be transferred normally.

Because cross-charging involves determining the receiving organization for a cost, the view exposes both the receiving organization identifier and its translated name. The RECVR_ORG_NAME column that users commonly search for is sourced from the organization name translation table, joined to the receiving organization identifier on the expenditure item. A consequence of this join is that the name is filtered by the session language, so the same organization can resolve to different translated names depending on the language environment of the querying session. The null-safe decoding in the join also ensures that rows are not lost when no translated organization name can be found. The view is defined over a union, which merges multiple exception categories into a single result set for consistent reporting and integration consumption.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PA_CC_DIST_LINES_ALL — the cross-charge distribution lines, supplying the line number, project and task references, accounting currency, amount, transfer status and rejection codes, and period name.
  • PA_EXPENDITURE_ITEMS_ALL — the expenditure items, supplying the receiving organization, the expenditure item identifier and date, expenditure type, and system linkage function.
  • PA_EXPENDITURES_ALL — the parent expenditures, supplying the incurred-by person, vendor, and incurred-by organization.
  • PA_PROJECTS — supplying the project number (segment1) and operating unit (org_id).
  • HR_ALL_ORGANIZATION_UNITS_TL — supplying the translated organization name used for the receiving organization.
  • PA_EXCEPTION_REASONS_PUB — a package invoked in the select list to convert the transfer rejection code into readable exception reason and corrective action text.
  • XLA_EVENTS — a documented referenced object associated with the subledger accounting event flow.

The tables are joined on expenditure item, expenditure, project, and receiving organization keys. The organization name join is an outer join with language filtering, and the exception text is obtained through a function within the exception reasons package.

Key Columns

Common Use Cases and Queries

Typical usage is exception reporting for cross-charge processing, resolution of rejected transfers, and feeder queries into reconciliation processes. Analysts commonly filter by receiving organization or project to isolate outstanding exceptions.

  • List all rejected cross-charge lines for a project: SELECT project_number, task_id, recvr_org_name, amount, exception_reason FROM pa_cc_exceptions_sum_v WHERE project_number = :p_project;
  • Aggregate exceptions by receiving organization: SELECT recvr_org_name, COUNT(*) exceptions, SUM(amount) amount FROM pa_cc_exceptions_sum_v GROUP BY recvr_org_name;
  • Locate exceptions pending transfer: SELECT expenditure_item_id, recvr_org_id, corrective_action FROM pa_cc_exceptions_sum_v WHERE transfer_rejection_code IS NULL;

Because the view joins the translated organization name, queries returning RECVR_ORG_NAME should be executed in the intended language session to obtain the appropriate organization name.