Search Results expenditure_org




Overview
Explore in AI Chat

Overview

PA_DEDUCTION_SUMMARY_V is an APPS-owned reporting view in the Oracle E-Business Suite Projects (PA) module. It exposes summarized burden deduction information at the intersection of a project task, an expenditure organization, and an expenditure type, and it is commonly used when analyzing unpaid or unprocessed burden deductions against burdened expenditure. The view carries a VALID status in both EBS 12.1.1 and 12.2.2. Its primary role is to support inquiry and reporting on deduction balances: it presents the deductions recorded for a given task/organization/expenditure type combination, separates those deductions into processed and unprocessed portions, and computes the corresponding burden cost of detail expenditure items. Because the view exposes EXPENDITURE_ORG and EXPENDITURE_ORG_ID as first-class columns, it is the natural access point for report queries that filter or group by expenditure organization, which is the term the user searched for.

Underlying Base Objects

The view is defined over a single documented base object, PA_DEDUCTION_SUMMARY_BASE_V, itself a view, aliased as V in the view text. It is therefore a thin projection and enrichment layer rather than a table-joining construct in its own right. Two additional objects are documented as referenced: the synonyms PA_EXPENDITURES_ALL and PA_EXPENDITURE_ITEMS_ALL, which resolve to the expenditure and expenditure item tables in the APPS schema. The view text uses these two objects only inside a scalar subquery that calculates PF_EXP_AMOUNT. The remaining columns are passed through from the base view. Column projection is explicit and includes CI_ID, TASK_ID, PROJECT_ID, TASK_NUMBER, EXPENDITURE_ORG, EXPENDITURE_TYPE, EXPENDITURE_ORG_ID, PF_EXP_AMOUNT, PFC_DEDUCTIONS_AMOUNT, PFC_UNPROC_DED_AMOUNT, and PFC_PROC_DED_AMOUNT.

Key Columns

  • CI_ID – Identifier of the capital interest or burden-related construct associated with the summarized deduction row.
  • PROJECT_ID / TASK_ID / TASK_NUMBER – Project and task context; TASK_NUMBER supplies the human-readable task identifier.
  • EXPENDITURE_ORG – The expenditure organization name, the primary search and reporting attribute for organization-level analysis.
  • EXPENDITURE_ORG_ID – The numeric organization identifier. It drives the burden cost subquery, which joins expenditure items to expenditures where the override-to-organization, or the incurred-by-organization when no override exists, equals this value.
  • EXPENDITURE_TYPE – Expenditure type, matched exactly against the expenditure item expenditure type in the subquery.
  • PF_EXP_AMOUNT – The total burden cost for the task, organization, and expenditure type, computed as NVL(SUM(BURDEN_COST),0); returns zero when no matching items exist.
  • PFC_DEDUCTIONS_AMOUNT – Total deductions recorded for the summarized combination.
  • PFC_PROC_DED_AMOUNT – The processed portion of those deductions.
  • PFC_UNPROC_DED_AMOUNT – The unprocessed remainder, derived arithmetically as PFC_DEDUCTIONS_AMOUNT minus PFC_PROC_DED_AMOUNT.

Common Use Cases and Queries

Typical scenarios include reconciling deduction balances by expenditure organization, isolating unprocessed deductions ahead of processing runs, and comparing deduction amounts to the burden cost of underlying expenditure items. A representative query filtering on the searched attribute is:

SELECT project_id, task_number, expenditure_org, expenditure_type, pfc_deductions_amount, pfc_proc_ded_amount, pfc_unproc_ded_amount, pf_exp_amount FROM apps.pa_deduction_summary_v WHERE expenditure_org = :org ORDER BY project_id, task_number, expenditure_type;

Aggregated reporting by organization and expenditure type follows naturally, for example SUM(pfc_unproc_ded_amount) grouped by expenditure_org and expenditure_type to highlight outstanding deduction exposure. Because PF_EXP_AMOUNT is a scalar subquery evaluated per output row, queries returning large result sets should be filtered on project, task, or organization to control cost. Deduction amounts represent the base view's summarized figures, so no double counting occurs across the projection layer.