Search Results pfc_proc_ded_amount




Overview
Explore in AI Chat

Overview

APPS.PA_DEDUCTION_SUMMARY_V is a reporting and integration view in Oracle E-Business Suite Projects (Oracle Projects / Project Costing) that summarizes deduction amounts associated with burden cost processing at the combination of task and expenditure type level. It is defined in the APPS schema and is documented as part of the Oracle EBS 12.1.1 / 12.2.2 technical reference set (ETRM). The view consolidates two distinct concepts in Project Costing: the deductions that have been identified or assigned through the burden structure (PFC_DEDUCTIONS_AMOUNT) and the portion of those deductions that has already been processed (PFC_PROC_DED_AMOUNT).

Because burden processing in Oracle Projects relies on the relationship between expenditures, expenditure items, and deduction definitions, this view presents a resolved summary rather than raw transactional detail. It is commonly surfaced in burden and cost analysis reports, reconciliation queries, and downstream integrations that need visibility into how much of the expected deduction has been applied and how much remains unprocessed. The naming prefix "PFC" refers to the burden-related Programmatic/Functional Costing elements associated with deduction processing.

Underlying Base Objects

The documented view definition references the following objects:

The view is essentially a wrapper over PA_DEDUCTION_SUMMARY_BASE_V that augments each row with a computed expenditure amount (PF_EXP_AMOUNT) and a derived unprocessed deduction amount. The correlated subquery matches expenditure items to the base view by organization, task, and expenditure type, resolving the organization through NVL(EI.OVERRIDE_TO_ORGANIZATION_ID, E.INCURRED_BY_ORGANIZATION_ID).

Key Columns

  • CI_ID — identifier of the cost/collection item context for the deduction row.
  • TASK_ID / PROJECT_ID — the project and task to which the deduction summary applies.
  • TASK_NUMBER — the user-facing task number for reporting.
  • EXPENDITURE_ORG / EXPENDITURE_ORG_ID — the expenditure organization (name and identifier) grouping the deduction.
  • EXPENDITURE_TYPE — the expenditure type used to classify the deduction.
  • PF_EXP_AMOUNT — the summed burden cost of matching expenditure items, computed via the correlated subquery with NVL(...,0).
  • PFC_DEDUCTIONS_AMOUNT — the total deduction amount defined or expected at this task/expenditure type/organization combination.
  • PFC_PROC_DED_AMOUNT — the amount of the deduction that has been processed. This is the column most directly associated with the searched term "pfc_proc_ded_amount".
  • PFC_UNPROC_DED_AMOUNT — a derived column computed as PFC_DEDUCTIONS_AMOUNT minus PFC_PROC_DED_AMOUNT, representing the remaining unprocessed deduction.

Common Use Cases and Queries

Typical usage focuses on reconciliation between total deductions and processed deductions, and on identifying residual unprocessed amounts by task and expenditure type.

To find rows where deductions remain unprocessed:

  • SELECT TASK_NUMBER, EXPENDITURE_TYPE, PFC_DEDUCTIONS_AMOUNT, PFC_PROC_DED_AMOUNT, PFC_UNPROC_DED_AMOUNT FROM APPS.PA_DEDUCTION_SUMMARY_V WHERE PFC_UNPROC_DED_AMOUNT <> 0;

To reconcile processed deduction against computed burden cost for a given project:

  • SELECT TASK_NUMBER, EXPENDITURE_TYPE, PF_EXP_AMOUNT, PFC_PROC_DED_AMOUNT FROM APPS.PA_DEDUCTION_SUMMARY_V WHERE PROJECT_ID = :project_id;

Because PFC_UNPROC_DED_AMOUNT is a computed expression, it should be referenced directly rather than recomputed in application logic. The view is read-only and is intended for query and reporting purposes; it should not be used as a target for DML. When performance is a concern, filters on TASK_ID, PROJECT_ID, and EXPENDITURE_ORG_ID are most selective because they align with the join keys used in the correlated subquery.