Search Results invproc_allocated_amount




Overview
Explore in AI Chat

Overview

The view PA_PROJECT_FUNDINGS_AMG_V is an Oracle E-Business Suite (EBS) Projects (PA) object owned by the APPS schema. It is based on the PA_PROJECT_FUNDINGS table and stores incremental allocations of agreement funds to projects or top tasks. In the EBS funding model, funding is a prerequisite for a contract project: a project must be funded before it can accrue revenue and generate invoices. Indirect or capitalized projects follow different funding rules managed elsewhere in the application.

The view participates in the agreements and project funding integration flow, exposing the columns required by the agreements (AMG) funding process. Rather than presenting new business logic, it provides a stable, denormalized read surface over PA_PROJECT_FUNDINGS, including the multi-currency amounts (project, project functional, invoice processing, and revenue processing) that surround each funding allocation. Reporting and integration components query this view to obtain allocation amounts, exchange rates, funding categories, and summarized-funding status without directly accessing the base table.

Underlying Base Objects

According to the documented view metadata for ETRM 12.2.2, PA_PROJECT_FUNDINGS_AMG_V is defined over the base object PA_PROJECT_FUNDINGS, accessed through the synonym of the same name in the APPS schema. The view's select list maps essentially the full column set of PA_PROJECT_FUNDINGS, which is consistent with a pass-through construct intended to isolate consumers from direct table access while preserving the table's transactional columns.

Because it is a simple view over a single base table, the view inherits the table's row-level granularity: one row per funding allocation to a project or top task. It does not join to agreement, project, or task tables; descriptive attributes such as project number or agreement name must be obtained by joining the view to PA_PROJECTS, PA_AGREEMENTS, or related objects on the respective keys.

Key Columns

Common Use Cases and Queries

Typical usage includes reconciling funded versus invoiced amounts, auditing summarized funding, and extracting allocation data for external reporting. A query filtering on the summarization flag, for example:

  • SELECT PROJECT_FUNDING_ID, PROJECT_ID, TASK_ID, AGREEMENT_ID, ALLOCATED_AMOUNT, PJI_SUMMARIZED_FLAG FROM APPS.PA_PROJECT_FUNDINGS_AMG_V WHERE PJI_SUMMARIZED_FLAG = 'Y';
  • Listing unsummarized funding awaiting the PJI summarization program: SELECT * FROM APPS.PA_PROJECT_FUNDINGS_AMG_V WHERE PJI_SUMMARIZED_FLAG = 'N' OR PJI_SUMMARIZED_FLAG IS NULL;
  • Totaling funding by project and joining to PA_PROJECTS for descriptive attributes: SELECT p.segment1, SUM(f.ALLOCATED_AMOUNT) FROM APPS.PA_PROJECT_FUNDINGS_AMG_V f, APPS.PA_PROJECTS p WHERE f.PROJECT_ID = p.PROJECT_ID GROUP BY p.segment1;
  • Reviewing backlog and invoiced balances across currency contexts using FUNDING_BACKLOG_AMOUNT and FUNDING_INV_APPLIED_AMOUNT.

Because the view is read-only in practice, all maintenance is performed against the base PA_PROJECT_FUNDINGS table through supported funding APIs or the Projects forms.