Search Results ci_canceled

Overview

APPS.PA_CI_CRPRJ_LIST_V is a reporting view in Oracle EBS Projects (PA) that consolidates project control item (change request / CI) header data with related project, status, classification, and financial-plan information. Control items represent change requests, issues, and similar project events tracked against a project. The view is designed as a flattened, denormalized read layer so that forms, concurrent programs, and ad-hoc reports can retrieve a full CI record without joining the underlying transactional tables directly.

The name element "CRPRJ" reflects its purpose: a change-request-to-project listing. The view joins control item records to project attributes (segment1, name, long name, status), CI type metadata, owner party, resolution and classification codes, priority lookup meanings, and aggregated financial-plan amounts. This makes it suitable both for list-style UI regions and for operational reporting on open change requests across a portfolio of projects.

Because the view is secured through PA_CI_SECURED_V and the PA_CI_SECURITY_PKG package, visibility is automatically restricted according to the CI security model, making it safe for use in user-facing queries without additional row-level filtering. The presence of the "ci_canceled" search term in relation to this view reflects the view's explicit handling of the CI_CANCELED status code.

Underlying Base Objects

The view is defined over a documented set of base objects. The primary transactional source is PA_CONTROL_ITEMS (synonym), aliased as ci, which supplies the change request identifier, summary, description, status, priority, price, and source-tracking columns. Project attributes come from PA_PROJECTS_ALL (alias ppa), joined on ci.project_id. Status decoding joins PA_PROJECT_STATUSES twice: once for the CI status (status) and once for the progress status (pro_status).

CI type information is drawn from PA_CI_TYPES_B and PA_CI_TYPES_TL (aliases citypeb and citypetl), supplying the type class, short name, and approval-required flag. Owner names come from HZ_PARTIES (alias owner). Classification and resolution codes reference PA_CLASS_CODES and PA_LOOKUPS (aliases classification, reason, priority_lkp). Element name and number columns are derived by calls to the PA_PROJ_ELEMENTS_UTILS package. Financial-plan quantities and costs come from the PA_FP_CI_AMOUNTS_V view (alias fp), and optional secured access is provided through PA_CI_SECURED_V with PA_CI_SECURITY_PKG.

Key Columns

• PROJECT_ID, SEGMENT1, NAME, LONG_NAME — project identity and display attributes; a concatenated NAME(SEGMENT1) form is also projected.
• CI_ID, CI_NUMBER — the control item's surrogate and user-visible identifiers.
• STATUS_CODE, PROJECT_STATUS_NAME, PROJECT_SYSTEM_STATUS_CODE — CI lifecycle status; notable values include CI_CLOSED and CI_CANCELED. The status decode is used to null out aging columns for closed and canceled items.
• DATE_REQUIRED, DATE_CLOSED, CLOSED_BY_ID — key dates and the closing user.
• RESOLUTION, CLASS_CODE, PRIORITY_CODE, PRIORITY_MEANING — classification and prioritization of the request.
• OWNER_ID, PARTY_NAME — the responsible party.
• OBJECT_TYPE, OBJECT_ID — identifies whether the CI is at project level or bound to a specific project element; element name/number are resolved via PA_PROJ_ELEMENTS_UTILS.
• PRICE, PRICE_CURRENCY_CODE — commercial value of the request.
• PROGRESS_STATUS_CODE, PROGRESS_AS_OF_DATE — progress tracking against the item.
• Effort-level and financial-plan columns (EST_QUANTITY, LABOR_QUANTITY, EST_PROJECT_RAW_COST, TOTAL_PROJECT_RAW_COST, EST_PROJECT_BURDENED_COST, EST_PROJECT_REVENUE, etc.) — planning amounts sourced from PA_FP_CI_AMOUNTS_V.
• CREATION_DATE, LAST_UPDATE_DATE, RECORD_VERSION_NUMBER — audit and optimistic-locking columns.

Common Use Cases and Queries

A frequent requirement is to exclude closed and canceled control items from an operational list. The view's status decode supports this directly:

SELECT ci_number, segment1, name, status_code, date_required, priority_meaning
FROM   apps.pa_ci_crprj_list_v
WHERE  status_code NOT IN ('CI_CLOSED','CI_CANCELED')
AND    project_id = :p_project_id
ORDER BY date_required;

Portfolio reporting of canceled change requests is equally straightforward, since the view retains canceled items rather than filtering them out:

SELECT segment1, name, ci_number, summary, date_closed, party_name
FROM   apps.pa_ci_crprj_list_v
WHERE  status_code = 'CI_CANCELED'
AND    creation_date >= :p_from_date;

Because the view already resolves element names, owner party names, priority meanings, and financial-plan amounts, it is commonly used as the data source for change-request dashboards and for integration extracts feeding external workflow or approval systems. In EBS 12.1.1 and 12.2.2 the view remains application-owned (APPS) and is referenced through the PA_CI_SECURED_V security wrapper, so query results are automatically constrained by the CI security profile of the executing user.