Results for “ci_type_id”

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

Overview

PA_CI_IMPACT_TYPE_USAGE is a configuration table in the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the setup data that defines which impact types are available for a given control item type or control item type class. Control items are used within Oracle Projects to capture project-related issues, changes, and quality records, and the impact types linked to them describe the downstream effects of those items on schedule, cost, scope, or other project dimensions. This table therefore acts as a cross-reference between control item definitions and the impact types that may be applied to them.

A defining constraint of the table is that only one of the two columns CI_TYPE_CLASS_CODE and CI_TYPE_ID can be populated on any given row. A row therefore associates an impact type either with a specific control item type or with an entire control item type class, never both. Under the heuristic Data Vault classification supplied in the metadata, this object is described as satellite-leaning: it behaves primarily as a descriptive, attribute-bearing structure attached to the control item type hub rather than as an independent hub or a pure transactional link.

Key Information Stored

The table is defined in the PA schema and contains eleven documented columns. The most significant are:

• CI_IMPACT_TYPE_USAGE_ID — the surrogate primary key, enforced by PA_CI_IMPACT_TYPE_USAGE_PK. It uniquely identifies each usage setup row.
• CI_TYPE_ID — foreign key to PA_CI_TYPES_B, identifying the specific control item type to which an impact type is assigned when the association is made at type level.
• CI_TYPE_CLASS_CODE — identifies the control item type class when the association is made at class level rather than at individual type level.
• IMPACT_TYPE_CODE — the impact type being made available for the control item type or class; a core business attribute.
• IMPACT_TYPE_CODE_ORDER — controls the display or processing sequence of impact types in the associated LOV or UI.
• ZD_EDITION_NAME — the editioning column used in the 12.2.2 schema to support online patching and multi-edition operation.
• CREATION_DATE, CREATED_BY — standard audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification and the responsible user and session.

Three unique indexes are documented. PA_CI_IMPACT_TYPE_USAGE_U1 is on (CI_IMPACT_TYPE_USAGE_ID, ZD_EDITION_NAME) and effectively mirrors the primary key under editioning. PA_CI_IMPACT_TYPE_USAGE_U2 is on (CI_TYPE_CLASS_CODE, CI_TYPE_ID, IMPACT_TYPE_CODE, ZD_EDITION_NAME), and PA_CI_IMPACT_TYPE_USAGE_U3 is on (CI_TYPE_ID, IMPACT_TYPE_CODE, CI_TYPE_CLASS_CODE, ZD_EDITION_NAME). These two indexes represent the business-key candidates: they prevent duplicate assignment of the same impact type to the same control item type or class within an edition.

Common Use Cases and Queries

The primary use case is setup verification and reporting: confirming which impact types are configured for a control item type or class before users create or update control items. Administrators and support analysts query this table to troubleshoot missing impact type values in the application UI.

• Listing impact types for a specific control item type, joined to PA_CI_TYPES_B on CI_TYPE_ID.
• Listing impact types assigned by class, filtering on CI_TYPE_CLASS_CODE.
• Detecting setup gaps by comparing configured usage rows against the expected impact type set.
• Reconciling impact types across environments during clone, migration, or patching validation.

A representative pattern is: select ciu.impact_type_code, ciu.impact_type_code_order from pa.pa_ci_impact_type_usage ciu where ciu.ci_type_id = :type_id order by ciu.impact_type_code_order. For class-level setup, substitute the CI_TYPE_CLASS_CODE predicate. In 12.2.2 queries, the active edition may be constrained using ZD_EDITION_NAME where edition-aware reporting is required.

Related Objects

• PA_CI_TYPES_B — referenced through CI_IMPACT_TYPE_USAGE.CI_TYPE_ID; provides the control item type definition.
• PA_CI_TYPES_TL — translation table for control item type names, joined through PA_CI_TYPES_B for user-facing reporting.
• PA_CI_IMPACT_TYPES — the impact type definition set referenced by IMPACT_TYPE_CODE.
• PA_CI_IMPACT_TYPE_USAGE_PK — the primary key constraint enforcing uniqueness of CI_IMPACT_TYPE_USAGE_ID.
• PA_CI_IMPACT_TYPE_USAGE_U2 / _U3 — unique constraints enforcing business-key integrity across type, class, and impact type.
• Control item creation and update flows in the Projects UI — these consume the setup data to restrict the impact types selectable by end users.

Because the table is setup-oriented and satellite-leaning, it is typically queried in read-only fashion for validation and reporting rather than updated directly; changes are normally made through the Oracle Projects setup interface.