Results for “document_distribution_type”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_COST_EXCEPTIONS_SUM_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to identify the details of Cost Distribution Lines that prevent a project accounting period from being closed. During the period-close process in Oracle Projects, cost distribution lines must be successfully transferred before the accounting period can be closed. Lines that remain in a pending, rejected, or otherwise unprocessed transfer state act as blockers to closure. This view surfaces exactly those lines, along with the exception reason and the recommended corrective action, providing both a diagnostic and a reporting mechanism for the period-close workflow.

Because it is a view rather than a table, it imposes no storage of its own and is always current with the underlying transactional data. It functions as a central reference for project accountants, cost analysts, and technical consultants who must resolve cost transfer failures before running period close.

Underlying Base Objects

The view is defined over several documented base objects. The primary driving object is PA_COST_DISTRIBUTION_LINES_ALL (a synonym), aliased CDL, which holds the individual cost distribution lines. It is joined to PA_EXPENDITURE_ITEMS_ALL (alias EI) on EXPENDITURE_ITEM_ID, linking each distribution line to its originating expenditure item. PA_PERIODS_ALL (alias PRD) supplies the period name and date boundaries, and the view restricts PA_DATE to fall between the period start and end dates. PA_IMPLEMENTATIONS (alias IMP) supplies ORG_ID and the interface flags (INTERFACE_LABOR_TO_GL_FLAG and INTERFACE_USAGE_TO_GL_FLAG) used to determine whether a given system linkage function should interface to General Ledger. The package PA_EXCEPTION_REASONS_PUB supplies the human-readable exception reason and corrective action through its GET_EXCEPTION_TEXT function. Additional documented references include PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, PA_PROJECT_UTILS, PA_PERIODS, and XLA_EVENTS, which support project-level context and subledger accounting event linkage.

Key Columns

Common Use Cases and Queries

The view is typically queried to list outstanding exceptions prior to period close, to diagnose rejection reasons, and to drive corrective action. A straightforward query returns current blocking lines for a period:

  • SELECT period_name, cost_distribution_line_num, transfer_status_code, exception_reason, corrective_action, amount FROM pa_cost_exceptions_sum_v WHERE period_name = 'JAN-24';
  • SELECT org_id, COUNT(*) FROM pa_cost_exceptions_sum_v GROUP BY org_id; — to gauge exception volume per operating unit.
  • SELECT * FROM pa_cost_exceptions_sum_v WHERE transfer_status_code = 'R' ORDER BY pa_date; — to isolate rejected lines requiring correction.

Because it exposes both the coded status and the descriptive reason and action, the view is well suited to ad hoc diagnostics, period-close checklists, and integration with custom reporting or dashboard tooling.