Search Results revaluation_through_date




Overview
Explore in AI Chat

Overview

APPS.PA_PROJECT_FUNDINGS_AMG_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes project funding records in a multi-currency, multi-process context. It is designed to present funding allocation amounts across the four transaction currency contexts used by Oracle Projects: funding currency, project currency, project functional (PROJFUNC) currency, and invoice processing (INVPROC) currency, together with revenue processing (REVPROC) currency. This makes the view particularly valuable for financial reporting, reconciliation, and downstream integration where funding must be analyzed from the perspective of each process currency rather than a single ledger currency.

The view is defined in the APPS schema and is typically consumed by Oracle Projects reporting components, extracts, and custom integrations that need a denormalized, currency-conversion-ready representation of funding data without joining to the underlying base table directly.

Underlying Base Objects

The view is defined over a single documented base object:

  • PA_PROJECT_FUNDINGS (referenced as a SYNONYM in the ETRM metadata) — the primary project funding table that stores funding records associated with projects, tasks, agreements, and budget types.

The view selects a broad set of columns from PA_PROJECT_FUNDINGS, aliasing PA_PROJECT_FUNDINGS_PROJECT_ID as a leading column. Because it is a straight projection (no joins, unions, or aggregations), the view performs as a simple filtered/selected read over the base table and inherits its indexing and partitioning characteristics. The presence of the AMG suffix historically relates to Oracle Projects' multi-currency/multi-process calculation logic that materializes allocated amounts per currency context.

Key Columns

The view exposes currency- and process-specific allocation amounts. Notable columns include:

Common Use Cases and Queries

Typical uses include funding reconciliation across currencies, revenue processing currency analysis, and feeding downstream extracts. Common patterns select by project and budget type, or focus on the revenue processing allocation amount:

  • Querying funding for a project in revenue processing currency.
  • Reconciling funding currency against project functional and invoice processing allocations.
  • Extracting funding backlog and invoice application amounts for cash and billing analysis.

Illustrative SQL:

  • SELECT PROJECT_ID, TASK_ID, BUDGET_TYPE_CODE, FUNDING_CURRENCY_CODE, REVPROC_CURRENCY_CODE, REVPROC_ALLOCATED_AMOUNT, REVPROC_EXCHANGE_RATE FROM APPS.PA_PROJECT_FUNDINGS_AMG_V WHERE PROJECT_ID = :p_project_id;
  • SELECT AGREEMENT_ID, SUM(ALLOCATED_AMOUNT), SUM(REVPROC_ALLOCATED_AMOUNT) FROM APPS.PA_PROJECT_FUNDINGS_AMG_V GROUP BY AGREEMENT_ID;
  • SELECT PROJECT_ID, FUNDING_INV_APPLIED_AMOUNT, FUNDING_INV_DUE_AMOUNT, FUNDING_BACKLOG_AMOUNT FROM APPS.PA_PROJECT_FUNDINGS_AMG_V WHERE BUDGET_TYPE_CODE = :p_budget_type;

Because the view is a direct projection of PA_PROJECT_FUNDINGS, users should apply the same security and business-group considerations that govern direct access to the base funding table.