Search Results ci_impact_id

Overview

The PA_CI_IMPACTS table is a core data repository within the Oracle E-Business Suite (EBS) Projects module (PA). It functions as the primary storage entity for impact records associated with control items. In the context of project management, a control item represents a significant event, issue, or change that requires formal tracking. Each impact record stored in this table details a specific consequence, requirement, or action item that has been identified as a direct result of its parent control item. The table's role is to maintain a detailed audit trail of all downstream effects, enabling comprehensive impact analysis, accountability assignment, and status monitoring throughout the project lifecycle in both EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to capture essential details about each impact. The primary key, CI_IMPACT_ID, uniquely identifies every impact record. The critical foreign key column CI_ID links the impact to its originating control item in the PA_CONTROL_ITEMS table. Other significant columns include STATUS_CODE, which references PA_PROJECT_STATUSES to track the impact's progress (e.g., Open, Closed, In Progress), and IMPLEMENTED_BY, which references HZ_PARTIES to record the party responsible for implementing the impact resolution. While the provided metadata does not list all columns, typical data would also include impact descriptions, creation and last update dates, severity or priority indicators, and references to affected project deliverables or tasks.

Common Use Cases and Queries

This table is central to impact management workflows. A common use case is generating a report of all open impacts for a specific control item or project to facilitate review meetings. Another scenario involves querying impacts assigned to a particular resource for workload tracking. Sample SQL patterns include retrieving basic impact information and joining to related tables for a comprehensive view. For example:

• SELECT ci_impact_id, description, status_code FROM pa_ci_impacts WHERE ci_id = :control_item_id ORDER BY creation_date;
• SELECT imp.ci_impact_id, imp.description, ps.name status, hzp.party_name implemented_by_name FROM pa_ci_impacts imp, pa_project_statuses ps, hz_parties hzp WHERE imp.status_code = ps.status_code AND imp.implemented_by = hzp.party_id(+) AND imp.ci_id IN (SELECT ci_id FROM pa_control_items WHERE project_id = :project_id);

Related Objects

As indicated by the foreign key relationships, PA_CI_IMPACTS is integrally connected to several key EBS objects. It is a child table of PA_CONTROL_ITEMS, the master table for control items. Status management is governed through its relationship with the PA_PROJECT_STATUSES table. The assignment of implementation responsibility is linked to the Trading Community Architecture via the HZ_PARTIES table. Furthermore, PA_CI_IMPACTS serves as a parent table to PA_CI_SUPPLIER_DETAILS, which stores additional procurement or supplier-specific information related to an impact. This hierarchy positions PA_CI_IMPACTS as a critical junction point between project control items and detailed execution data.