Search Results pa_summary_project_fundings

Overview

The PA_SUMMARY_PROJECT_FUNDINGS table is a core data object within the Oracle E-Business Suite Projects (PA) module, specifically in versions 12.1.1 and 12.2.2. It serves as a summary repository for financial commitments, recording the aggregated funding amounts that have been allocated from funding agreements (sources) to specific projects and their constituent tasks. Its primary role is to provide a consolidated, auditable record of project funding, enabling efficient tracking of budget availability, expenditure against funds, and overall financial control for project portfolios. This table is integral to the agreement-to-project funding process, acting as the system of record for summarized funding distributions.

Key Information Stored

The table's structure is designed to link funding sources with project work breakdown structures and store the associated financial totals. Its primary key is a composite of PROJECT_ID and AGREEMENT_ID, enforcing a unique summary record per project and agreement combination. Key columns include AGREEMENT_ID, which references the source funding document in PA_AGREEMENTS_ALL; PROJECT_ID, linking to the funded project in PA_PROJECTS_ALL; and TASK_ID, which optionally links to a specific task within the project in PA_TASKS for more granular funding allocation. The table primarily holds summary amount columns, such as the total funded amount, which represents the cumulative allocation from the agreement to that project or task. Other columns typically track the raw and burdened cost amounts, revenue amounts, and potentially the consumed and remaining funds, though the specific amount column names are derived from the module's implementation.

Common Use Cases and Queries

This table is central to financial reporting and inquiry within Projects. A primary use case is generating a summary funding report for a project, showing all agreement sources and total amounts allocated. Another critical scenario is checking available funds before incurring project costs or creating expenditure batches, often by comparing summarized funded amounts against summarized actual costs from transaction tables. A common SQL pattern involves joining this table to PA_PROJECTS_ALL and PA_AGREEMENTS_ALL to produce a readable report.

SELECT p.segment1 project_number,
       a.agreement_number,
       spf.*
FROM pa_summary_project_fundings spf,
     pa_projects_all p,
     pa_agreements_all a
WHERE spf.project_id = p.project_id
AND spf.agreement_id = a.agreement_id
AND p.segment1 = 'P12345';

It is also frequently queried in conjunction with cost detail tables (e.g., PA_COST_DISTRIBUTION_LINES_ALL) to perform fund availability checks and commitment tracking.

Related Objects

PA_SUMMARY_PROJECT_FUNDINGS has defined relationships with several key tables, as indicated by its foreign keys. Its primary dependencies are:

• PA_AGREEMENTS_ALL: The source of the funding commitment. The AGREEMENT_ID foreign key enforces that every summary record must originate from a valid agreement.
• PA_PROJECTS_ALL: The recipient of the funds. The PROJECT_ID foreign key ties the funding to a master project definition.
• PA_TASKS: Provides an optional link for task-level funding allocation via the TASK_ID foreign key.

This table is also a likely source for various project funding summary views and is central to the agreement funding workflows managed by the Projects module's APIs and user interfaces.