Results for “ci_type_class_code”

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

Overview

PA_CI_STATUSES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the Projects (PA) product family and lists all allowable statuses for a given control item type. A control item is a project-level management object — such as a deliverable, issue, change request, or action item — whose lifecycle is governed by a status list. PA_CI_STATUSES_V resolves the relationship between a control item type, the status list assigned to it, and each individual project status that the list permits, exposing them in a single denormalised result set.

Because control item statuses are not stored as flat columns on a single table, the view performs the join work so that reports, integrations, and extensions can retrieve allowable statuses without navigating the underlying normalised model. It is commonly consumed in Oracle Projects reporting, in control item status validation logic, and in interfaces that must present or restrict status values by control item type.

Underlying Base Objects

The view is defined over eight referenced objects, all accessed through APPS synonyms or views:

• PA_CI_TYPES_B — base table holding control item type definitions, including the CI type class code.
• PA_CI_TYPES_TL — translation table supplying the control item type name in the session language.
• PA_LOOKUPS — view providing the meaning of the CI type class code via lookup type PA_CI_TYPE_CLASSES.
• PA_OBJ_STATUS_LISTS — maps an object (here a CI type) to its assigned status list.
• PA_STATUS_LISTS_V — the status list header view.
• PA_STATUS_LIST_ITEMS — the lines of each status list, each carrying a project status code.
• PA_PROJECT_STATUSES — the project status definitions that supply system status code, name, and description.
• PA_CONTROL_ITEMS_UTILS — a PL/SQL package; its function CHECKCIACTIONALLOWED is invoked in the SELECT list to derive the IMPLEMENTABLE_FLAG.

The joins are driven from PA_CI_TYPES_B through PA_CI_TYPES_TL, filtered by the session language via USERENV('LANG'), then linked through PA_OBJ_STATUS_LISTS and PA_STATUS_LISTS_V to PA_STATUS_LIST_ITEMS and finally to PA_PROJECT_STATUSES.

Key Columns

• CI_TYPE_ID — identifier of the control item type.
• CI_TYPE_CLASS_CODE — class of the control item type; its descriptive MEANING is resolved from the PA_CI_TYPE_CLASSES lookup.
• MEANING — the translated lookup meaning for the CI type class.
• NAME — the control item type name in the current language.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective date range of the control item type.
• PROJECT_STATUS_CODE — the allowable project status on the status list.
• PROJECT_SYSTEM_STATUS_CODE — the internal system status code.
• PROJECT_STATUS_NAME and DESCRIPTION — display attributes of the status.
• IMPLEMENTABLE_FLAG — result of PA_CONTROL_ITEMS_UTILS.CHECKCIACTIONALLOWED('CONTROL_ITEM', PROJECT_STATUS_CODE, 'CI_ALLOW_IMPACT_IMPLEMENT'), indicating whether the status permits implementation actions.

Common Use Cases and Queries

Typical uses include building value lists of valid statuses for a control item type, validating status selection in custom forms, and reporting on status lists per control item type. A representative query returns allowable statuses for a specific control item type:

• SELECT ci_type_id, name, project_status_code, project_status_name, implementable_flag FROM apps.pa_ci_statuses_v WHERE ci_type_id = :p_ci_type_id;
• SELECT ci_type_class_code, meaning, project_status_name FROM apps.pa_ci_statuses_v WHERE implementable_flag = 'Y' ORDER BY name, project_status_name;

Because IMPLEMENTABLE_FLAG is computed through a PL/SQL function call, queries returning large result sets may incur per-row execution cost; filtering by CI_TYPE_ID is recommended where possible.