Search Results pa_task_priority_code




Overview
Explore in AI Chat

Overview

PA_FP_ELIGIBLE_CI_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. Its documented purpose is to contain the details of all control orders (also referred to as control items, or CIs) that have a financial impact. The view consolidates information drawn from the control item definition, the budget version, the financial plan implementation status, project status, task, party, and lookup tables, so that a single query returns the set of control items that qualify for financial plan processing.

The name reflects its role: "FP" denotes financial plan, "ELIGIBLE" denotes the filtering condition, and "CI" denotes control item. It acts as an integration and reporting surface rather than a base table, exposing a pre-joined result set for consumers such as financial plan generation, budget version review, and project cost reporting. Because the view filters on the financial plan impact type and joins to version-type and status configuration, it is intended to return only those control items that are genuinely eligible to affect the financial plan for a given project and task combination.

Underlying Base Objects

The view is defined over the following documented objects under the APPS schema: 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, PA_TASKS. The majority are referenced through synonyms, while PA_CI_TYPES_VL and PA_LOOKUPS are views in their own right.

The join structure establishes the eligibility rule. PBV.CI_ID equals PCI.CI_ID, tying budget versions to control items. PCIM.IMPACT_TYPE_CODE is restricted to 'FINPLAN', which is the core financial-impact filter. The status chain links PCI.STATUS_CODE to PPC.STATUS_CODE and then to PCS.PROJECT_STATUS_CODE. Version type is resolved by DECODE (PBV.VERSION_TYPE, 'ALL', PPC.VERSION_TYPE, PBV.VERSION_TYPE) = PPC.VERSION_TYPE, allowing a budget version flagged as 'ALL' to match any configured implementation status version type. Tasks are joined with an outer join (PT.TASK_ID(+) = PCIM.IMPACTED_TASK_ID), so control items with no impacted task are still returned. The owner is resolved to HZ_PARTIES, and the priority lookup join on PA_TASK_PRIORITY_CODE is also an outer join.

Key Columns

Common Use Cases and Queries

The view is typically used to drive financial plan and budget version reporting, showing which control items have financial impact on a project and which task they affect. A common pattern queries by project and version to list eligible control items:

  • SELECT PROJECT_ID, CI_NUMBER, IMPACTED_TASK_ID, RAW_COST, BURDENED_COST, REVENUE FROM APPS.PA_FP_ELIGIBLE_CI_V WHERE PROJECT_ID = :p_project_id ORDER BY CI_NUMBER;
  • Filter by priority and owner: SELECT CI_NUMBER, PROJECT_ID, PROJECT_STATUS_NAME, PRIORITY_CODE FROM APPS.PA_FP_ELIGIBLE_CI_V WHERE PRIORITY_CODE IS NOT NULL;
  • Join to project or task master data using PROJECT_ID and IMPACTED_TASK_ID to enrich downstream reports, since the view itself already resolves task name and number, owner party name, project status, and the priority lookup meaning.

Because the view embeds the FINPLAN impact-type filter and the version-type matching logic, reports can rely on it directly instead of reconstructing those rules against the base tables.