Search Results pa_ci_types_v




Overview
Explore in AI Chat

Overview

PA_CI_TYPES_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the definition of Control Item Types — the configurable categories of project control items used by Oracle Projects to govern, track, and approve control items such as change requests, issues, and action items. The view consolidates the base Control Item Types entity with its translated name and description, its class lookup meaning, its associated classification, reason, and resolution categories, and its linked status list. This consolidation makes the view a single, denormalized reporting source for Control Item Type setup data.

Because it exposes user-facing meaning rather than raw codes, the view is well suited for both reporting and integration. Report developers use it to build value sets and LOVs, while integration developers read it to validate an item type before inserting or updating control records. All access is through the APPS schema, and the view is documented as VALID.

Underlying Base Objects

The view is defined over four documented base objects and three supporting joins. The primary entity is the base table PA_CI_TYPES_B, which stores Control Item Type attributes including the auto-number, approval, resolution, source-attribute, and usage flags. The multilingual table PA_CI_TYPES_TL supplies the language-specific NAME, SHORT_NAME, and DESCRIPTION, restricted to the session language via USERENV('LANG'). The class code is resolved through PA_LOOKUPS using the lookup type 'PA_CI_TYPE_CLASSES'.

Three classification lookups — CLASSIFICATION_CATEGORY, REASON_CATEGORY, and RESOLUTION_CATEGORY — are each outer-joined to PA_CLASS_CATEGORIES so that types without a category assignment still appear. Finally, the status list is obtained by joining PA_OBJ_STATUS_LISTS (filtered to OBJECT_TYPE = 'PA_CI_TYPES' and STATUS_TYPE = 'CONTROL_ITEM') to PA_STATUS_LISTS_V. The joins produce a row per Control Item Type per session language, with a ROWID and ROW_ID exposed from the base table.

Key Columns

Common Use Cases and Queries

Typical scenarios include building a Control Item Type LOV, generating a setup report, validating configuration before an interface load, and confirming which types are currently effective. The following sample returns active Control Item Types with their class and status list:

  • SELECT ci_type_id, name, ci_type_class, start_date_active, end_date_active FROM pa_ci_types_v WHERE (end_date_active IS NULL OR end_date_active >= SYSDATE) ORDER BY name;
  • SELECT ci_type_id, name, approval_required_flag, resolution_required_flag FROM pa_ci_types_v WHERE approval_required_flag = 'Y';

Because the view is a reporting layer, it is read-only; changes must be applied to PA_CI_TYPES_B and PA_CI_TYPES_TL. Joins to PA_CI_TYPES_B via CI_TYPE_ID remain valid for reconciling view output against the underlying configuration.