Results for “projfunc_total_billed”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_SUMMARY_PROJECT_RETN is a Projects (PA) module table in the Oracle E-Business Suite that stores summary retention amounts calculated from the retention and retention billing setup defined at the project or top task level. Rather than holding every individual retention transaction, the table aggregates the detailed retention records into one summarized row per project, task, and agreement combination. This makes it the reporting-friendly counterpart to the transaction-level retention tables used during billing and revenue processing.

Retention represents amounts withheld by a customer from progress payments and released later according to contract terms. In Oracle Projects, retention is driven by retention terms attached to the project or top task and by retention billing configuration. PA_SUMMARY_PROJECT_RETN captures the rolled-up retained, billed, and write-off totals so that users can review a project's retention position without scanning detailed records.

From a data-modeling perspective, the table exhibits link characteristics. It sits at the intersection of several master entities — project, task, agreement, and customer — and its primary key is the composite of those business identifiers rather than a single surrogate. A heuristic Data Vault classification would therefore suggest treating it as a link (or a link with descriptive satellite attributes), since the retention measures are contextual to the combination of referenced dimensions. This classification is a modeling suggestion only; the physical table remains a standard Oracle EBS denormalized summary object.

Key Information Stored

The table contains 29 documented columns. The most significant are the key and measure columns described below.

• PROJECT_ID — identifies the project to which the summarized retention belongs; part of the unique business key.
• TASK_ID — identifies the task (typically a top task) associated with the retention summary; part of the unique business key.
• AGREEMENT_ID — identifies the funding agreement under which retention terms apply; part of the unique business key.
• CUSTOMER_ID — the customer account associated with the retention amounts.
• TOTAL_RETAINED, TOTAL_BILLED, TOTAL_WRITEOFF — aggregate retention measures in the invoice processing currency.
• INVPROC_CURRENCY_CODE — currency of the invoice processing amounts.
• PROJFUNC_CURRENCY_CODE — currency of the project functional amounts.
• PROJFUNC_TOTAL_RETAINED, PROJFUNC_TOTAL_BILLED, PROJFUNC_TOTAL_WRITEOFF — the same retention measures expressed in project functional currency.
• PROJECT_CURRENCY_CODE and the PROJECT_TOTAL_* columns — retention amounts in project currency.
• FUNDING_CURRENCY_CODE and the FUNDING_TOTAL_* columns — retention amounts in funding currency.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and audit lineage indicating which process populated the row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

The unique index PA_SUMMARY_PROJECT_RETN_U1 covers PROJECT_ID, TASK_ID, and AGREEMENT_ID, confirming this triplet as the business-key candidate. The table does not expose a single surrogate primary-key column in the documented metadata; the composite key serves that purpose.

Common Use Cases and Queries

Typical uses include retention position reporting by project, reconciliation of summarized retention totals back to detailed retention transactions, and multi-currency analysis across invoice processing, project functional, project, and funding currencies.

A representative query joining the summary to project and task masters:

• Select r.project_id, p.project_number, r.task_id, r.total_retained, r.total_billed, r.total_writeoff from PA_SUMMARY_PROJECT_RETN r, PA_PROJECTS_ALL p where r.project_id = p.project_id and r.total_retained > 0.
• Group by customer to review retention by CUSTOMER_ID across all agreements.
• Compare PROJFUNC_TOTAL_RETAINED against PROJECT_TOTAL_RETAINED and FUNDING_TOTAL_RETAINED to validate currency conversion behavior.
• Filter by REQUEST_ID to identify rows produced by a specific concurrent run.

Because the table is a summary, it is well suited to dashboard and subledger-style reporting, while drill-through to detail should reference the underlying retention transaction tables.

Related Objects

• PA_PROJECTS_ALL — joined on PROJECT_ID; provides project attributes and project number.
• PA_TASKS — joined on TASK_ID; supplies task name and hierarchy context.
• PA_AGREEMENTS_ALL — joined on AGREEMENT_ID; defines the funding agreement.
• HZ_CUST_ACCOUNTS — joined on CUSTOMER_ID; identifies the customer account.
• FND_CURRENCIES — referenced four times via PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE, FUNDING_CURRENCY_CODE, and INVPROC_CURRENCY_CODE for currency descriptions.
• Oracle Projects billing and retention processing programs — populate these summary rows from detailed retention records during retention calculation and billing runs.