Search Results pa_task_priority_code




Overview
Explore in AI Chat

Overview

APPS.PA_FP_ELIGIBLE_CI_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that identifies control items eligible for financial planning treatment. The view joins control item definitions to their financial plan implementation statuses, impacted project tasks, budget version associations, project statuses, owner party records, and lookup-driven descriptors. Its primary role is to support inquiry and integration scenarios in which users must determine which control items (change requests, issues, and similar project control artifacts) are recognized within a financial plan, what their current implementation status is, and which tasks they affect.

The view is documented as owned by APPS and is present in both ETRM 12.1.1 and 12.2.2. It is not a transactional base object; it is a denormalized convenience layer intended for read-only access, typically surfaced through Oracle Forms inquiry screens, OBIEE/XML Publisher reports, or custom extensions that require a flattened picture of control item planning data.

Underlying Base Objects

The documented base objects underlying the view are HZ_PARTIES, PA_BUDGET_VERSIONS, PA_CI_IMPACTS, PA_CI_TYPES_VL, PA_CONTROL_ITEMS, PA_LOOKUPS, PA_PROJECT_STATUSES, PA_PT_CO_IMPL_STATUSES, and PA_TASKS, most of which are exposed to APPS as synonyms over the corresponding PA schema tables.

  • PA_CONTROL_ITEMS supplies the control item identity, number, type, summary, owner, required date, and priority code.
  • PA_PT_CO_IMPL_STATUSES supplies the financial plan type, version type, status code, and priority code mapping that define implementation eligibility.
  • PA_BUDGET_VERSIONS contributes budget version, version type, and rolled-up quantity, cost, and revenue metrics (labor, equipment, raw cost, burdened cost, revenue, and the partially implemented revenue flag).
  • PA_CI_IMPACTS links control items to impacted tasks where the impact type code equals 'FINPLAN'.
  • PA_TASKS provides the impacted task name and number, concatenated into a single descriptive column.
  • PA_PROJECT_STATUSES and PA_CI_TYPES_VL supply readable status and type descriptions.
  • HZ_PARTIES resolves the owner party name, and PA_LOOKUPS resolves the priority code meaning.

Key Columns

The view exposes identifiers and descriptive attributes required to interpret control item financial planning data. Notable columns include PROJECT_ID, CI_ID, CI_NUMBER, CI_TYPE_ID, NAME, and SUMMARY for control item identity; IMPACTED_TASK_ID and the DECODE-generated task description for task impact; FIN_PLAN_TYPE_ID and BUDGET_VERSION_ID for plan definition; and VERSION_TYPE from both budget and implementation status sources. Financial measures include LABOR_QUANTITY, EQUIPMENT_QUANTITY, TOTAL_PROJECT_RAW_COST, TOTAL_PROJECT_BURDENED_COST, TOTAL_PROJECT_REVENUE, RAW_COST, BURDENED_COST, REVENUE, and REV_PARTIALLY_IMPL_FLAG. Status and classification columns include PROJECT_STATUS_NAME, PROJECT_SYSTEM_STATUS_CODE, and CI_TYPE_CLASS_CODE.

Because the user searched for pa_task_priority_code, the most relevant columns are PRIORITY_CODE and the derived lookup meaning, MEANING, resolved via the outer join on PA_LOOKUPS where LOOKUP_TYPE is 'PA_TASK_PRIORITY_CODE'. This outer join ensures control items without a priority code are retained with a null meaning rather than being excluded.

Common Use Cases and Queries

Typical uses include listing eligible control items for a project, reporting impacted tasks with priorities, and reviewing financial plan amounts tied to approved or partially implemented control items.

  • Filter by PROJECT_ID or CI_ID to inspect a single control item’s financial plan footprint.
  • Report priority distribution using PRIORITY_CODE and MEANING.
  • Identify control items whose revenue is only partially implemented using REV_PARTIALLY_IMPL_FLAG.

Sample query:

SELECT ci_number, name, impacted_task_id, priority_code, meaning, total_project_raw_cost, rev_partially_impl_flag FROM apps.pa_fp_eligible_ci_v WHERE project_id = :p_project_id ORDER BY priority_code, ci_number;