Results for “impacted_task_id”

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

Overview

PA_CI_IMPACTS is a table in the PA (Projects) schema of Oracle E-Business Suite, documented as VALID in releases 12.1.1 and 12.2.2. It stores the impacts identified for a control item, forming part of the project management and control-item tracking functionality within Oracle Projects. Each row represents a discrete impact associated with a control item, capturing its classification, status, the task affected, and the implementation details recorded when the impact is actioned.

The table sits downstream of PA_CONTROL_ITEMS, which supplies the parent control-item context through CI_ID. Impacts are therefore subordinate records, describing how a control item affects project execution, ownership, and implementation status. Status values are validated against PA_PROJECT_STATUSES, and the implementing party is resolved to a party record in HZ_PARTIES. Downstream, PA_CI_SUPPLIER_DETAILS references PA_CI_IMPACTS through CI_IMPACT_ID, indicating that supplier-specific detail may be attached to an individual impact.

Based on the mined foreign-key structure, the heuristic Data Vault classification for this object is satellite-leaning. It should be treated as a modeling suggestion: PA_CI_IMPACTS describes and qualifies a parent control item rather than acting as an independent hub, and it carries descriptive and status attributes that change over time.

Key Information Stored

The documented schema contains 15 columns. The surrogate primary key is CI_IMPACT_ID, enforced by the PA_CI_IMPACTS_PK constraint. Two unique indexes act as business-key candidates: PA_CI_IMPACTS_U1 defines CI_IMPACT_ID as unique, while PA_CI_IMPACTS_U2 defines the composite business key (CI_ID, IMPACT_TYPE_CODE), ensuring that a given control item has at most one impact of each type.

• CI_ID — foreign key to PA_CONTROL_ITEMS; identifies the control item to which the impact belongs.
• IMPACT_TYPE_CODE — classifies the nature of the impact; paired with CI_ID in the composite unique key.
• STATUS_CODE — foreign key to PA_PROJECT_STATUSES; conveys the project-status context of the impact.
• IMPLEMENTED_BY — foreign key to HZ_PARTIES; the party responsible for implementing the impact.
• IMPACTED_TASK_ID — identifies the project task affected by the impact.
• IMPLEMENTATION_DATE — the date the impact was implemented.
• IMPLEMENTATION_COMMENT and DESCRIPTION — free-text fields recording explanatory detail.
• RECORD_VERSION_NUMBER — optimistic-locking / concurrency control column.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting resolves impacts for a control item together with their status and implementing party. A representative query joins the parent and lookup tables:

• Impact inventory per control item: SELECT ci.CI_IMPACT_ID, ci.IMPACT_TYPE_CODE, ci.STATUS_CODE, ci.IMPACTED_TASK_ID FROM PA.PA_CI_IMPACTS ci WHERE ci.CI_ID = :ci_id;
• Impacts with implementing party and status: join HZ_PARTIES on IMPLEMENTED_BY and PA_PROJECT_STATUSES on STATUS_CODE.
• Implementation tracking by date: filter on IMPLEMENTATION_DATE and group by STATUS_CODE for status dashboards.
• Supplier detail rollup: join PA_CI_SUPPLIER_DETAILS on CI_IMPACT_ID to report supplier-specific information per impact.

These patterns support control-item impact analysis, status reporting, and audit reconciliations, with RECORD_VERSION_NUMBER available for optimistic-locking checks during concurrent updates.

Related Objects

• PA_CONTROL_ITEMS — parent table; joined via PA_CI_IMPACTS.CI_ID = PA_CONTROL_ITEMS.CI_ID.
• PA_PROJECT_STATUSES — lookup for STATUS_CODE.
• HZ_PARTIES — resolves IMPLEMENTED_BY to a trading party.
• PA_CI_SUPPLIER_DETAILS — child table referencing CI_IMPACT_ID; supplies supplier-level detail per impact.
• PA_CI_IMPACTS_PK / PA_CI_IMPACTS_U1 / PA_CI_IMPACTS_U2 — primary key and unique indexes enforcing identity and the CI_ID + IMPACT_TYPE_CODE business key.