Results for “pa_ci_impact_types”

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

Overview

The APPS.PA_CI_IMPACTS_V view is a reporting and integration object within the Oracle E-Business Suite Projects (PA) module. It presents denormalized information about Change Impact records associated with project Control Items. The view joins the base impact table PA_CI_IMPACTS to lookup, status, task, and control item sources to expose not only the stored foreign key codes but also their translated meanings. This design allows reporting tools, Oracle Discoverer workbooks, Oracle Business Intelligence Publisher (BI Publisher) reports, and custom integrations to consume change impact data in business-readable terms without requiring additional lookup resolution at runtime.

The view is available in both Oracle EBS 12.1.1 and 12.2.2. In 12.2.2 it is documented as owned by APPS and is exposed to other schemas through the standard APPS synonym layer. Its role is primarily read-only: it supports query and reporting rather than transactional data entry. Because it exposes descriptive attributes such as impact type meaning and status name, it is well suited to end-user reporting and to integrations that must present change impact status and type without embedding lookup joins in every query.

Underlying Base Objects

The view is defined over several documented base objects. The primary driving table is PA_CI_IMPACTS, referenced through its APPS synonym, which stores each change impact row. PA_CONTROL_ITEMS, also a synonym, supplies the parent control item context and links the impact to the change item via CI_ID. PA_LOOKUPS is a view that provides lookup meanings; here it is filtered to LOOKUP_TYPE = 'PA_CI_IMPACT_TYPES', which resolves the impact type code to a meaningful description. This lookup type is the direct linkage to the user's search term "pa_ci_impact_types". PA_PROJECT_STATUSES, a synonym, supplies the status name and is restricted to STATUS_TYPE = 'CI_IMPACT'. PA_TASKS, a synonym, provides the impacted task name and is outer-joined to the impact so that impacts without a task remain in the result set. PA_PROJ_ELEMENTS is also documented as referenced, reflecting the broader project element hierarchy that tasks belong to.

The join conditions are critical: impact type code equals the lookup code; status code equals the project status code with the CI_IMPACT status type; control item CI_ID equals the impact CI_ID; and the impacted task is matched through an outer join (PT.TASK_ID(+) = PCI.IMPACTED_TASK_ID).

Key Columns

• CI_IMPACT_ID — Primary key identifying each impact record.
• CI_ID — Identifier of the parent control item to which the impact belongs.
• IMPACT_TYPE_CODE and IMPACT_TYPE_MEANING — The stored lookup code and its resolved meaning from PA_LOOKUPS for lookup type PA_CI_IMPACT_TYPES.
• STATUS_CODE and STATUS — The stored status code and the resolved project status name limited to the CI_IMPACT status type.
• DESCRIPTION — Free-text description of the impact.
• IMPLEMENTATION_DATE, IMPLEMENTED_BY, IMPLEMENTATION_COMMENT — Fields capturing when, by whom, and with what notes the impact was implemented.
• TASK_ID and TASK_NAME — The impacted task, supplied through the outer join to PA_TASKS.
• RECORD_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit and concurrency columns.

Common Use Cases and Queries

Typical scenarios include listing all impacts for a control item, reporting impacts by type, tracking implementation status, and identifying impacts tied to specific tasks. The following query returns impacts with translated type and status:

SELECT ci_id, impact_type_meaning, status, description, implementation_date, task_name FROM apps.pa_ci_impacts_v WHERE ci_id = :p_ci_id ORDER BY creation_date;

To count impacts by type: SELECT impact_type_meaning, COUNT(*) FROM apps.pa_ci_impacts_v GROUP BY impact_type_meaning;

To find implemented impacts by date range: SELECT ci_impact_id, ci_id, status, implementation_date FROM apps.pa_ci_impacts_v WHERE implementation_date BETWEEN :p_from AND :p_to;