Results for “prj_allocated_amount”

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

Overview

PJI_FM_EXTR_FUNDG is an intermediate summarization table owned by the PJI schema within the Project Intelligence (PJI) product family of Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, Project Intelligence provides the analytical and reporting layer that consolidates project costing, billing, and funding data into denormalized structures optimized for extraction, reporting, and transfer into external analytical environments. PJI_FM_EXTR_FUNDG specifically supports the funding management extraction process, holding pre-aggregated funding allocation amounts across workers, projects, organizations, and customers before they are consumed by downstream reporting or extraction programs.

Because the table is described as an intermediate summarization table, it functions as a staging and aggregation point rather than a transaction-bearing entity. Rows are produced by extraction or summarization concurrent programs and are typically truncated or purged between extraction runs. From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone, meaning the table does not participate in a defined hub, link, or satellite relationship within the documented schema. It is best treated as a derived or transient staging artifact rather than a durable business entity. The only documented foreign key, ROW_ID referencing CS_SYSTEMS_ALL_B_TEMP, reinforces that rows are tied to an extraction or batch context rather than to a persistent master record.

Key Information Stored

The table is documented with 12 columns. The most significant include:

• ROW_ID — The documented foreign key to CS_SYSTEMS_ALL_B_TEMP, serving as the extraction-context or batch-row identifier. While it participates in a foreign key relationship, it is not documented as the surrogate primary key of this table.
• BATCH_ID — Identifies the summarization or extraction batch that produced each row, supporting run isolation and purge logic.
• WORKER_ID — The worker associated with the summarized funding allocation, typically the resource or assignment owner.
• PROJECT_ID — The project to which the funding allocation applies.
• PROJECT_ORG_ID and PROJECT_ORGANIZATION_ID — Organization identifiers for the project, used to segment funding by operating unit or project organization.
• CUSTOMER_ID — The customer associated with the funded project, enabling customer-level funding analysis.
• DATE_ALLOCATED — The date on which the funding amount was allocated, supporting period-based reporting.
• POU_ALLOCATED_AMOUNT — The allocated amount attributed at the project organization unit level.
• PRJ_ALLOCATED_AMOUNT — The allocated amount attributed at the project level.
• FUNDING_CATEGORY — The classification of the funding, used to group and filter allocations by funding type.
• PJI_SUMMARIZED_FLAG — A processing indicator that marks rows as summarized and ready for downstream consumption or exclusion.

The metadata does not document a surrogate primary key or unique business-key index for this table. In practice, uniqueness is implied by the combination of BATCH_ID with the project, organization, worker, customer, and allocation-date business keys. The distinction matters because direct DML against this table is generally discouraged; it is a managed staging object.

Common Use Cases and Queries

The table is most commonly queried in three scenarios: verifying summarization completeness, reconciling allocated amounts, and feeding external extracts. A typical completeness check filters on the summarization flag and batch:

SELECT BATCH_ID, COUNT(*), SUM(PRJ_ALLOCATED_AMOUNT)
FROM PJI.PJI_FM_EXTR_FUNDG
WHERE PJI_SUMMARIZED_FLAG = 'Y'
GROUP BY BATCH_ID;

A funding-by-category report aggregates allocations across projects and customers:

SELECT PROJECT_ID, CUSTOMER_ID, FUNDING_CATEGORY,
SUM(POU_ALLOCATED_AMOUNT) POU_AMT,
SUM(PRJ_ALLOCATED_AMOUNT) PRJ_AMT
FROM PJI.PJI_FM_EXTR_FUNDG
WHERE DATE_ALLOCATED BETWEEN :start_date AND :end_date
GROUP BY PROJECT_ID, CUSTOMER_ID, FUNDING_CATEGORY;

Because rows are transient, purge and validation queries joining to CS_SYSTEMS_ALL_B_TEMP on ROW_ID are also common, ensuring the extraction context is valid before data is promoted to downstream reporting tables. Reporting use cases include project funding dashboards, customer funding trend analysis, and reconciliation between summarized allocations and project funding source transactions.

Related Objects

• CS_SYSTEMS_ALL_B_TEMP — Referenced via the documented foreign key PJI_FM_EXTR_FUNDG.ROW_ID to CS_SYSTEMS_ALL_B_TEMP, providing the extraction or system context for each row.
• PJI_FM_EXTR family tables — Sibling funding-management extraction tables that share batch and summarization patterns and are often processed together.
• PA_PROJECTS_ALL — Source of PROJECT_ID values, used to enrich summarized rows with project attributes.
• PA_ORGANIZATIONS_ALL — Source of organization identifiers corresponding to PROJECT_ORG_ID and PROJECT_ORGANIZATION_ID.
• RA_CUSTOMERS — Source of CUSTOMER_ID values for customer-level funding reporting.
• PER_ALL_PEOPLE_F — Source of WORKER_ID values for resource-level allocation analysis.

These relationships should be confirmed against the specific EBS patch level, as the funding extraction process and its staging tables were subject to change between 12.1.1 and 12.2.2.