Search Results create_action_flag




Overview
Explore in AI Chat

Overview

APPS.PA_CI_SECURED_V is an Oracle E-Business Suite internal database view owned by the APPS schema. In the ETRM metadata it is registered as a VIEW with status VALID, mapped to the FND Design Data object PA.PA_CI_SECURED_V. The view is explicitly flagged as "Oracle Internal Use Only," meaning Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Its internal view type designation reinforces that it is a supporting construct consumed by Oracle Project Costing / Project Contracts security logic rather than a published reporting interface.

The view exists to expose control-item rows that have already passed through Oracle Project Costing's security evaluation. Rather than presenting raw control item data, it returns a secured projection that includes action flags, allowing calling forms, concurrent programs, and other internal views to determine whether a given control item may be created or updated in the current user context. The user search term create_action_flag corresponds directly to one of the three columns documented for this view, indicating a specific interest in how creation authorization is surfaced.

Underlying Base Objects

According to the documented dependency information, PA_CI_SECURED_V references the following objects:

  • APPS.PA_CI_SECURITY_PKG (PACKAGE) — the security package that encapsulates the control-item authorization rules.
  • APPS.PA_CI_TYPES_B (SYNONYM) — the base table defining control item types.
  • APPS.PA_CONTROL_ITEMS (SYNONYM) — the primary control item entity table.
  • APPS.PA_PROJECT_STATUSES (SYNONYM) — project status reference data used in security evaluation.

The view therefore sits above the control item and control item type tables, with its security behavior driven by calls into PA_CI_SECURITY_PKG. The reference to PA_PROJECT_STATUSES indicates that project status is a factor in determining the secured action flags returned. Because the dependent objects are registered as synonyms, the resolved base tables reside in the APPS schema alongside the view itself.

Key Columns

The documented column list for PA_CI_SECURED_V contains three columns:

  • CI_ID (NUMBER, length 15) — the unique identifier of the control item, providing the join key back to PA_CONTROL_ITEMS and related entities.
  • CREATE_ACTION_FLAG (VARCHAR2) — a security-derived flag indicating whether the current user is permitted to perform a create action on the control item.
  • UPDATE_FLAG (VARCHAR2) — a security-derived flag indicating whether update action is permitted on the control item.

The two action flags are the functional payload of the view. They are computed rather than stored, which is why the view depends on PA_CI_SECURITY_PKG rather than exposing a simple join. Note that the ETRM column listing does not record explicit lengths for the VARCHAR2 flag columns, so consumers should treat their widths as defined in the underlying package implementation.

Common Use Cases and Queries

The principal consumers of this view are other Oracle-delivered views. The metadata records that PA_CI_CRPRJ_LIST_V and PA_CI_LIST_V reference PA_CI_SECURED_V. This indicates that list-of-values and control item list views overlay the secured action flags to control which rows and actions are presented to users in Project Costing and Project Contracts forms.

The canonical query documented by ETRM is a direct projection of all three columns:

  • SELECT CI_ID, CREATE_ACTION_FLAG, UPDATE_FLAG FROM APPS.PA_CI_SECURED_V;

In practice, this pattern is typically extended with filters on the action flags, for example restricting output to rows where CREATE_ACTION_FLAG indicates create authorization, or joining CI_ID to PA_CONTROL_ITEMS to retrieve descriptive attributes. Because the view is marked internal and unsupported for direct access, any custom use should be limited to diagnostic or read-only investigation, and production logic should rely on the Oracle-supplied views and PL/SQL APIs that already integrate these security checks.