Results for “pa_fp_planning_res_tmp1_1”

11 results




Overview
Explore in AI Chat

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

Overview

PA_FP_PLANNING_RES_TMP1_1 is a temporary planning table in the PA (Projects) schema of Oracle E-Business Suite, documented as VALID in ETRM release 12.2.2. It belongs to the Project Resource Management / forecasting and planning area of the Projects module, and is one of a family of interim (TMP) tables used by the resource planning and forecasting programs to stage, sort, or aggregate planning rows before they are consumed by reporting logic or promoted into permanent planning tables. Because the name carries a numeric suffix, it should be regarded as a workspace or scratch table rather than a transactional master: contents are generally transient, scoped to a single planning run, and should not be treated as a system of record for committed project data.

From the mined foreign key structure, the object is classified heuristically as a standalone data vault construct. This is a modeling suggestion rather than a definitional statement: the table does not currently exhibit the hub-and-link topology typical of a normalized integration model, which is consistent with an interim planning staging table whose grain is defined by the combination of a task, a resource, and a planning window rather than by a single durable business entity. Implementers treating this object in a warehouse or integration layer should therefore consider a satellite-style treatment keyed on the task and resource combination, with the planning dates as descriptive context.

Key Information Stored

The documented physical schema exposes seven columns. The most significant are:

  • TASK_ID — identifier of the project task against which planning is performed. This is the principal business-key candidate for the row grain.
  • RESOURCE_LIST_MEMBER_ID — the resource list member being planned, linking the row to a specific resource within a resource list definition.
  • RESOURCE_ASSIGNMENT_ID — the resource assignment context, tying the planning row to how the resource is assigned on the project.
  • TOP_TASK_ID — the top-level task for the planning structure. This is the only documented foreign key, referencing PA_TOP_TASKS_IT, and is used to roll planning rows up to a structural parent task.
  • PLANNING_START_DATE and PLANNING_END_DATE — the effective window over which the resource is planned, providing the temporal dimension of the staging row.
  • CBS_ELEMENT_ID — the cost breakdown structure element used to classify the planned cost or effort.

No surrogate primary key is documented in the metadata excerpt; the effective row identity is therefore the composite of task, resource, CBS element, and planning window. Because this is an interim table, any uniqueness is generally enforced by the process that populates it rather than by a permanent constraint.

Common Use Cases and Queries

Typical uses are diagnostic and reporting-oriented: verifying that a forecasting run staged the expected planning rows, reconciling planned resource effort against assignments, and joining planning windows to financial periods for capacity reporting.

  • Audit a planning run by task: SELECT task_id, resource_list_member_id, planning_start_date, planning_end_date FROM pa_fp_planning_res_tmp1_1 WHERE task_id = :task_id;
  • Rollup by top task: join to PA_TOP_TASKS_IT on TOP_TASK_ID to group planned resources by structural parent.
  • Cost classification review: group rows by CBS_ELEMENT_ID to confirm planned effort maps to the intended cost element.
  • Resource demand by window: filter on PLANNING_START_DATE / PLANNING_END_DATE to build time-phased resource demand extracts.
  • Reconciliation: outer join the temporary rows to resource assignment facts on RESOURCE_ASSIGNMENT_ID to identify staged rows with no matching assignment.

Queries should be constrained tightly and executed soon after the planning process runs, since interim content is subject to truncation.

Related Objects

  • PA_TOP_TASKS_IT — referenced via PA_FP_PLANNING_RES_TMP1_1.TOP_TASK_ID; provides the top-level task structure used for rollups.
  • PA_TASKS — supplies the task definition behind TASK_ID.
  • PA_RESOURCE_ASSIGNMENTS — the assignment context behind RESOURCE_ASSIGNMENT_ID.
  • PA_RESOURCE_LIST_MEMBERS — the resource list membership behind RESOURCE_LIST_MEMBER_ID.
  • PA_CBS_ELEMENTS — the cost breakdown structure element behind CBS_ELEMENT_ID.
  • PA_FP_PLANNING_RES_TMP1 and sibling interim tables in the PA_FP_PLANNING_RES_TMP family — parallel staging objects produced by the same planning programs.
  • PA_PROJECTS_ALL — the project master used to resolve planning rows to project context.

Because the metadata available is limited to column and FK information, the above related objects are inferred from documented column semantics and should be validated against the live data dictionary in the target 12.1.1 or 12.2.2 instance before being relied upon in production SQL.