Results for “pa_ci_impacts_v”

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

Overview

PA_CI_IMPACTS_V is an APPS-owned database view within the Oracle E-Business Suite Projects (PA) module. It presents a denormalized, query-ready representation of change impact records associated with project control items. In Oracle Projects terminology, a "control item" (CI) is a change-management construct that groups a change together with its impacted entities, approvals, and historical rollup. The PA_CI_IMPACTS table stores the individual impact lines that hang off a control item — each line describing what type of impact occurred, its current status, its implementation details, and (optionally) the specific project task affected. The view enriches that raw data by decoding lookup codes and status codes into human-readable meanings and by outer-joining to PA_TASKS so the impacted task name is available alongside its internal identifier.

The view is marked VALID in the ETRM metadata for both 12.1.1 and 12.2.2 and is documented as part of the Implementation/DBA data set — that is, it is a seeded, supported object that customers may query but not modify. Because it hides the underlying lookup joins and code decodes, it is commonly used in custom reports, Oracle Discoverer/BI Publisher data models, and integration extracts that need to surface change-impact information without reimplementing the PA lookup semantics. The user search term "impacted_task_id" maps directly to one of the view's exposed columns (IMPACTED_TASK_ID), which is why this view is the natural target when that identifier must be resolved to a task name.

Underlying Base Objects

The documented base objects referenced by the view are PA_CI_IMPACTS (synonym), PA_CONTROL_ITEMS (synonym), PA_LOOKUPS (view), PA_PROJECT_STATUSES (synonym), PA_PROJ_ELEMENTS (synonym), and PA_TASKS (synonym). The primary driving table is PA_CI_IMPACTS, aliased PCI. The view joins PCI.IMPACT_TYPE_CODE to PA_LOOKUPS where LOOKUP_TYPE = 'PA_CI_IMPACT_TYPES', producing IMPACT_TYPE_MEANING. It joins PCI.STATUS_CODE to PA_PROJECT_STATUSES constrained to STATUS_TYPE = 'CI_IMPACT', producing the STATUS column. PA_CONTROL_ITEMS is joined on CI_ID, confirming the control-item relationship. PA_TASKS is outer-joined via PT.TASK_ID (+) = PCI.IMPACTED_TASK_ID, which allows impact rows with no affected task to be returned without losing rows. PA_PROJ_ELEMENTS is referenced in the metadata, consistent with the task's position within the project element hierarchy. All joins except the task join are inner, so an impact row is only returned when matching lookup and status definitions exist.

Key Columns

• CI_IMPACT_ID — primary key of the impact line; unique per impact record.
• CI_ID — foreign key to the parent control item in PA_CONTROL_ITEMS.
• IMPACT_TYPE_CODE / IMPACT_TYPE_MEANING — coded and decoded impact category from the PA_CI_IMPACT_TYPES lookup.
• STATUS_CODE / STATUS — coded and decoded status of the impact, drawn from PA_PROJECT_STATUSES for status type CI_IMPACT.
• IMPACTED_TASK_ID / IMPACTED_TASK_NAME — the task identifier and its name; the name is null when the impact is not task-specific, because of the outer join.
• DESCRIPTION, IMPLEMENTATION_DATE, IMPLEMENTED_BY, IMPLEMENTATION_COMMENT — narrative and audit fields describing how and when the impact was implemented.
• RECORD_VERSION_NUMBER — optimistic locking version used by the PA forms.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The most frequent use is resolving a control-item impact to its affected task, and reporting all impacts for a control item with decoded statuses. A representative query follows:

SELECT ci_impact_id, ci_id, impact_type_meaning, status,
       impacted_task_id, impacted_task_name, implementation_date
FROM  apps.pa_ci_impacts_v
WHERE  ci_id = :p_ci_id
ORDER BY ci_impact_id;

To find every control-item impact that touches a given task:

SELECT ci_id, ci_impact_id, impact_type_meaning, status
FROM  apps.pa_ci_impacts_v
WHERE  impacted_task_id = :p_task_id;

Analysts also aggregate open impacts by type and status across a project portfolio, filter on IMPLEMENTATION_DATE for period reporting, and join CI_ID back to PA_CONTROL_ITEMS for change-request context. Because the view is APPS-owned and VALID, it is safe to query directly in custom reports; however, no DML should ever be issued against it.