Search Results pa_ci_impact_type_usage_pk

Overview

The PA_CI_IMPACT_TYPE_USAGE table is a core setup table within the Oracle E-Business Suite Projects module (PA), specifically for the Control Items functionality. It defines the permissible relationships between Control Item types (or type classes) and the various impact types that can be associated with them. In essence, it acts as a configuration matrix, governing which types of impacts—such as schedule, cost, or scope changes—are applicable and can be recorded for a given Control Item classification. This setup is fundamental to ensuring data integrity and enforcing business rules during the creation and management of Control Items, which are used to track changes, issues, and other project events.

Key Information Stored

The table primarily stores configuration mappings. Its critical columns include a unique identifier (CI_IMPACT_TYPE_USAGE_ID) and the columns that define the mapping rule. As explicitly noted in the documentation, only one of two key columns can be populated for any given row: CI_TYPE_CLASS_CODE (to apply the rule to a broad class of Control Item types) or CI_TYPE_ID (to apply the rule to a specific Control Item type, as defined in PA_CI_TYPES_B). This design allows for flexible setup at either a granular or categorical level. The table will also contain a column (or columns) to store the specific IMPACT_TYPE_CODE(s) that are allowed for the associated type or class, thereby defining the valid impact options.

Common Use Cases and Queries

The primary use case is administrative setup and validation. During the creation or update of a Control Item, the application references this table to present only the relevant, pre-configured impact types to the user. A common reporting need is to audit the setup configuration. A sample query might join this table to PA_CI_TYPES_B to list all impact types enabled for specific Control Item types:

• SELECT cit.NAME ci_type_name, imp.* FROM pa_ci_impact_type_usage imp, pa_ci_types_b cit WHERE imp.ci_type_id = cit.ci_type_id ORDER BY cit.NAME;

Conversely, a query might be used to find all Control Item types or classes that are configured for a particular impact type, which is useful for impact analysis during a business process change.

Related Objects

This table has defined relationships with other key Control Item setup tables. As per the provided metadata:

• Primary Key: PA_CI_IMPACT_TYPE_USAGE_PK on column CI_IMPACT_TYPE_USAGE_ID.
• Foreign Key (References): The table contains a foreign key relationship where PA_CI_IMPACT_TYPE_USAGE.CI_TYPE_ID references PA_CI_TYPES_B. This ensures that any usage rule defined for a specific type ID must correspond to a valid record in the master Control Item types table.

While not listed in the provided excerpt, this table is also logically related to tables storing impact instances (e.g., PA_CI_IMPACTS) which would rely on the rules defined here, and to the lookup tables defining the valid list of impact type codes and CI type class codes.