Search Results pa_proj_unbilled_base_view




Overview
Explore in AI Chat

Overview

PA_PROJ_UNBILLED_BASE_VIEW is a standard Oracle EBS Projects (PA) base view owned by the APPS schema. It consolidates project-level unbilled amounts derived from detail transactions, providing a single aggregated row per project. The view is part of the unbilled receivables reporting layer and serves as a foundational query source for concurrent programs, Oracle Business Intelligence (OBIEE) extracts, and custom reporting that needs to quantify work performed but not yet invoiced. Because the underlying transactions include both expenditure items and events, the view captures two distinct unbilled streams: billable expenditures that have not been swept into a draft invoice, and standalone billable events that have not been invoiced. The view is marked VALID and uses a UNION to merge these streams into a common column layout, making it suitable for consumption by parent views or downstream calculations that also consider billed and revenue amounts.

Underlying Base Objects

The view is defined over five base objects, all of which are synonyms referencing the PA transactional tables:

Key Columns

Common Use Cases and Queries

Typical scenarios include unbilled receivables dashboards, month-end project accrual reconciliations, and feeds into revenue recognition processes.

To list total unbilled amounts per project:

  • SELECT project_id, unbilled_item_amount, unbilled_event_amount FROM pa_proj_unbilled_base_view WHERE unbilled_item_amount > 0 OR unbilled_event_amount > 0;

To isolate held amounts awaiting release:

  • SELECT project_id, on_hold_amount, one_time_hold_amount, on_hold_quantity + one_time_hold_quantity AS total_holds FROM pa_proj_unbilled_base_view;

To detect multi-currency exposure on unbilled balances:

  • SELECT project_id, item_currency_count, item_currency_code, ub_item_bill_trans_amount FROM pa_proj_unbilled_base_view WHERE item_currency_count > 1;

Because the view is a base layer defined with an inline hint and a correlated subquery, joins to PA_PROJECTS for project names, or to PA_PROJECT_CUSTOMERS for customer-level rollups, are commonly applied by downstream reporting queries.