Search Results pa_fp_merged_ctrl_items




Overview
Explore in AI Chat

Overview

PA_FP_MERGED_CTRL_ITEMS is an Oracle Projects (PA) transactional table that records the change documents merged into a financial plan version. In Oracle EBS 12.1.1 and 12.2.2, it functions as the reconciliation bridge between the change management (control items) subsystem and the financial plan/budget versioning subsystem. When changes affecting cost, revenue, quantity, or equipment are approved and then incorporated into a plan version, a row is written here to capture the impact values that were merged, the source control item, the version into which it was merged, and the person who performed the inclusion.

The ETRM metadata classifies this object, using a Data Vault heuristic derived from its foreign key structure, as a link table. This is a modeling suggestion rather than a physical constraint: the table sits at the intersection of projects, plan versions, control items, and parties, and its unique index confirms it is a many-to-many resolution entity rather than a pure hub or satellite. It carries descriptive (satellite-like) measures as well as the linking keys, so downstream modelers should treat it as a link with attached descriptive attributes.

Key Information Stored

The table is defined in the PA schema with 22 documented columns. The most significant are the linking and descriptive attributes that drive both the unique key and downstream reporting:

The unique index PA_FP_MERGED_CTRL_ITEMS_U1 covers (PROJECT_ID, PLAN_VERSION_ID, CI_ID, CI_PLAN_VERSION_ID, VERSION_TYPE), making this composite the business-key candidate. No separate surrogate primary key column is documented in the ETRM metadata; the composite unique index effectively serves as the business key.

Common Use Cases and Queries

Typical scenarios include auditing which control items were folded into a plan version, reconciling merged amounts against source control items, and reporting the financial impact of approved changes by version. A representative join pattern follows the documented foreign keys:

  • Listing all control items merged into a specific plan version:
    SELECT m.ci_id, m.impl_proj_raw_cost, m.impl_proj_revenue FROM pa.pa_fp_merged_ctrl_items m WHERE m.project_id = :project_id AND m.plan_version_id = :version_id;
  • Identifying the person and method for each inclusion by joining to HZ_PARTIES on INCLUDED_BY_PERSON_ID.
  • Reconciling merged impacts across functional and project cost/revenue columns for financial reporting.
  • Auditing change merge activity using CREATION_DATE, CREATED_BY, and LAST_UPDATE_DATE.

Related Objects

  • PA_PROJECTS_ALL — joined on PROJECT_ID.
  • PA_BUDGET_VERSIONS — joined on PLAN_VERSION_ID and, separately, on CI_PLAN_VERSION_ID.
  • PA_CONTROL_ITEMS — joined on CI_ID; the source change documents.
  • HZ_PARTIES — joined on INCLUDED_BY_PERSON_ID for the including user.
  • PA_FINANCIAL_PLANS / plan version UI — consumes this data when displaying merged changes.
  • PA Change Management APIs — used during merge processing that populates this table.