Search Results hz_create

Overview

APPS.PA_CI_ACTIONS_V is a reporting and inquiry view exposed in the Oracle E-Business Suite Applications (APPS) schema. It presents change initiative (CI) action records — that is, the individual actions, tasks, or assignments that make up a change initiative or change control item within Oracle Projects. The view consolidates data from multiple underlying change management and control item entities into a single denormalized presentation layer, exposing transaction identifiers, project context, action status, assignment and ownership details, and derived date metrics such as days until due and days since update.

In Oracle EBS 12.1.1 and 12.2.2 the view carries the FND Design Data name PA.PA_CI_ACTIONS_V and is defined with an internal view type. The view is intended to support change management reporting and workflow integration around change initiatives and their actions. The ETRM metadata explicitly flags it with the Oracle Internal Use Only warning, meaning Oracle does not support direct customer access to Oracle applications data through this object except from standard Oracle Application programs. Customers who require supported change management reporting should prefer documented Oracle Projects APIs and views, and must account for the risk of internal object changes during patching.

Underlying Base Objects

The documented dependency list for PA_CI_ACTIONS_V includes the following base objects: FND_GLOBAL (package), FND_LOOKUPS (view), HZ_PARTIES (synonym), PA_CI_ACTIONS (synonym), PA_CI_COMMENTS (synonym), PA_CI_TYPES_VL (view), PA_CONTROL_ITEMS (synonym), PA_CONTROL_ITEMS_UTILS (package), PA_LOOKUPS (view), PA_PROJECTS_ALL (synonym), PA_UTILS (package).

The core transactional source is PA_CI_ACTIONS, which supplies the change initiative action rows and their identifiers, status codes, assignment references, comment text, record version, and sign-off flags. PA_CI_COMMENTS and PA_CONTROL_ITEMS contribute related comment and control item context. PA_CI_TYPES_VL supplies the change initiative type name and type class code. PA_PROJECTS_ALL provides project name and project context. HZ_PARTIES supplies party name resolution for assignment, creation, and reassignment references. FND_LOOKUPS and PA_LOOKUPS resolve lookup meanings such as status, priority, and action type, while FND_GLOBAL, PA_UTILS, and PA_CONTROL_ITEMS_UTILS are used for session and utility functions invoked within the view definition.

Key Columns

• CONTROL_ITEM (VARCHAR2, 133) — control item identifier associated with the action.
• CI_ACTION_ID, CI_ID, CI_ACTION_NUMBER — primary keys and human-readable numbers for the action and its parent change initiative.
• PROJECT_ID, PROJECT_NAME — project context for the action.
• CI_NUMBER, CI_TYPE_NAME, CI_STATUS_CODE — change initiative number, type, and status.
• PRIORITY_DESCRIPTION, PRIORITY_ORDER — priority of the action.
• SUBJECT, OBJECT_NAME, COMMENT_TEXT, CANCEL_COMMENT — descriptive and comment text.
• CREATION_DATE, DATE_CLOSED, DATE_CANCELED, DATE_REQUIRED — lifecycle dates for the action.
• ACTION_TYPE, ACTION_TYPE_CODE — classification of the action.
• ASSIGN_PARTY_ID, ASSIGN_NAME, CREATE_PARTY_ID, CREATE_NAME — assignment and ownership identity, with CREATE_NAME being the resolved party name of the creator (relevant to the search term "create_name").
• SIGN_OFF_REQUIRED_FLAG, SIGN_OFF_FLAG and their MEANING columns — sign-off indicators.
• REASSIGN_NAME, REASSIGN_CI_ACTION_ID, REASSIGN_CI_ACTION_NUMBER, REASSIGN_TO_ID — reassignment details.
• DAYS_UNTIL_DUE, DAYS_SINCE_UPDATE, LAST_UPDATE_DATE — derived aging metrics.
• RECORD_VERSION_NUMBER, STATUS_CODE, STATUS_MEANING — concurrency and status semantics.

Common Use Cases and Queries

Typical scenarios include listing open change initiative actions by project, tracking aging against required dates, identifying actions created by a specific person, and reporting reassignment history. For example, to list actions with creator identity and due metrics:

SELECT ci_action_number, project_name, subject, ci_type_name, status_meaning, create_name, assign_name, date_required, days_until_due FROM apps.pa_ci_actions_v WHERE days_until_due < 7 ORDER BY days_until_due;

Because the view is an internal Oracle object, it should be queried read-only, and queries should avoid hard-coding column lengths or relying on undocumented behavior. Performance is best supported by filtering on indexed identifiers such as CI_ID or CI_ACTION_ID where available.