Search Results pa_fp_res_assignments_tmp




Overview
Explore in AI Chat

Overview

PA_FP_RES_ASSIGNMENTS_TMP is a transient Oracle Projects (PA) table that stores resource assignment level data for the internal use of Oracle Projects during the forecast planning (FP) and budget generation processes. The table is owned by the PA schema and is classified as VALID in Oracle EBS 12.1.1 and 12.2.2. It holds denormalized, staging-oriented rows produced while Oracle Projects assembles and evaluates plan or budget line data, including rates, quantities, currency amounts, and spread information, before that data is ultimately written to the permanent plan structures.

The name suggests a temporary or working table (the "_TMP" suffix), meaning its contents are typically populated, consumed, and purged by concurrent programs such as budget generation, forecast generation, and commitment processing rather than being maintained as durable business data. Because of the very wide column footprint (113 columns), the table combines resource assignment attributes, rate-schedule references, multi-currency billing indicators, and display-oriented columns (such as RESOURCE_NAME and TASK_NAME) in one physical row.

From a heuristic Data Vault modeling perspective, the FK relationships mined from the schema point to PA_RBS_ELEMENTS, PA_PROJECT_ROLE_TYPES, and PA_TOP_TASKS_IT. This pattern is consistent with a standalone classification, though it could reasonably be modeled as a satellite-like structure attached to a project/task hub, since RESOURCE_ASSIGNMENT_ID governs individual rows and the surrounding foreign keys represent business keys rather than a classical link between two hubs.

Key Information Stored

The table contains 113 columns, but the following are the most significant for identification, join, and rate logic:

Business-key candidates center on the combination of PROJECT_ID, TASK_ID, RBS_ELEMENT_ID, PROJECT_ROLE_ID, and PLANNING_START_DATE, though the metadata does not document a specific unique index.

Common Use Cases and Queries

The table is primarily consumed by Oracle Projects' internal forecast and budget generation routines, so direct reporting use is uncommon. Diagnostic queries usually filter by project or budget version to inspect staging output.

  • Verifying that a budget generated correctly by joining PA_FP_RES_ASSIGNMENTS_TMP rows back to PA_PROJECTS and PA_TASKS on PROJECT_ID and TASK_ID.
  • Comparing planned quantities against committed values by summing TXN_PLAN_QUANTITY grouped by RESOURCE_CLASS_CODE.
  • Checking rate application logic by selecting RAW_COST_RATE, BURDEN_COST_RATE, and BILL_RATE alongside the associated schedule IDs.
  • Debugging multi-currency issues by filtering on MULTI_CURRENCY_BILLING_FLAG and comparing TXN_CURRENCY_CODE against PROJECT_CURRENCY_CODE.
  • Cleansing stale rows by deleting on BUDGET_VERSION_ID after generation completes.

A representative pattern: SELECT t.PROJECT_ID, t.TASK_ID, t.RESOURCE_CLASS_CODE, SUM(t.TXN_PLAN_QUANTITY), SUM(t.TXN_RAW_COST) FROM PA.PA_FP_RES_ASSIGNMENTS_TMP t WHERE t.BUDGET_VERSION_ID = :version GROUP BY t.PROJECT_ID, t.TASK_ID, t.RESOURCE_CLASS_CODE;

Related Objects

The following tables are directly referenced by documented foreign keys or are the principal consumers of this data:

  • PA_RBS_ELEMENTS — joined on RBS_ELEMENT_ID.
  • PA_PROJECT_ROLE_TYPES — joined on PROJECT_ROLE_ID.
  • PA_TOP_TASKS_IT — joined on TOP_TASK_ID.
  • PA_PROJECTS_ALL / PA_PROJECTS — joined on PROJECT_ID for project context.
  • PA_TASKS — joined on TASK_ID for task detail.
  • PA_BUDGET_VERSIONS — joined on BUDGET_VERSION_ID to scope rows to a version.
  • PA_PLANNING_RESOURCES and PA_RESOURCE_ASSIGNMENTS — permanent counterparts where staged data ultimately lands.

Because the table is internal, Oracle does not publish a supported API for direct DML against it; any integration should go through the documented Oracle Projects budget and forecast APIs instead.