Results for “revenue_writeoff”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PJI_AC_XBS_ACCUM_F is a table owned by the PJI schema within Oracle E-Business Suite, historically associated with the Project Intelligence (PJI) product. As noted in the ETRM metadata, the PJI product is flagged as Obsolete, meaning the table is retained primarily for backward compatibility and historical reporting rather than active development. The table's documented purpose is to store summarized booking and backlog activity measures for project performance, aggregated across work breakdown structure (WBS) and program hierarchies.

Functionally, PJI_AC_XBS_ACCUM_F acts as a pre-aggregated fact store. Rather than computing booking, funding, revenue, and backlog metrics on demand from transactional tables such as PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, and the AR subledger, PJI summarizes these measures by time period, organization, and hierarchy level. This design supports the performance-oriented reporting characteristic of Project Intelligence, allowing dashboards and analytical queries to scan a compact, denormalized fact table instead of joining across many high-volume transactional sources.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is link. This is a modeling suggestion: the table's four documented foreign keys each reference independent business entities — organizations, projects, and project elements — and the table records measure-bearing relationships among them. In practice, however, the table blends link semantics with satellite-like measure columns, since it carries a large body of numeric facts (63 documented columns) rather than pure relationship metadata.

Key Information Stored

The table contains 63 documented columns. The most significant fall into three groups: keys, dimensional context, and accumulated financial measures.

No surrogate primary key or unique index is documented in the supplied metadata; the logical business key is most plausibly the combination of PROJECT_ID, PROJECT_ELEMENT_ID, TIME_ID, PROJECT_ORG_ID, and the rollup flags. Audit columns include LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The primary use case is analytical reporting on project performance and backlog. A typical query aggregates metrics by project and period:

  • SELECT PROJECT_ID, TIME_ID, SUM(REVENUE), SUM(ACTIVE_BACKLOG) FROM PJI_AC_XBS_ACCUM_F GROUP BY PROJECT_ID, TIME_ID;
  • Backlog aging and risk reporting filtered by WBS_ROLLUP_FLAG or PRG_ROLLUP_FLAG.
  • Funding accumulation analysis using INITIAL_FUNDING_AMOUNT and ADDITIONAL_FUNDING_AMOUNT by organization.
  • Receivables and unbilled analysis using AR_AMOUNT_DUE and UNBILLED_RECEIVABLES.

Because the table is pre-aggregated, it is generally queried directly rather than joined to transactional sources.

Related Objects

  • PA_PROJECTS_ALL — joined on PROJECT_ID.
  • PA_PROJ_ELEMENTS — joined on PROJECT_ELEMENT_ID.
  • HR_ALL_ORGANIZATION_UNITS — joined on PROJECT_ORG_ID and PROJECT_ORGANIZATION_ID.
  • PJI reporting views and concurrent programs that populate and consume the accumulated measures.