Search Results wbs_sort_order




Overview
Explore in AI Chat

Overview

APPS.POR_TASK_LOV_V is a lightweight Oracle EBS view that exposes a list-of-values (LOV) style result set for project tasks, primarily for use by purchasing and requisitioning forms. It presents the WBS task number, an indented task name suitable for hierarchical display, scheduling dates, a chargeable indicator, the internal task identifier, a fixed enabled task level, the owning project identifier, and the WBS sort order. In the context of Oracle EBS 12.1.1 and 12.2.2, the view serves as the data source behind task selection lists in purchasing-related modules, where users pick a valid task against which expenditures, requisition lines, or purchase order distributions are charged. Because it is a view rather than a table, it carries no storage of its own and reflects the current state of the underlying project task structures at query time. Its name prefix, POR, associates it with the purchasing family of objects, while its body draws entirely from project accounting objects.

Underlying Base Objects

The documented base objects referenced by this view are FND_PROFILE (PACKAGE), PA_TASKS_EXPEND_V (VIEW), PA_TASK_UTILS (PACKAGE), and PA_UTILS4 (PACKAGE). The view definition itself is a simple projection over PA_TASKS_EXPEND_V, selecting TASK_NUMBER, INDENTED_TASK_NAME, START_DATE, COMPLETION_DATE, a DECODE against CHARGEABLE_FLAG, TASK_ID, the literal value 2 aliased as "enabled_task_level", PROJECT_ID, and WBS_SORT_ORDER. The dependency on FND_PROFILE, PA_TASK_UTILS, and PA_UTILS4 arises indirectly, since PA_TASKS_EXPEND_V and the task-related logic it embodies rely on these packages and the profile option framework to resolve security and functional behavior. Consequently, query performance and result content depend on how PA_TASKS_EXPEND_V is resolved for the querying user, including any operating unit or security profile context applied through the profile package.

Key Columns

  • TASK_NUMBER — The user-facing identifier of the task, typically a concatenated WBS number used for display and selection.
  • INDENTED_TASK_NAME — The task name padded or prefixed to reflect hierarchy, enabling indented WBS presentation in LOV windows.
  • START_DATE / COMPLETION_DATE — Scheduled or actual task start and completion dates, useful for validity checks during selection.
  • CHARGEABLE — Derived via DECODE(CHARGEABLE_FLAG,'Y','*',NULL), returning an asterisk when the task is chargeable and NULL otherwise.
  • TASK_ID — The internal primary key of the task, used to store the selected value in the calling form.
  • ENABLED_TASK_LEVEL — A constant value of 2, consumed by the LOV logic to control which task levels are selectable.
  • PROJECT_ID — The identifier of the parent project, enabling filtering and joins back to project tables.
  • WBS_SORT_ORDER — The ordering key that enforces correct hierarchical sequencing of tasks in the list; this is the column associated with the user search term "wbs_sort_order."

Common Use Cases and Queries

Typical usage is to populate a task LOV filtered by project, ordering results by the WBS sort order so that the indented structure appears correctly. A sample query follows:

  • SELECT task_number, indented_task_name, chargeable, task_id, project_id, wbs_sort_order FROM apps.por_task_lov_v WHERE project_id = :project_id ORDER BY wbs_sort_order;
  • SELECT task_number, completion_date FROM apps.por_task_lov_v WHERE chargeable = '*' AND start_date <= SYSDATE;
  • SELECT task_id, project_id FROM apps.por_task_lov_v WHERE task_number LIKE :search_term ORDER BY wbs_sort_order;

Reporting extensions frequently join POR_TASK_LOV_V to purchasing distributions or project expenditure tables on TASK_ID and PROJECT_ID to attribute commitments and actuals to the correct WBS element. Because the view exposes ENABLED_TASK_LEVEL as a constant 2, any custom logic that depends on task-level restrictions should be validated against the calling form's expectations in both 12.1.1 and 12.2.2, where the underlying PA_TASKS_EXPEND_V behavior is consistent but security context may vary by responsibility.