Search Results additional_funding_count

Overview

PJI_AC_XBS_ACCUM_F_V is an APPS-owned database view within the Oracle E-Business Suite environment, historically associated with the Project Intelligence (PJI) product family. Project Intelligence was a business intelligence and analytics layer that sat over Oracle Projects and Oracle Financials, supplying pre-aggregated activity and financial measures for dashboards, ad hoc reporting, and analytic extracts. In EBS 12.1.1 and 12.2.2, the PJI product is documented as obsolete, meaning the seeded analytics functionality has been superseded by Oracle Business Intelligence Applications and related products; however, the underlying objects frequently remain present and valid in upgraded or legacy instances.

The view presents Project Intelligence numbers for activity data at the project level. It exposes a single denormalized row per combination of project, project organization, project element (WBS or task), time identifier, and currency, with numerous pre-computed amount and count measures. The presence of the UNBILLED_RECEIVABLES column is directly relevant to users searching for unbilled receivables reporting, since this view materializes that figure alongside related revenue, billing, funding, backlog, and cash measures.

Underlying Base Objects

Per the documented 12.2.2 metadata, the view is defined over a single referenced base object: PJI_AC_XBS_ACCUM_F, accessed through a synonym. PJI_AC_XBS_ACCUM_F is the Project Intelligence accumulation fact table that stores activity-level accumulations at the WBS (project element) rollup grain. The view is a thin projection with an explicit column list rather than a multi-table join; it does not add filtering or aggregation logic. Its principal structural transformation is the truncation of the CUSTOM1 through CUSTOM15 descriptive attribute set and the substitution of CAST(NULL AS NUMBER) for CUSTOM16 through CUSTOM30, which standardizes the shape of the custom column block for downstream consumers.

Key Columns

• PROJECT_ID, PROJECT_ORG_ID, PROJECT_ORGANIZATION_ID — Project and organization identifiers establishing the reporting context.
• PROJECT_ELEMENT_ID — The WBS or task element to which the accumulated measures apply.
• TIME_ID, PERIOD_TYPE_ID, CALENDAR_TYPE — Time dimension keys and calendar classification for period-based reporting.
• WBS_ROLLUP_FLAG, PRG_ROLLUP_FLAG — Indicate whether the row represents a WBS-level or program-level rollup, preventing double counting.
• CURR_RECORD_TYPE_ID, CURRENCY_CODE — Record type classification and the currency of the stored amounts.
• REVENUE — Recognized revenue for the combination.
• UNBILLED_RECEIVABLES — Revenue recognized but not yet billed to the customer, a core Project Revenue/AR reconciliation measure.
• UNEARNED_REVENUE — Billings in excess of recognized revenue.
• AR_INVOICE_AMOUNT, AR_INVOICE_COUNT, AR_CREDIT_MEMO_AMOUNT, AR_CASH_APPLIED_AMOUNT, AR_INVOICE_WRITE_OFF_AMOUNT — Accounts Receivable transaction aggregates.
• AR_AMOUNT_DUE, AR_AMOUNT_OVERDUE, AR_UNAPPR_INVOICE_AMOUNT, AR_APPR_INVOICE_AMOUNT — Receivables aging and approval status measures.
• INITIAL_FUNDING_AMOUNT, ADDITIONAL_FUNDING_AMOUNT, CANCELLED_FUNDING_AMOUNT, FUNDING_ADJUSTMENT_AMOUNT and their COUNT counterparts — Funding lifecycle measures.
• DORMANT_BACKLOG_INACTIV, DORMANT_BACKLOG_START, LOST_BACKLOG, ACTIVE_BACKLOG, REVENUE_AT_RISK — Backlog and risk analytics.
• LAST_UPDATE_DATE, CREATION_DATE and audit columns plus CUSTOM1–CUSTOM30 — Standard EBS audit and extensibility attributes.

Common Use Cases and Queries

The view is typically queried for unbilled receivables analysis, revenue versus billing reconciliation, funding utilization, and backlog reporting. A representative query retrieving unbilled receivables by project and period is:

SELECT project_id, project_element_id, time_id, currency_code, revenue, unbilled_receivables FROM apps.pji_ac_xbs_accum_f_v WHERE unbilled_receivables <> 0 AND wbs_rollup_flag = 'Y' ORDER BY project_id, time_id;

Because the view carries no WHERE clause, users must supply their own filters, ordinarily restricting WBS_ROLLUP_FLAG or PRG_ROLLUP_FLAG to a single value to avoid mixing rollup levels, and constraining TIME_ID or CALENDAR_TYPE to the periods of interest. Given the obsolete status of the PJI product, organizations should confirm object validity in their environment and treat this view as a legacy data source for archival or migration reporting.