Results for “named_role”

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

Overview

PJI_FM_AGGR_FIN6 is an intermediate aggregation table owned by the PJI (Project Intelligence) schema in Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It supports the Project Intelligence product, which provides analytical reporting and costing intelligence over project data, and its documented purpose is to serve as the first aggregation of PJP (project performance) data by accounting periods. In effect, it consolidates detailed project transaction records into a period-level staging structure that downstream materialized views, summary tables, and dashboards in PJI consume.

Because the table has no foreign-key dependencies directed at it and no data-vault relationship to other tables through its primary key, the ETRM metadata classifies it as standalone in its heuristic Data Vault classification. In other words, the table functions as a de-normalized, self-contained fact staging object rather than a hub, link, or satellite in the strictly modeled sense.

Key Information Stored

The table contains 97 columns, most of which are numeric measures summed at a period grain. Several columns form the implicit business-key candidates that define the row's granularity:

• PROJECT_ID, TASK_ID, PROJECT_ORG_ID / PROJECT_ORGANIZATION_ID — the project and task dimension keys.
• RECVR_PERIOD_ID and RECVR_PERIOD_TYPE — the accounting period identifier and its type (e.g., GL period, PA period), which drive the “by periods” aggregation.
• EXPENDITURE_CATEGORY_ID, EXPENDITURE_TYPE_ID, EXPENDITURE_ORG_ID / EXPENDITURE_ORGANIZATION_ID — expenditure classification and owning organization.
• RESOURCE_CLASS_ID, JOB_ID, VENDOR_ID, WORK_TYPE_ID, PERSON_ID, WORKER_ID, ASSIGNMENT_ID, PROJECT_ROLE_ID — resource and labor attribution.
• EVENT_TYPE_ID, EXP_EVT_TYPE_ID, EVENT_TYPE_CLASSIFICATION — the cost/revenue event source.
• TXN_CURRENCY_CODE plus the measure groups: TXN_* (transaction currency), PRJ_* (project currency), POU_* (project organization currency), EOU_* (expenditure organization currency), and G1_*/G2_* (global reporting currencies).
• QUANTITY and BILL_QUANTITY — summed units of work or billed measure.

The measure families repeat the same set of metrics — REVENUE, RAW_COST, BRDN_COST, BILL_RAW_COST, BILL_BRDN_COST, REVENUE_WRITEOFF, and SUP_INV/PO/PR/OTH_COMMITTED_COST — across each currency context. Two foreign keys are documented: EVENT_TYPE_ID references RCV_ACCOUNTING_EVENT_TYPES, and PROJECT_ROLE_ID references PA_PROJECT_ROLE_TYPES.

Common Use Cases and Queries

The most common pattern is period-over-period costing and revenue analysis, often filtered by project, task, or the current period, e.g.:

SELECT PROJECT_ID, TASK_ID, RECVR_PERIOD_ID,
       SUM(PRJ_REVENUE)     AS revenue,
       SUM(PRJ_RAW_COST)    AS raw_cost,
       SUM(PRJ_BRDN_COST)   AS burdened_cost
FROM   PJI.PJI_FM_AGGR_FIN6
WHERE  RECVR_PERIOD_ID = :p_period
GROUP  BY PROJECT_ID, TASK_ID, RECVR_PERIOD_ID;

Typical consumers include Project Intelligence dashboards that must display both transaction-currency and project-currency totals without hitting the much larger detail tables. Because the table consolidates the five currency contexts plus committed-cost buckets in one place, it is also used for earned-value style reporting and for reconciling project currency against expenditure-organization currency.

Related Objects

• RCV_ACCOUNTING_EVENT_TYPES — joined on EVENT_TYPE_ID to classify cost and revenue events.
• PA_PROJECT_ROLE_TYPES — joined on PROJECT_ROLE_ID to describe the labor role used on the project.
• PJI_FM_AGGR_FINn sibling aggregation tables, which form the layered PJI summary chain consumed by project intelligence facts.
• PA_PROJECTS / PA_TASKS — the source of PROJECT_ID and TASK_ID dimensional attributes.
• PA_PERIODS (or the GL period table) — the source of RECVR_PERIOD_ID and RECVR_PERIOD_TYPE.
• PA_EXPENDITURE_TYPES and PA_EXPENDITURE_CATEGORIES — joined on EXPENDITURE_TYPE_ID and EXPENDITURE_CATEGORY_ID for classification.
• PJI_FM_* materialized views and ODI/ETL mappings — the runtime consumers that refresh and publish this staging table's contents.