Search Results planning_start_date




Overview
Explore in AI Chat

Overview

PA.PA_FP_PLANNING_RES_TMP1_1 is a global temporary table within the Oracle E-Business Suite Projects (PA) schema, documented as VALID in ETRM for releases 12.1.1 and 12.2.2. It is a transient staging object used by the workforce planning and resource forecasting functionality, most plausibly the planning engine behind resource assignment and requirement-date calculations. Because it is a global temporary table with a data duration of SYS$TRANSACTION, rows are visible only to the session that inserts them, and all data is purged at transaction commit or rollback. The table is therefore never a permanent record of business state; it is an intermediate work area whose contents are consumed by the calling program during a planning run.

Under the heuristic Data Vault classification supplied with the metadata, this object is modelled as a standalone structure with no conformed hub, link, or satellite designation. The suggestion from this classification is to treat the table as a transient staging area rather than a persistent entity; any enduring history should be captured in the permanent planning or assignment tables that the temporary rows are derived from. The physical definition carries a PCT FREE of 10 and PCT USED of 40, settings consistent with a high-volume insert-and-consume workload in which blocks are discarded rather than updated repeatedly.

Key Information Stored

The table contains seven documented columns, of which the most significant are the task and resource identifiers along with the planning date range that the user's search term, planning_end_date, targets.

  • TASK_ID (NUMBER 15) — Identifier of the project task whose resource plan is being computed. Indexed non-uniquely by PA_FP_PLANNING_RES_TMP1_N1.
  • TOP_TASK_ID (NUMBER 15) — Identifier of the top-level task from which the planned task descends; the only documented foreign key in this object, referencing PA_TOP_TASKS_IT. This supports hierarchical roll-up of planning results.
  • RESOURCE_LIST_MEMBER_ID (NUMBER 15) — Identifier of the resource list member supplying the resource definition. Indexed non-uniquely by PA_FP_PLANNING_RES_TMP1_N2.
  • RESOURCE_ASSIGNMENT_ID (NUMBER 15) — Identifier linking the temporary row to the underlying resource assignment.
  • PLANNING_START_DATE (DATE) — Start of the planning interval used when the row was generated.
  • PLANNING_END_DATE (DATE) — End of the planning interval; this is the column most commonly used to filter, group, or slice planning output and is the target of the user's search.
  • CBS_ELEMENT_ID (NUMBER 15) — Identifier of the cost breakdown structure element to which the planned resource is attributed, enabling financial integration.

No primary key constraint is documented. The nearest business-key candidates are the two non-unique indexes on TASK_ID and RESOURCE_LIST_MEMBER_ID; the logical grain is most plausibly the combination of TASK_ID, RESOURCE_LIST_MEMBER_ID, and the planning date range, though this is not enforced at the database level.

Common Use Cases and Queries

Because the table is session-scoped and transaction-duration, practical use falls into three categories: extracting a session's planning output, validating the planning horizon, and diagnosing why a particular task or assignment produced no forecast.

  • Extract all planning rows for a task across the planning horizon:
    SELECT task_id, resource_list_member_id, resource_assignment_id, planning_start_date, planning_end_date FROM pa.pa_fp_planning_res_tmp1_1 WHERE task_id = :task_id ORDER BY planning_start_date;
  • Identify resource plans that extend beyond or end before a chosen cutoff:
    SELECT * FROM pa.pa_fp_planning_res_tmp1_1 WHERE planning_end_date > :cutoff_date;
  • Roll up planned resources by top task and CBS element:
    SELECT top_task_id, cbs_element_id, COUNT(*) FROM pa.pa_fp_planning_res_tmp1_1 GROUP BY top_task_id, cbs_element_id;

Reporting should generally be performed against permanent planning tables. Temporary rows are intended for inspection only while the generating session remains active; once the transaction commits, the contents are lost.

Related Objects

The dependency metadata identifies PA_TOP_TASKS_IT as the parent of TOP_TASK_ID, making it the principal participant in any join. Beyond this documented link, the following objects are the most significant associates of this temporary planning structure:

  • PA_TOP_TASKS_IT — referenced through TOP_TASK_ID; supplies the top-task definition for roll-up.
  • APPS.PA_FP_PLANNING_RES_TMP1_1 — the APPS synonym, the object through which application code normally accesses the table.
  • PA.PA_FP_PLANNING_RES_TMP1_N1 / _N2 — the supporting non-unique indexes on TASK_ID and RESOURCE_LIST_MEMBER_ID.
  • PA.PA_RESOURCE_ASSIGNMENTS — the persistent assignment records referenced by RESOURCE_ASSIGNMENT_ID.
  • PA.PA_RESOURCE_LIST_MEMBERS — the resource list definitions referenced by RESOURCE_LIST_MEMBER_ID.
  • PA.PA_TASKS — the task hierarchy providing TASK_ID context.
  • PA.PA_CBS_ELEMENTS — the cost breakdown structure definitions behind CBS_ELEMENT_ID.

Join paths should use TASK_ID to PA_TASKS, TOP_TASK_ID to PA_TOP_TASKS_IT, RESOURCE_LIST_MEMBER_ID to PA_RESOURCE_LIST_MEMBERS, and CBS_ELEMENT_ID to PA_CBS_ELEMENTS, observing that the temporary table holds no enforced uniqueness and may return multiple rows per key combination.