Search Results pji_fp_xbs_accum_f




Overview

The PJI_FP_XBS_ACCUM_F table is a core data repository within the Project Intelligence (PJI) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a fact table in the PJI data warehouse, designed to store aggregated performance metrics for projects. Its primary role is to support complex analytical reporting and performance dashboards by providing pre-summarized financial and commitment data across multiple organizational and project hierarchies. By accumulating measures at various levels of detail, this table enables efficient querying for project portfolio analysis, cost control, and revenue recognition reporting without requiring real-time aggregation from transactional source tables.

Key Information Stored

The table stores summarized measures categorized by several key dimensions. While the specific column list is not detailed in the provided metadata, the description and foreign key relationships indicate it contains a combination of dimension foreign keys and numeric fact columns. The dimension keys typically include identifiers for the project (PROJECT_ID), work breakdown structure (WBS) via PROJECT_ELEMENT_ID, resource breakdown structure (RBS) via RBS_ELEMENT_ID, budget plan (PLAN_VERSION_ID), and organization (PROJECT_ORGANIZATION_ID, PROJECT_ORG_ID). The factual measures stored are summarized values for cost, revenue, and commitments. These are likely period-based (e.g., period-to-date, quarter-to-date, year-to-date) and may include planned, actual, and forecast amounts, forming the basis for variance analysis and performance tracking.

Common Use Cases and Queries

This table is central to Project Intelligence reporting. Common use cases include analyzing project cost and revenue performance against budgets, tracking commitments against funding, and generating roll-up reports across program or organizational hierarchies. A typical analytical query would join this fact table to its dimension tables to retrieve meaningful descriptions. For example, to report actual costs by project and task, a query might join to PA_PROJECTS_ALL and PA_PROJ_ELEMENTS. Performance dashboards often query this table to calculate key metrics like Cost Variance (CV) or Schedule Performance Index (SPI) when integrated with earned value data. Data is typically accessed via pre-built PJI reports, Oracle Business Intelligence (OBIEE) analyses, or custom SQL extracts for enterprise reporting systems.

Related Objects

The PJI_FP_XBS_ACCUM_F table is integrally connected to several foundational EBS tables via foreign key relationships, as documented. These relationships define its dimensional context:

  • PA_BUDGET_VERSIONS: Joined via PLAN_VERSION_ID to associate accumulated measures with a specific project budget version.
  • PA_RBS_ELEMENTS: Joined via RBS_ELEMENT_ID to break down measures by the Resource Breakdown Structure.
  • HR_ALL_ORGANIZATION_UNITS: Joined via PROJECT_ORGANIZATION_ID and PROJECT_ORG_ID to provide organizational hierarchy context.
  • PA_PROJ_ELEMENTS: Joined via PROJECT_ELEMENT_ID to break down measures by the Work Breakdown Structure (task).
  • PA_PROJECTS_ALL: Joined via PROJECT_ID, the primary project master record.

This table is also a primary source for various PJI summary and cube views, which further aggregate data for end-user consumption.