Search Results pa_proj_billing_status_view




Overview
Explore in AI Chat

Overview

PA_PROJ_BILLING_STATUS_VIEW is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides in the Projects (PA) product family and presents the billing status of projects in a single consolidated row per project. The view is the data source for the MGT: Project Billing Status report, and its column set mirrors the measures printed by that report. Because it aggregates the transactional billing detail held in PA_PROJ_BILLING_DETAIL_VIEW, it allows report writers, FSG-style inquiries, and external integrations to retrieve project-level billing health without traversing invoice, revenue, retention, and event records individually.

The view is documented as VALID and is exposed to reporting tools such as BI Publisher, Oracle Reports, and ad hoc SQL clients. Its principal value is the comparison of revenue recognized against amounts invoiced, which yields the unbilled receivable position for each project.

Underlying Base Objects

The documented view text defines PA_PROJ_BILLING_STATUS_VIEW as a GROUP BY PROJECT_ID aggregate query over PA_PROJ_BILLING_DETAIL_VIEW. Because it performs only aggregation, the view does not itself join base tables; all denormalization is performed one layer down in the detail view, which in turn derives from PA billing and revenue entities. The ETRM metadata further records the following referenced base objects:

  • PA_PROJ_BILLING_DETAIL_VIEW (VIEW) — the sole row source, supplying all project billing, revenue, retention, and event measures.
  • PA_BILLING_CYCLES_PKG (PACKAGE) — billing cycle logic used to derive next billing date and release behavior.
  • PA_PROJECT_UTILS (PACKAGE) — shared project utility functions used during derivation.

Aggregation rules are significant: MAX is applied to descriptive and date attributes such as BILLING_METHOD, PROJECT_NUMBER, PROJECT_NAME, and the last released invoice attributes, while SUM is applied to monetary and duration measures. NVL wrappers convert null measures to zero before summation. The retention flag RETN_ACCOUNTING_FLAG determines whether unbilled retention is reported within the unbilled receivable amount or separately, using a DECODE against the maximum flag value.

Key Columns

Common Use Cases and Queries

The view supports unbilled receivable analysis, billing cycle monitoring, and reconciliation of the MGT: Project Billing Status report. Typical usage identifies projects with growing unbilled balances or delayed invoice release.

SELECT project_number, project_name, billing_method,
       last_released_invoice_num, last_released_invoice_date,
       days_since_last_release, next_billing_date,
       revenue_amount, invoice_amount, unbilled_receivable_amount
FROM   apps.pa_proj_billing_status_view
WHERE  unbilled_receivable_amount > 0
ORDER  BY unbilled_receivable_amount DESC;
SELECT project_id, project_number,
       projfunc_revenue_amount,
       projfunc_invoice_amount,
       projfunc_ubr_amount,
       projfunc_unbilled_retention
FROM   apps.pa_proj_billing_status_view
WHERE  days_since_last_release > 30;

Because aggregation occurs on PROJECT_ID only, consumers must not expect task-level granularity; task-level reporting requires querying PA_PROJ_BILLING_DETAIL_VIEW directly.