Results for “pji_summarized_flag”

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

Overview

PJI_FM_EXTR_ARINV is a table owned by the PJI schema within the Oracle E-Business Suite Project Intelligence (PJI) product family. The ETRM documentation classifies PJI as an obsolete module in release 12.1.1 and 12.2.2, and describes this object specifically as an intermediate summarization table. In practice, this means PJI_FM_EXTR_ARINV does not represent a transactional master entity. Instead, it functions as a staging or aggregation surface that consolidates Accounts Receivable invoice and cash application facts for downstream reporting, extract generation, and project-level financial analysis.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone, meaning the documented FK topology does not reveal a classic hub, link, or satellite pattern. This should be treated as a modeling suggestion rather than a definitive design statement. The table carries its own ROW_ID surrogate identifier and references CS_SYSTEMS_ALL_B_TEMP through that column, which supports the interpretation that it is populated by an ETL or batch extraction process rather than by direct online transaction entry.

Key Information Stored

Among the 14 documented columns, the most operationally significant are the following:

• ROW_ID — the surrogate primary key and the only column with a documented foreign key relationship, pointing to CS_SYSTEMS_ALL_B_TEMP.ROW_ID.
• WORKER_ID — identifies the user or worker context associated with the extracted row.
• PROJECT_ID, PROJECT_ORG_ID, and PROJECT_ORGANIZATION_ID — the project and organization key candidates that drive joins to project and operating unit dimensions.
• CUSTOMER_ID — the Accounts Receivable customer identifier associated with the summarized invoice data.
• DRAFT_INVOICE_NUM — the invoice number reference, used as a business-key candidate for tracing summarized amounts back to AR documents.
• CASH_APPLIED_AMOUNT — the amount of cash already applied against the invoice.
• AMOUNT_DUE_REMAINING and AMOUNT_OVERDUE_REMAINING — the outstanding and past-due balances respectively.
• MAX_ACTUAL_DATE_CLOSED — the latest actual close date captured for the summarized record.
• INTER_COMPANY_BILLING_FLAG — indicates whether the invoice involves intercompany billing.
• PJI_SUMMARIZED_FLAG — signals whether the row has already been rolled into a summary state.
• BATCH_ID — identifies the extraction batch that produced the row.

No explicit unique index columns are documented beyond the surrogate ROW_ID, so business-key uniqueness on DRAFT_INVOICE_NUM combined with PROJECT_ID should be verified against the live system before being relied upon.

Common Use Cases and Queries

The primary use case is project-level AR aging and cash application reporting. Analysts query this table to reconcile invoiced amounts against applied cash and remaining balances. A representative pattern is:

• Summarizing outstanding exposure by project: SELECT PROJECT_ID, SUM(AMOUNT_DUE_REMAINING) FROM PJI_FM_EXTR_ARINV WHERE PJI_SUMMARIZED_FLAG = 'Y' GROUP BY PROJECT_ID;
• Isolating overdue intercompany receivables: SELECT DRAFT_INVOICE_NUM, AMOUNT_OVERDUE_REMAINING FROM PJI_FM_EXTR_ARINV WHERE INTER_COMPANY_BILLING_FLAG = 'Y' AND AMOUNT_OVERDUE_REMAINING > 0;
• Auditing a specific extraction run by BATCH_ID to validate completeness before loading a downstream report.

Because the object is a summarization intermediate, queries should generally filter on PJI_SUMMARIZED_FLAG to avoid double counting unsummarized staging rows.

Related Objects

The documented relationship set is narrow. The principal references are:

• CS_SYSTEMS_ALL_B_TEMP — joined on PJI_FM_EXTR_ARINV.ROW_ID = CS_SYSTEMS_ALL_B_TEMP.ROW_ID, providing the system-level extraction context.
• PJI_FM_EXTR_ARINV column set implies joins to AR invoice and customer dimension objects (CUSTOMER_ID) and to project/organization dimensions (PROJECT_ID, PROJECT_ORG_ID, PROJECT_ORGANIZATION_ID).
• Downstream PJI extract and summary tables that consume BATCH_ID and PJI_SUMMARIZED_FLAG complete the extraction pipeline.

Given the obsolete product status in 12.2.2, dependency analysis should confirm whether any active concurrent program or report still reads this table before retirement.