Results for “project_amount”

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

Overview

PA_GL_COST_EXCEPT_SUM_V is a reporting and diagnostic view in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and defined as a VALID database object. Its documented purpose is to identify the cost distribution lines that prevent a period from being closed or that block the transfer of costs to the General Ledger. In practice, this view serves as a consolidated exception summary, exposing only those distribution lines that carry conditions requiring user attention before period-end processing and GL transfer can complete successfully.

Because the underlying exception detail is normally spread across expenditure items, cost distribution lines, and implementation setup, this view is a convenience layer that presents joined, decoded exception information in a single queryable structure. It is commonly consumed by Project Costing reporting, period-close diagnostics, and reconciliation of rejected or unprocessed cost distributions.

Underlying Base Objects

Per the documented metadata, the view is defined over the following referenced objects:

• PA_COST_DISTRIBUTION_LINES_ALL — the core source of distribution lines, GL dates, amounts, and transfer status.
• PA_EXPENDITURE_ITEMS_ALL — provides the expenditure item detail such as task, expenditure type, vendor, and document references.
• PA_IMPLEMENTATIONS_ALL — supplies implementation-level attributes including same PA/GL period flags and set of books.
• PA_PROJECTS_ALL and PA_PROJECT_TYPES_ALL — supply project and project type context.
• PA_EXCEPTION_REASONS_PUB — a PL/SQL package invoked to derive human-readable exception reason text and corrective action text.
• PA_EXPENDITURES_UTILS — a utility package used, for example, to resolve the operating unit name from ORG_ID.
• GL_PERIOD_STATUSES — provides period status context.
• XLA_EVENTS — links distributions to subledger accounting events.
• DUAL — used in the FROM clause for decoding/single-row expressions.

The view therefore sits directly on top of the core cost distribution and expenditure tables, enriching them with exception classification logic from the PA_EXCEPTION_REASONS_PUB package.

Key Columns

• TASK_ID, EXPENDITURE_ID, EXPENDITURE_ITEM_ID — identify the project task and expenditure item associated with the exception.
• EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE — when and what type of expenditure was charged.
• COST_DISTRIBUTION_LINE_NUM, GL_DATE, PERIOD_NAME — the distribution line, accounting date, and GL period.
• TRANSFER_STATUS_CODE, TRANSFER_REJECTION_REASON — the transfer state and reason a line was rejected.
• QUANTITY, AMOUNT, DENOM_AMOUNT, PROJECT_AMOUNT — quantities and raw, denominated, and project currency amounts.
• VENDOR_ID, INVOICE_ID, INVOICE_DISTRIBUTION_ID, INVOICE_LINE_NUMBER — supplier and invoice references.
• EXCEPTION_REASON, CORRECTIVE_ACTION — decoded text from PA_EXCEPTION_REASONS_PUB describing why the line is an exception and how to correct it.
• CDL_EXCEPTION_TYPE — classifies the exception (for example, cost distribution versus burden-related).
• ORG_ID, SET_OF_BOOKS_ID, SAME_PA_GL_PERIOD — operating unit, ledger, and whether PA and GL periods align.

Common Use Cases and Queries

The view is typically used to list lines blocking period close or GL transfer, and to drive corrective action. A representative query follows:

• SELECT expenditure_item_id, cost_distribution_line_num, period_name, transfer_status_code, exception_reason, corrective_action FROM pa_gl_cost_except_sum_v WHERE org_id = :org_id AND period_name = :period_name ORDER BY period_name, cost_distribution_line_num;
• Filter on CDL_EXCEPTION_TYPE to isolate particular exception classes for operational review.

Analysts use this view to reconcile rejected cost distributions against transferred amounts before running the cost transfer process.