Search Results uncost_excp

Overview

APPS.PA_GL_UNCOST_EXCEPT_SUM_V is a reporting view in Oracle E-Business Suite Projects (Oracle Projects) that presents expenditure items which failed cost distribution processing and were therefore not interfaced to Oracle General Ledger. The view consolidates uncosted exception records with the descriptive context needed for investigation and correction, including project, task, expenditure, organization, and period identifiers. Its defining characteristic is the derivation of an exception code and its corresponding exception reason and corrective action, returned through calls to the PA_EXCEPTION_REASONS_PUB package and resolved against the PA_LOOKUPS lookup type UNCOST_EXCP.

The view is a summary-style reporting object rather than a transactional base table. It exists to support the Oracle Projects cost distribution exception workflow, allowing implementers and support personnel to identify why specific expenditure items were rejected during the cost distribution and GL interface process. The exception classification is keyed on the code COST_EXCP, which is passed to PA_EXCEPTION_REASONS_PUB.GET_EXCEPTION_TEXT to obtain translated exception descriptions.

Underlying Base Objects

The view is defined over a join of several core Oracle Projects and Oracle General Ledger objects. The principal transactional source is PA_EXPENDITURE_ITEMS_ALL, aliased EI, which supplies the expenditure item detail. It is joined to PA_EXPENDITURES_ALL (EXP), which provides the expenditure batch and incurred-by person, and to PA_PROJECTS_ALL (PP) and PA_TASKS (TT) for project and task naming. Organization name resolution is handled by the PA_EXPENDITURES_UTILS.GetOrgTlName function.

Additional joins include GL_PERIOD_STATUSES (PRD), which supplies the period name, and PA_IMPLEMENTATIONS_ALL (IMP), which contributes the same-PA-GL-period flag and set of books identifier. Person information is obtained from PER_PEOPLE_F (EMP). The view also references PA_COST_DISTRIBUTION_LINES_ALL, PA_PERIODS_ALL, and PO_VENDORS, and depends on the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages for person name and security handling. The heavy dependency on packaged functions means the view is not a simple relational projection; row-level exception text is computed dynamically at query time.

Key Columns

• PROJECT_ID / NAME and TASK_ID / TASK_NAME — identify the project and task owning the failed expenditure item.
• EXPENDITURE_ID / EXPENDITURE_ITEM_ID — the expenditure and item-level keys used for drill-down.
• EXPENDITURE_ITEM_DATE and EXPENDITURE_TYPE — the date and classification of the item.
• EXCEPTION_CODE — derived as NO_COST_DIST when COST_DIST_REJECTION_CODE is null, otherwise the rejection code itself.
• EXCEPTION_REASON and CORRECTIVE_ACTION — resolved via PA_EXCEPTION_REASONS_PUB.GET_EXCEPTION_TEXT and PA_LOOKUPS; fall back to the lookup meaning when the function returns 'Undefined'.
• PERIOD_NAME — from GL_PERIOD_STATUSES, indicating the accounting period.
• Organization columns — the distribution organization ID (nvl of ORGANIZATION_ID and OVERRIDE_TO_ORGANIZATION_ID) and its translated name.
• Amount and quantity columns — QUANTITY plus raw and burdened costs and currency codes at denominated, accounted, and project currency levels (DENOM_*, ACCT_*, PROJECT_CURRENCY_CODE).
• ORG_ID, SET_OF_BOOKS_ID, same_pa_gl_period — multi-org and ledger context.
• person_name / person_id and expenditure_batch — incurring person and expenditure group.

Common Use Cases and Queries

The primary use case is diagnosing uncosted expenditures before or after the PRC (cost distribution) process. Users typically filter by project, by period, or by exception code to isolate items with no cost distribution.

SELECT project_id, name, task_name, expenditure_item_id,
       exception_code, exception_reason, corrective_action,
       period_name, quantity, acct_raw_cost
FROM   apps.pa_gl_uncost_except_sum_v
WHERE  project_id = :p_project_id
AND    exception_code = 'NO_COST_DIST';

A second pattern groups exceptions to assess volume and root cause across a period:

SELECT exception_code, exception_reason, COUNT(*)
FROM   apps.pa_gl_uncost_except_sum_v
WHERE  period_name = :p_period
GROUP  BY exception_code, exception_reason
ORDER  BY 3 DESC;

Because the view invokes PA_EXCEPTION_REASONS_PUB and PA_EXPENDITURES_UTILS per row, queries against large data sets can be costly; restricting by project, period, or org is recommended. The view is best treated as a read-only diagnostic and reporting object, not as a source for transactional updates, and the exception text is subject to the language and lookup configuration of the environment.