Search Results created_by_id




Overview
Explore in AI Chat

Overview

APPS.PA_CI_BASIC_CTL_V is a denormalized reporting view over the Oracle Project Management control items subsystem. Control items in Oracle EBS Projects represent tracked action items, issues, change requests, and similar records attached to a project and optionally to a specific project object (task, resource, deliverable, or budget line). The view consolidates the core control item record with descriptive lookups, project context, ownership information, and computed action flags into a single readable result set.

The view is exposed under the APPS schema and is intended for reporting, Oracle Business Intelligence extract queries, and integration interfaces that need control item detail without joining the base PA_CONTROL_ITEMS table to multiple lookup and party tables manually. Because the descriptive values (lookup meanings, party names, currency descriptions) are already resolved, the view is suitable for direct consumption by concurrent programs, BI Publisher data templates, and SOA integrations that must render human-readable control item data. The user-supplied search term "priority_lkp" corresponds to an inline lookup alias used within the view text to resolve ci.priority_code, illustrating that the view maps coded values to their display meanings through PA_LOOKUPS.

Underlying Base Objects

The view is documented as referencing the following base objects:

  • PA_CONTROL_ITEMS — the primary transactional table holding control item rows (alias ci), including identifiers, status, priority, price, source attributes, and audit columns.
  • PA_PROJECTS_ALL — supplies project number (segment1), project name, status code, and start date for the parent project.
  • PA_PROJECT_STATUSES — provides the status name, system status code, and icon indicators used to drive action eligibility and display.
  • PA_CI_TYPES_VL — the control item type definition, contributing type class code, name, short name, and behavior flags such as approval_required_flag and auto_number_flag.
  • PA_CLASS_CODES — referenced through resolution, classification, and reason code identifiers to return class_code values.
  • PA_LOOKUPS — used multiple times as inline lookup sources, including for priority_code, source_type_code, and effort_level_code.
  • HZ_PARTIES — joins for owner, closed-by, and last-modified-by party names, plus the created_by and last_updated_by user names resolved via PA_CONTROL_ITEMS_UTILS.
  • FND_CURRENCIES_TL — supplies the currency description for price_currency_code.
  • PA_CONTROL_ITEMS_UTILS — a PL/SQL package whose functions return object names, user names, and the computed boolean flags closeAllowed, deleteAllowed, and submitAllowed.

Key Columns

Identity and context columns include project_id, segment1 (project number), the concatenated project name and number, ci_id, ci_number, and ci_type_id. Status-related columns include status_code, project_status_name, project_system_status_code, and status_overview. The priority attribute is exposed as priority_code alongside the resolved priority_lkp.meaning, which is the column that satisfies the "priority_lkp" search. Classification, resolution, and reason are represented by their code IDs and resolved class_code values.

Descriptive columns include summary, description, object_type, object_id, and the computed object name. Financial and source data appear as price, price_currency_code, currency description, source_type_code, source_lkp.meaning, source_comment, source_number, source_date_received, source_organization, and source_person. Audit and lifecycle columns include creation_date, last_update_date, created_by, last_updated_by, date_closed, closed_by_id, record_version_number, open_action_num, progress_as_of_date, and last_modification_date. The three computed permission flags—close, delete, and submit allowed—are returned directly from PA_CONTROL_ITEMS_UTILS.

Common Use Cases and Queries

Typical use cases include building an open control item register, filtering by priority for escalation reporting, and suppressing action buttons where permission flags are false. A representative query retrieving high-priority open items is:

  • SELECT segment1, ci_number, summary, priority_lkp_meaning, project_status_name FROM pa_ci_basic_ctl_v WHERE project_id = :p_project_id AND date_closed IS NULL AND priority_lkp_meaning = 'High' ORDER BY date_required;
  • SELECT ci_number, owner_party, date_required, open_action_num FROM pa_ci_basic_ctl_v WHERE project_id = :p_project_id AND close_allowed = 'Y';
  • SELECT ci_id, ci_number, priority_code, priority_lkp_meaning, classification_class_code, resolution_class_code FROM pa_ci_basic_ctl_v WHERE project_id = :p_project_id AND status_code = 'OPEN';

Because action flags and party names are precomputed, the view reduces application-layer logic and is well suited to read-only reporting and interface extraction.