Search Results pending_projfunc_inv_amount




Overview
Explore in AI Chat

Overview

APPS.PA_PROJ_BILLING_STATUS_VIEW is a project-level billing status aggregate view in Oracle E-Business Suite, owned by the APPS schema. It presents billing, revenue, invoice, retention, and next-event information consolidated to one row per project. The view is defined on top of PA_PROJ_BILLING_DETAIL_VIEW, the detail-level billing view, and collapses that detail through a GROUP BY PROJECT_ID clause so that reporting tools and integration programs can retrieve a single summarized billing status record for each project.

The view is widely used by Oracle Projects reporting, project billing dashboards, and downstream integrations that need billing-to-date and revenue-to-date positions without traversing the transaction-level detail. Because it aggregates from a project-level billing detail view, it sits near the top of the Projects billing data model and is intended for read-only consumption.

Underlying Base Objects

The view text is defined over a single database object, PA_PROJ_BILLING_DETAIL_VIEW, which supplies all projected columns referenced in the SELECT list. Documented referenced base objects at the package level include PA_BILLING_CYCLES_PKG, PA_PROJECT_UTILS, and PA_PROJ_BILLING_DETAIL_VIEW. The first two are PL/SQL packages that participate in the billing calculation chain used to populate the detail view, while PA_PROJ_BILLING_DETAIL_VIEW is the direct FROM object of this view.

  • PA_PROJ_BILLING_DETAIL_VIEW — direct source; supplies billing method, project attributes, invoice, revenue, retention, and project functional currency amounts at detail level.
  • PA_BILLING_CYCLES_PKG — package involved in billing cycle logic that feeds the underlying billing detail data.
  • PA_PROJECT_UTILS — utility package supporting project-level derived values.

The aggregation applies MAX() to descriptive and flag columns, SUM() to financial measures, and DECODE() to retention handling based on the RETN_ACCOUNTING_FLAG, as shown in the documented view text.

Key Columns

All measures are grouped by PROJECT_ID. In Oracle Projects, project functional currency amounts are prefixed PROJFUNC_, while the corresponding project currency and global currency amounts appear without that prefix or with alternatives. Key columns include:

Common Use Cases and Queries

Typical uses include project billing status inquiries, revenue versus invoice variance reporting, unbilled receivable analysis, and extract programs for financial reconciliation. The following sample retrieves billing status for a project, highlighting the project functional currency revenue column referenced by the search term.

SELECT project_number,
       project_name,
       billing_method,
       projfunc_revenue_amount,
       projfunc_invoice_amount,
       projfunc_revenue_amount - projfunc_total_invoiced_amount
         AS projfunc_unbilled
FROM   apps.pa_proj_billing_status_view
WHERE  project_id = :p_project_id;

A second pattern lists projects with revenue exceeding invoices, useful for unbilled revenue review:

SELECT project_id,
       project_number,
       revenue_amount,
       invoice_amount,
       revenue_amount - invoice_amount AS unbilled_amount
FROM   apps.pa_proj_billing_status_view
WHERE  revenue_amount - invoice_amount > 0
ORDER  BY unbilled_amount DESC;

Because the view aggregates at PROJECT_ID, results are one row per project. Reports requiring task-level or event-level breakdown should query PA_PROJ_BILLING_DETAIL_VIEW instead.