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.
- PROJECT_ID — foreign key to PA_PROJECTS_ALL; identifies the project whose performance is summarized.
- PROJECT_ELEMENT_ID — foreign key to PA_PROJ_ELEMENTS; identifies the WBS element or project element within the project.
- PROJECT_ORG_ID and PROJECT_ORGANIZATION_ID — both foreign keys to HR_ALL_ORGANIZATION_UNITS, providing organizational context for the summarized row.
- TIME_ID and PERIOD_TYPE_ID plus CALENDAR_TYPE — the time dimension for the aggregation, identifying the period and calendar against which measures were accumulated.
- WBS_ROLLUP_FLAG and PRG_ROLLUP_FLAG — indicators distinguishing whether the row represents WBS-level rollup or program-level rollup, which is central to the table's stated purpose.
- CURRENCY_CODE and CURR_RECORD_TYPE_ID — currency context so that amounts can be interpreted consistently.
- REVENUE and REVENUE_WRITEOFF — summarized revenue and write-off amounts.
- INITIAL_FUNDING_AMOUNT and ADDITIONAL_FUNDING_AMOUNT — funding accumulation measures (paired with corresponding count columns).
- ACTIVE_BACKLOG, DORMANT_BACKLOG_INACTIV, DORMANT_BACKLOG_START, LOST_BACKLOG, and REVENUE_AT_RISK — backlog and risk measures reflecting the booking-and-backlog focus of the table.
- AR_INVOICE_AMOUNT, UNBILLED_RECEIVABLES, UNEARNED_REVENUE, and AR_AMOUNT_DUE — accounts receivable and revenue-recognition balances.
- CUSTOM1 through CUSTOM15 — descriptor flexfields available for extensibility.
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.
-
This table stores summarized booking and backlog activity measures for project performance by work breakdown and program hierarchies
-
Table: PJI_AC_ORGO_F_MV 12.1.1
-
Table: PJI_FP_ORGO_F_MV 12.1.1
-
Table: PJI_FM_AGGR_FIN4 12.1.1
This is an intermediate summarization table.
-
Table: PJI_FM_AGGR_FIN3 12.1.1
This is an intermediate summarization table.
-
10SC Only
APPS.PA_SUMMARY_PROJECT_FUNDINGS_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ PA_AGREEMENTS_ALL·Explore PA module →
-
Table: PJI_AC_AGGR_PJP0 12.1.1
-
Table: PJI_FM_AGGR_ACT3 12.1.1
This is an intermediate summarization table.
-
View: PJI_AC_XBS_ACCUM_F_V 12.1.1
This view stores Project Intelligence numbers for activity data at the project level
APPS.PJI_AC_XBS_ACCUM_F_V·↳ PJI_AC_XBS_ACCUM_F·Explore PJI module →
-
Table: PJI_AC_ORG_F_MV 12.1.1
-
Table: PJI_AC_CLS_F_MV 12.1.1
-
Table: PJI_AC_AGGR_PJP0 12.2.2
-
Table: PJI_AC_PROJ_F 12.1.1
This table stores summarized data for booking and backlog measures at the project level for Project Intelligence
-
10SC Only
APPS.PA_SUMMARY_PROJECT_FUNDINGS_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ PA_AGREEMENTS_ALL·Explore PA module →
-
This table stores summarized booking and backlog activity measures for project performance by work breakdown and program hierarchies
-
Table: PJI_FM_AGGR_FIN5 12.1.1
This is an intermediate summarization table.
-
Table: PJI_FP_CLSO_F_MV 12.1.1
-
Table: PJI_AC_CLSO_F_MV 12.1.1
-
APPS.PA_SUM_PROJECT_FUNDINGS2_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ PA_AGREEMENTS_ALL·Explore PA module →
-
View: PJI_AC_XBS_ACCUM_F_V 12.2.2
This view stores Project Intelligence numbers for activity data at the project level
APPS.PJI_AC_XBS_ACCUM_F_V·↳ PJI_AC_XBS_ACCUM_F·Explore PJI module →
-
Table: PJI_FP_ORG_F_MV 12.1.1
-
Table: PJI_FP_CLS_F_MV 12.1.1
-
Table: PJI_FP_PROJ_F 12.1.1
This table stores summarized cost and revenue measures at the project level for Project Intelligence
-
APPS.PA_SUM_PROJECT_FUNDINGS2_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ PA_AGREEMENTS_ALL·Explore PA module →
-
Table: PJI_AC_AGGR_PJP1 12.2.2
-
Table: PJI_AC_AGGR_PJP1 12.1.1
-
VIEW: PJI.PJI_AC_AGGR_PJP0# 12.2.2
-
VIEW: PJI.PJI_AC_AGGR_PJP1# 12.2.2
-
VIEW: PA.PA_AC_OLAP_STAGE# 12.2.2
-
TABLE: PJI.PJI_FM_AGGR_FIN5 12.1.1
-
VIEW: PJI.PJI_AC_AGGR_PJP0# 12.2.2
-
TABLE: PJI.PJI_FM_AGGR_FIN3 12.1.1
-
Not implemented in this database·Explore PA module →
-
TABLE: PJI.PJI_FM_AGGR_FIN4 12.1.1
-
TABLE: PJI.PJI_FM_AGGR_ACT3 12.1.1
-
VIEW: PA.PA_AC_OLAP_STAGE# 12.2.2
-
VIEW: PJI.PJI_AC_AGGR_PJP1# 12.2.2
-
Not implemented in this database·Explore PA module →
-
TABLE: APPS.PJI_AC_ORG_F_MV 12.1.1