Search Results pa_ci_types_b

Overview

The PA_CI_TYPES_B table is a core repository for control item type definitions within Oracle E-Business Suite Projects (PA) module, specifically for versions 12.1.1 and 12.2.2. It functions as a master reference table, enabling the classification and management of control items—key project management objects used to track changes, issues, actions, and other project-related events. As a base table (denoted by the "_B" suffix), it stores the fundamental, non-language-dependent attributes of a control item type. The data within this table is not seeded by Oracle but is defined and maintained by the customer, allowing for a highly customized implementation of the control items functionality to align with specific organizational processes and governance requirements.

Key Information Stored

The primary data stored in PA_CI_TYPES_B centers on the unique identification and categorization of a control item type. The most critical column is the CI_TYPE_ID, which serves as the primary key and unique numeric identifier for each type record. Another significant column is REASON_CATEGORY, which links the control item type to a broader classification reason category via a foreign key relationship to the PA_CLASS_CATEGORIES table. While the full column list is not detailed in the provided metadata, typical attributes in such a base table would include creation and last update dates, the user who created the record, and other descriptive codes. The language-specific names and descriptions for these types are stored in the corresponding translated table, PA_CI_TYPES_TL.

Common Use Cases and Queries

This table is primarily referenced for setup validation, reporting, and as a constraint in transactional data entry. A common use case is generating a list of all active control item types available for assignment to a project. Administrators may query this table to audit setup or before creating new types to avoid duplication. Sample SQL to retrieve basic type information often involves a join to its translated table for the descriptive name:

• SELECT b.CI_TYPE_ID, tl.NAME, b.REASON_CATEGORY FROM PA.PA_CI_TYPES_B b, PA.PA_CI_TYPES_TL tl WHERE b.CI_TYPE_ID = tl.CI_TYPE_ID AND tl.LANGUAGE = USERENV('LANG');

Another frequent pattern is using the CI_TYPE_ID as a filter or join condition when reporting on transactional control items from the PA_CONTROL_ITEMS table to group items by their type.

Related Objects

PA_CI_TYPES_B is central to the control items data model, with several key foreign key relationships documented in the ETRM metadata. The PA_CONTROL_ITEMS table references it via CI_TYPE_ID, making the type definition a mandatory parent for every control item created. Setup and implementation tables also depend on it: PA_CI_TYPE_USAGE controls which project types can use a given control item type, PA_CI_IMPACT_TYPE_USAGE defines allowed impact types, and PA_CI_SUPPLIER_DETAILS holds supplier-related attributes for a type. Furthermore, it is referenced by PA_PT_CO_IMPL_STATUSES for implementation statuses and by PA_OBJ_STATUS_LISTS (via the PCB_CI_TYPE_ID column) for status lists, highlighting its role in workflow and status tracking. As noted, it also has a foreign key to PA_CLASS_CATEGORIES on the REASON_CATEGORY column for classification.