Search Results expenditure_batch

Overview

PA_GL_UNCOST_EXCEPT_SUM_V is a Projects (PA) module reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to identify expenditure items whose cost distribution lines prevent a Projects period from being closed or swept to the General Ledger. When the PRC: Interface Usage and Cost to GL process, or the period-close exception report, encounters expenditure items that could not be distributed to GL, this view surfaces the offending rows together with a classified exception code and a human-readable reason.

The view is the presentation layer for the "no_cost_dist" condition — the user's search term. In the view text this is expressed through a DECODE on EI.COST_DIST_REJECTION_CODE: when the code is NULL the view renders the literal string NO_COST_DIST, otherwise it passes the stored rejection code through as EXCEPTION_CODE. This makes the view the primary diagnostic query for un-costed or unreleased expenditure items during period close.

Underlying Base Objects

The view is defined over a join of the core Projects transaction tables and several supporting lookups and security objects. The documented referenced base objects are:

• PA_EXPENDITURE_ITEMS_ALL — the driving table (aliased EI), supplying expenditure item date, quantity, currencies and the COST_DIST_REJECTION_CODE.
• PA_EXPENDITURES_ALL (EXP) — the parent expenditure batch header, supplying the incurred-by person and expenditure group.
• PA_COST_DISTRIBUTION_LINES_ALL — the cost distribution lines whose absence or rejection triggers the exception.
• PA_PROJECTS_ALL (PP), PA_TASKS (TT), PA_PERIODS_ALL (PRD), PA_IMPLEMENTATIONS_ALL (IMP) — project name, task name, period name, and the SAME_PA_GL_PERIOD / SET_OF_BOOKS_ID context.
• GL_PERIOD_STATUSES — used to compare PA and GL period status.
• PER_PEOPLE_F (EMP) and the HR_GENERAL, HR_PERSON_NAME, HR_SECURITY packages — resolve the person name subject to Row Level Security.
• PO_VENDORS — supplier columns, exposed here as NULL placeholders.
• PA_LOOKUPS and the packages PA_EXCEPTION_REASONS_PUB and PA_EXPENDITURES_UTILS — provide exception reason text, corrective action text, and organization name translation via GETORGTLNAME.

Key Columns

• EXCEPTION_CODE — the decoded rejection code; returns NO_COST_DIST when COST_DIST_REJECTION_CODE is NULL.
• EXCEPTION_REASON / CORRECTIVE_ACTION — subquery results driven by PA_EXCEPTION_REASONS_PUB.GET_EXCEPTION_TEXT for lookup type UNCOST_EXCP, defaulting to the lookup MEANING.
• PROJECT_ID / NAME, TASK_ID / TASK_NAME — the project and task context of the failed item.
• EXPENDITURE_ID, EXPENDITURE_ITEM_ID, EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE — unique identification of the offending transaction.
• PERIOD_NAME, SAME_PA_GL_PERIOD, SET_OF_BOOKS_ID — the accounting period and ledger context.
• DENOM_RAW_COST / DENOM_BURDENED_COST and the ACCT_ and PROJECT_ currency equivalents — the amounts blocked from distribution.
• PERSON_NAME / PERSON_ID, EXPENDITURE_BATCH — the incurring person and expenditure group.
• ORG_ID — the operating unit, supporting multi-org security filtering.

Common Use Cases and Queries

The principal use is period-close troubleshooting: identifying which expenditure items are blocking a Projects period from being accounted. Typical query:

SELECT project_id, name, task_name, expenditure_item_id,
       expenditure_item_date, period_name, exception_code,
       exception_reason, corrective_action, denom_raw_cost
FROM   apps.pa_gl_uncost_except_sum_v
WHERE  period_name = :p_period_name
ORDER  BY name, expenditure_item_date;

A narrower query filters specifically for the missing-distribution condition:

SELECT project_id, name, expenditure_item_id, exception_code
FROM   apps.pa_gl_uncost_except_sum_v
WHERE  exception_code = 'NO_COST_DIST';

Because the view includes ORG_ID and resolves person names through HR security, it is also suitable for operating-unit restricted reporting and for reconciliation dashboards that track unaccounted distributions by project, task, or expenditure batch before re-running the PRC: Interface Usage and Cost to GL concurrent program.