Search Results cost_distribution_line_num




Overview
Explore in AI Chat

Overview

APPS.PA_COST_EXCEPTIONS_SUM_V is a reporting view in Oracle EBS Projects (PA) that consolidates cost distribution lines which have failed or are pending transfer to General Ledger. It surfaces expenditure transactions whose TRANSFER_STATUS_CODE falls into the pending/rejected exception set, presenting each affected cost distribution line alongside its source expenditure item, the accounting period it belongs to, and human-readable exception reason and corrective action text. The view acts as the primary diagnostic surface for the "Cost Exceptions" workflow in Project Costing, allowing users and integrators to identify rejected distributions, understand why they were rejected, and obtain the corrective guidance maintained in the exception reason setup.

Because the view joins cost distribution lines, expenditure items, implementation options, and period definitions, it reconciles transaction-level detail with the period table required for GL transfer eligibility. The cost_distribution_line_num referenced by the user corresponds to the LINE_NUM column of PA_COST_DISTRIBUTION_LINES_ALL, exposed here as COST_DISTRIBUTION_LINE_NUM; it is the unique line identifier within an expenditure item's distribution set and is the column most commonly used when troubleshooting individual rejected lines.

Underlying Base Objects

The documented view definition selects from four primary objects and references several auxiliary ones:

The view is defined as a UNION of two branches, each tuned with a LEADING/USE_NL hint against the PA_COST_DISTRIBUTION_LINES_N7 index, reflecting the original optimization for exception-driven access paths.

Key Columns

Common Use Cases and Queries

The view supports cost exception inquiries, reconciliation of unposted costs, and integration diagnostics. A representative query filtering on the distribution line number is:

SELECT cost_distribution_line_num, task_id, expenditure_item_id,
       period_name, transfer_status_code,
       exception_reason, corrective_action, amount
FROM   apps.pa_cost_exceptions_sum_v
WHERE  cost_distribution_line_num = :line_num
AND    org_id = :org_id;

Grouping by period and exception reason produces a management summary of the unposted cost backlog:

SELECT period_name, exception_reason, COUNT(*) lines, SUM(project_amount) amt
FROM   apps.pa_cost_exceptions_sum_v
GROUP  BY period_name, exception_reason;

Because the view returns only pending, rejected, or in-progress transfer statuses, it is well suited to daily exception monitoring reports and to integrations that must resolve rejects before the period close.