Search Results pji_fm_extr_dinvc




Overview
Explore in AI Chat

Overview

PJI_FM_EXTR_DINVC is a table owned by the PJI schema within the Oracle E-Business Suite Project Intelligence (PJI) product family. Per the ETRM documentation, it is described as an intermediate summarization table. In practice, this object functions as a staging and aggregation layer that Project Intelligence uses to consolidate draft invoice and revenue-related facts extracted from Oracle Projects before those facts are loaded into the PJI reporting star schemas. Because PJI delivers project financial analytics, cost, revenue, and margin reporting, intermediate summarization tables such as this one exist to reduce the volume of source transactions and to expose only the summarized grain that the analytics engine consumes.

The mined Data Vault classification for this table is standalone, meaning the heuristic FK analysis did not identify it as a conventional hub, link, or satellite. A reasonable modeling suggestion is therefore to treat it as a satellite-style summarization structure keyed by its surrogate identifier, with descriptive and financial measures attached rather than acting as a shared business key hub.

Key Information Stored

With 22 documented columns, the table mixes surrogate identifiers, project context, and financial measures. The most significant columns include:

Common Use Cases and Queries

Typical use cases center on draft invoice analysis, unbilled receivable reporting, unearned revenue reconciliation, and approval status tracking. A representative query to examine summarized draft invoice activity by project follows:

  • SELECT PROJECT_ID, DRAFT_INVOICE_NUM, SUM(UNBILLED_RECEIVABLE_DR) DR, SUM(UNEARNED_REVENUE_CR) CR FROM PJI_FM_EXTR_DINVC GROUP BY PROJECT_ID, DRAFT_INVOICE_NUM;
  • Filtering by APPROVED_FLAG = 'Y' isolates approved transactions, while PJI_SUMMARIZED_FLAG can be used to track rows already processed by the summarization routine.
  • Date-bounded reporting relies on GL_DATE or PA_DATE, often combined with PJI_DATE_RANGE_FLAG to respect the configured extract range.
  • Reconciliation queries join CUSTOMER_ID to customer master tables to validate draft invoice balances by customer.

Related Objects

The documented relationship data links ROW_ID to CS_SYSTEMS_ALL_B_TEMP, the EBS systems registration structure that anchors many PJI extract tables. Beyond this documented link, PJI summarization and reporting flows typically connect this staging table to:

  • CS_SYSTEMS_ALL_B_TEMP — joined on ROW_ID to resolve the source system registration.
  • Oracle Projects base tables, including PA_PROJECTS_ALL (via PROJECT_ID), PA_DRAFT_INVOICES_ALL (via DRAFT_INVOICE_NUM), and PA_DRAFT_REVENUES_ALL for source revenue detail.
  • Customer master objects such as HZ_CUST_ACCOUNTS (via CUSTOMER_ID) for customer-level reporting.
  • PJI summary and fact tables that consume this intermediate layer during extract and load processing.

Because schemas, column lists, and relationships can vary between EBS 12.1.1 and 12.2.2, readers should validate against the ETRM data for their specific release before building dependent logic.