Results for “pa_fp_excluded_elements”

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

Overview

PA_FP_EXCLUDED_ELEMENTS is a transactional table in the Oracle Projects (PA) schema that stores tasks which have been excluded from financial planning calculations. In Oracle EBS 12.1.1 and 12.2.2, financial planning allows project managers to generate forecasts and budgets over a defined plan type and version. Certain tasks on a project—typically non-labor, summary, or administrative tasks—may be intentionally omitted from that planning scope. PA_FP_EXCLUDED_ELEMENTS persists those exclusions so that plan generation, summarization, and reporting routines consistently honor the same task set across sessions and release upgrades.

Functionally, the table acts as a filter registry keyed by the plan option, the element type, and the specific task being excluded. It is consulted by the financial planning engine before costs and quantities are aggregated into a plan, ensuring that excluded tasks do not contribute rows to the planning output.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is link. The table's shape—a composite key referencing multiple hubs (project, plan options, plan type, plan version, and task)—is consistent with a link entity that resolves a many-to-many relationship between planning configurations and excluded tasks. This classification should be treated as a modeling suggestion rather than a documented Oracle architectural assertion.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• PROJ_FP_OPTIONS_ID — Identifier of the financial planning option record to which the exclusion applies; part of the primary key.
• PROJECT_ID — The project owning the excluded task, referencing PA_PROJECTS_ALL.
• FIN_PLAN_TYPE_ID — The financial plan type (for example, cost budget or revenue budget) within which the task is excluded, referencing PA_FIN_PLAN_TYPES_B.
• FIN_PLAN_VERSION_ID — The specific plan version the exclusion is scoped to, referencing PA_BUDGET_VERSIONS.
• ELEMENT_TYPE — Classifies the excluded element (for example, task versus other planning element categories); part of the primary key.
• TASK_ID — The task being excluded, referencing PA_TASKS; part of the primary key.
• RECORD_VERSION_NUMBER — Optimistic locking counter used to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO columns for audit and change tracking.

The surrogate primary key is PA_FP_EXCLUDED_ELEMENTS_PK, defined over (PROJ_FP_OPTIONS_ID, ELEMENT_TYPE, TASK_ID). A unique index, PA_FP_EXCLUDED_ELEMENTS_U1, shares the same three-column composition, making it the business-key candidate that enforces one exclusion record per option/element/task combination.

Common Use Cases and Queries

Typical scenarios include auditing which tasks are omitted from a plan, reconciling plan output differences against the exclusion list, and migrating exclusion configurations between environments. A representative query lists excluded tasks for a given plan option:

• SELECT e.TASK_ID, t.TASK_NUMBER, t.TASK_NAME, e.ELEMENT_TYPE FROM PA_FP_EXCLUDED_ELEMENTS e, PA_TASKS t WHERE e.TASK_ID = t.TASK_ID AND e.PROJ_FP_OPTIONS_ID = :p_option_id;
• Reporting by plan type and version: join FIN_PLAN_TYPE_ID to PA_FIN_PLAN_TYPES_B and FIN_PLAN_VERSION_ID to PA_BUDGET_VERSIONS to produce a readable exclusion report.
• Change auditing: filter on LAST_UPDATE_DATE greater than a cutoff to identify recently added or removed exclusions.
• Integrity validation: outer-join back to PA_TASKS to detect orphaned TASK_ID values indicating stale exclusions after task deletion.

Related Objects

The following objects are referenced by foreign keys or depend on this table:

• PA_PROJECTS_ALL — joined on PROJECT_ID; supplies project context.
• PA_PROJ_FP_OPTIONS — joined on PROJ_FP_OPTIONS_ID; the parent planning option definition.
• PA_FIN_PLAN_TYPES_B — joined on FIN_PLAN_TYPE_ID; the plan type definition.
• PA_BUDGET_VERSIONS — joined on FIN_PLAN_VERSION_ID; the plan version record.
• PA_TASKS — joined on TASK_ID; the excluded task master.

These relationships confirm that PA_FP_EXCLUDED_ELEMENTS sits at the intersection of project planning configuration and the task hierarchy, acting as a persistent exclusion filter for financial planning.