Search Results indented_task_name

Overview

POR_TASK_LOV_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, delivered as part of the ICX (Oracle iProcurement) product. Its documented purpose is to provide the List of Values (LOV) for tasks within the iProcurement requisition and shopping flow. When a user creates or edits a requisition line and must associate a project task, the task LOV presented in the iProcurement user interface is sourced from this view. The view is designated VALID in the ETRM repository and inherits its APPS ownership, meaning it is referenced through the standard APPS synonym layer rather than being queried directly against the underlying schema.

The view resolves against the project accounting task-expenditure structures exposed by PA_TASKS_EXPEND_V. Rather than exposing raw task records, it projects a curated set of columns tailored for the LOV, including a formatted chargeable indicator. The inclusion of the CHARGEABLE_FLAG-derived column is of particular interest to users who search on the term "chargeable_flag," since this flag determines whether a task is marked chargeable and thus whether it appears with a visual indicator in the LOV.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects for POR_TASK_LOV_V: FND_PROFILE (PACKAGE), PA_TASKS_EXPEND_V (VIEW), PA_TASK_UTILS (PACKAGE), and PA_UTILS4 (PACKAGE). The primary data source is the PA_TASKS_EXPEND_V view in the Projects (PA) module, which supplies task number, indented task name, dates, the chargeable flag, task identifier, project identifier, and WBS sort order. The view text itself performs a straightforward projection with a DECODE transformation on the chargeable flag.

The FND_PROFILE, PA_TASK_UTILS, and PA_UTILS4 packages are referenced to support the dynamic behavior of the underlying task view and LOV logic, including the resolution of profile-driven security and task-level enablement. The view therefore sits at the intersection of the Projects and iProcurement modules: iProcurement consumes the LOV output, while Projects supplies the authoritative task data and the utility logic that governs which tasks are visible and selectable.

Key Columns

• TASK_NUMBER — The task identifier as displayed to the user in the LOV.
• INDENTED_TASK_NAME — The task name with indentation reflecting the WBS hierarchy, giving the LOV its familiar nested presentation.
• START_DATE and COMPLETION_DATE — The task effective date range, used to constrain task validity.
• CHARGEABLE — A derived column produced by DECODE(CHARGEABLE_FLAG, 'Y', '*', NULL). When the underlying chargeable flag equals 'Y', an asterisk is displayed; otherwise NULL is returned. This column is the direct response to searches for "chargeable_flag."
• TASK_ID — The unique task identifier used as the LOV return value for downstream requisition processing.
• ENABLED_TASK_LEVEL — A constant value of 2, exposed to support task-level enablement logic in the LOV.
• PROJECT_ID — The owning project identifier, linking the task to its project context.
• WBS_SORT_ORDER — The ordering sequence that governs how tasks are sorted in the LOV, preserving WBS hierarchy.

Common Use Cases and Queries

This view is commonly queried when diagnosing why a particular task does or does not appear in the iProcurement task LOV, when verifying whether a task is chargeable, and when auditing the task values available for requisition entry. A typical query listing chargeable tasks for a project is:

SELECT task_number, indented_task_name, chargeable, task_id
FROM apps.por_task_lov_v
WHERE project_id = :project_id
ORDER BY wbs_sort_order;

To isolate only chargeable tasks (those flagged with an asterisk), filter on the CHARGEABLE column:

SELECT task_number, indented_task_name, start_date, completion_date
FROM apps.por_task_lov_v
WHERE project_id = :project_id
AND chargeable = '*';

Because the view abstracts the DECODE on CHARGEABLE_FLAG, consumers need not query PA_TASKS_EXPEND_V directly, and the LOV remains consistent with the iProcurement display rules across both 12.1.1 and 12.2.2.