Results for “pji_rm_res_f”

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

Overview

PJI_RM_RES_F is a table owned by the PJI schema and belongs to the Project Intelligence product family, which Oracle has classified as Obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores summarized data for utilization and availability measures by resource, effectively serving as a pre-computed fact store for resource management reporting within Project Intelligence. Rather than aggregating raw expenditure and assignment transactions at query time, Project Intelligence materializes period-based summaries into this table so that resource utilization, billing, training, and availability metrics can be retrieved efficiently.

In the documented physical schema the object exposes 53 columns, and it carries three foreign key relationships: JOB_ID to PER_JOBS, and both EXPENDITURE_ORGANIZATION_ID and EXPENDITURE_ORG_ID to HR_ALL_ORGANIZATION_UNITS. From a heuristic Data Vault modeling perspective, the presence of these foreign keys and the absence of any referenced-by relationships suggests this object is best treated as a link classification — it joins resource, job, organization, and time context — although it also carries many aggregate measure columns that behave like satellite attributes.

Key Information Stored

The table blends dimensional keys, period context, and a wide set of additive and semi-additive measures. The most significant columns fall into three groups.

• Resource and job identity: PERSON_ID identifies the resource, while JOB_ID references PER_JOBS to describe the resource's job role. EXPENDITURE_ORGANIZATION_ID and EXPENDITURE_ORG_ID capture the owning expenditure organization.
• Time and period context: TIME_ID anchors the summary to a calendar period, supported by PERIOD_TYPE_ID and CALENDAR_TYPE.
• Utilization and availability measures: Actual-hours metrics such as CAPACITY_HRS, TOTAL_HRS_A, BILL_HRS_A, TRAINING_HRS_A, UNASSIGNED_HRS_A, and REDUCE_CAPACITY_HRS_A; scheduled/forecast metrics distinguished by the _S suffix such as CONF_HRS_S, PROV_HRS_S, CONF_BILL_HRS_S, and PROV_BILL_HRS_S; and bucketed availability measures AVAILABLE_HRS_BKT1_S through AVAILABLE_HRS_BKT5_S paired with AVAILABLE_RES_COUNT_BKT1_S through AVAILABLE_RES_COUNT_BKT5_S. The column TOTAL_RES_COUNT summarizes resource headcount for the period.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN follow standard EBS conventions.

No explicit surrogate primary key or unique business key index is documented in the supplied metadata. In practice, the natural business key is the combination of TIME_ID, PERSON_ID, JOB_ID, and the expenditure organization columns, which together define a unique resource-period-organization summary row.

Common Use Cases and Queries

The primary use case is resource utilization and availability reporting for project portfolios. Analysts query this table to determine how many hours a person or job role was capacity-available versus billed across a period, and to compare confirmed against provisional billable hours.

SELECT PERSON_ID, TIME_ID, CAPACITY_HRS, BILL_HRS_A, AVAILABLE_HRS_BKT1_S
FROM   PJI.PJI_RM_RES_F
WHERE  TIME_ID = :period_id
AND    EXPENDITURE_ORG_ID = :org_id;

Other scenarios include capacity planning (comparing AVAILABLE_HRS_BKT*_S against REDUCE_CAPACITY_HRS_A), utilization trending by job (JOB_ID), and headcount reporting via TOTAL_RES_COUNT. Because the object is obsolete, these queries typically serve historical reconciliation or migration efforts rather than current dashboards.

Related Objects

• PER_JOBS — joined on PJI_RM_RES_F.JOB_ID = PER_JOBS.JOB_ID; supplies job name and classification for resource reporting.
• HR_ALL_ORGANIZATION_UNITS — joined twice, on EXPENDITURE_ORGANIZATION_ID and on EXPENDITURE_ORG_ID, providing organization name and hierarchy.
• PER_ALL_PEOPLE_F — referenced implicitly through PERSON_ID to resolve resource names.
• PER_TIME_PERIODS_F / time dimension — referenced through TIME_ID for period descriptions.
• PJI_RM_ORG_F and other PJI resource-management fact tables — sibling summaries populated by the same Project Intelligence collection programs.

Because Project Intelligence is obsolete, most integrations depend on these summaries through legacy collection concurrent programs rather than direct API calls.