Search Results implementable_flag

Overview

APPS.PA_CI_STATUSES_V is a read-only database view in the Oracle E-Business Suite Applications (APPS) schema that consolidates control item type definitions with their associated project status attributes for Oracle Projects. The view is marked as Oracle Internal Use Only; Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. It is registered in the FND design data repository as PA.PA_CI_STATUSES_V and holds a VALID status across the 12.1.1 and 12.2.2 releases. The view is documented under the ETRM metadata with the internal view type designation.

The view serves as a denormalized reporting and integration surface for control item types, their multilingual names and descriptions, active date ranges, and the project status context in which a control item applies. Because it exposes the IMPLEMENTABLE_FLAG column—central to implementing project control items and financial plan control items—it is frequently referenced by Oracle Projects' internal APIs and utility packages rather than by end-user reporting tools.

Underlying Base Objects

The dependencies list documents that PA_CI_STATUSES_V is defined over the following base objects:

• APPS.PA_CI_TYPES_B — the base table storing control item type definitions (synonym).
• APPS.PA_CI_TYPES_TL — the translation table supplying language-specific NAME and DESCRIPTION (synonym).
• APPS.PA_CONTROL_ITEMS_UTILS — a package providing control item utility logic referenced by the view definition.
• APPS.PA_LOOKUPS — a view supplying lookup code meanings, including MEANING for the CI_TYPE_CLASS_CODE.
• APPS.PA_OBJ_STATUS_LISTS — a synonym exposing object status list associations.
• APPS.PA_PROJECT_STATUSES — a synonym holding project status definitions and system status mappings.
• APPS.PA_STATUS_LISTS_V — a view presenting status list headers.
• APPS.PA_STATUS_LIST_ITEMS — a synonym storing individual status list items.

The view joins these sources to combine control item type metadata with the project status codes and names under which each type is valid.

Key Columns

• CI_TYPE_ID (NUMBER) — system-generated primary identifier for the control item type.
• CI_TYPE_CLASS_CODE (VARCHAR2 30) — lookup code classifying the control item type.
• MEANING (VARCHAR2 80) — translated meaning of the class code from PA_LOOKUPS.
• NAME (VARCHAR2 150) — control item type name from the translation table.
• START_DATE_ACTIVE / END_DATE_ACTIVE (DATE) — effective date range of the type.
• PROJECT_STATUS_CODE (VARCHAR2 30) — project status code associated with the control item.
• PROJECT_SYSTEM_STATUS_CODE (VARCHAR2 30) — internal system status code.
• PROJECT_STATUS_NAME (VARCHAR2 80) — user-facing project status name.
• DESCRIPTION (VARCHAR2 255) — translated description of the control item type.
• IMPLEMENTABLE_FLAG (VARCHAR2 4000) — flag indicating whether the control item/status combination is implementable.

Common Use Cases and Queries

The view is referenced by PA_CI_ACTIONS_PVT, PA_CONTROL_ITEMS_PVT, PA_CONTROL_ITEMS_WORKFLOW, PA_FIN_PLAN_TYPES_UTILS, and PA_FP_CONTROL_ITEMS_UTILS. A typical query retrieves implementable control item types together with their project status context:

• SELECT ci_type_id, name, project_status_code, project_status_name, implementable_flag FROM apps.pa_ci_statuses_v WHERE implementable_flag = 'Y'
• SELECT ci_type_id, ci_type_class_code, meaning, name FROM apps.pa_ci_statuses_v WHERE start_date_active <= SYSDATE AND (end_date_active IS NULL OR end_date_active >= SYSDATE)

These patterns support validation during control item implementation and financial plan configuration. Direct ad-hoc use should be limited, as the object is intended for Oracle Applications internal consumption.