Results for “pa_fp_elements”

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

Overview

PA_FP_ELEMENTS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the plannable elements associated with a project. Each row defines an element — a combination of task, planning level, and resource — that participates in the financial planning process for a project. The table is central to how Oracle Projects Financial Planning (FP) determines which tasks and resources can be planned, at what level of the work breakdown structure they are planned, and how planning amounts are captured against them.

The object is owned by the PA schema and is documented as VALID in the ETRM reference for 12.2.2. It contains 22 columns and is anchored by the primary key constraint PA_FP_ELEMENTS_PK on PROJ_FP_ELEMENTS_ID. Based on the foreign-key structure mined from the documented relationships, this table is heuristically classified as a link in Data Vault modeling terms — it connects projects, tasks, planning options, plan versions, plan types, and resource list members into a single plannable-element record rather than representing an independent business entity.

Key Information Stored

The surrogate primary key is PROJ_FP_ELEMENTS_ID, which uniquely identifies each plannable element. A second unique index, PA_FP_ELEMENTS_U2, covers the combination of PROJ_FP_OPTIONS_ID, ELEMENT_TYPE, TASK_ID, and RESOURCE_LIST_MEMBER_ID, making that tuple the effective business-key candidate for the record.

The most significant columns include:

• PROJECT_ID — the project to which the element belongs; joins to PA_PROJECTS_ALL.
• PROJ_FP_OPTIONS_ID — the financial planning options record that governs the element.
• FIN_PLAN_TYPE_ID — the financial plan type (for example, budget or forecast) under which the element is planned.
• FIN_PLAN_VERSION_ID — the specific plan version the element is associated with; joins to PA_BUDGET_VERSIONS.
• ELEMENT_TYPE — categorizes the plannable element.
• TASK_ID and TOP_TASK_ID — the task and its top-level task in the work breakdown structure; both join to PA_TASKS.
• RESOURCE_LIST_MEMBER_ID — the resource member being planned; joins to PA_RESOURCE_LIST_MEMBERS.
• TOP_TASK_PLANNING_LEVEL and RESOURCE_PLANNING_LEVEL — indicate the planning granularity for the top task and resource respectively.
• PLANNABLE_FLAG and TMP_PLANNABLE_FLAG — control whether the element is currently plannable.
• RESOURCES_PLANNED_FOR_TASK — indicates whether resources are planned at the task level.
• PLAN_AMOUNT_EXISTS_FLAG — flags whether planning amounts exist for the element.
• RECORD_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit and concurrency columns.

Common Use Cases and Queries

Typical reporting scenarios include identifying which tasks and resources are eligible for planning within a project, auditing plannable levels, and determining whether plan amounts have been entered. A representative query joins the element to its project, task, and plan version:

SELECT e.proj_fp_elements_id, e.project_id, e.task_id, e.top_task_id, e.fin_plan_version_id, e.plannable_flag, e.plan_amount_exists_flag FROM pa_fp_elements e WHERE e.project_id = :project_id AND e.plannable_flag = 'Y';

Analysts frequently filter on PLANNABLE_FLAG to reconcile the elements surfaced in the planning user interface against the underlying data, and use PLAN_AMOUNT_EXISTS_FLAG to detect elements that are plannable but not yet populated. Joining to PA_BUDGET_VERSIONS supports version-level reporting, while ELEMENT_TYPE and RESOURCE_LIST_MEMBER_ID support resource-oriented breakdowns.

Related Objects

The documented foreign keys establish the following principal relationships:

• PA_PROJECTS_ALL via PROJECT_ID — the owning project.
• PA_TASKS via TASK_ID and TOP_TASK_ID — the planned task and its top task.
• PA_PROJ_FP_OPTIONS via PROJ_FP_OPTIONS_ID — the financial planning options controlling the element.
• PA_FIN_PLAN_TYPES_B via FIN_PLAN_TYPE_ID — the plan type definition.
• PA_BUDGET_VERSIONS via FIN_PLAN_VERSION_ID — the plan version containing the element.
• PA_RESOURCE_LIST_MEMBERS via RESOURCE_LIST_MEMBER_ID — the resource being planned.

These relationships confirm PA_FP_ELEMENTS as a linkage table that ties planning configuration, work breakdown structure, resources, and plan versions together, and it is typically accessed through Projects Financial Planning forms, concurrent programs, and reporting views that rely on the same join paths.