Search Results pa_online_tasks_v




Overview
Explore in AI Chat

Overview

PA_ONLINE_TASKS_V is an APPS-owned view in the Oracle E-Business Suite Projects (PA) module. It is documented as a customizable view that supplies task information to the Self Service Time application, Oracle Time Capture, and Self Service Expense. Rather than exposing the full PA_TASKS table, the view presents a filtered, presentation-ready list of tasks that end users may select when recording time or expense entries online. Its definition is deliberately profile-driven, allowing administrators to control which tasks appear to users based on organizational setup.

In EBS 12.1.1 and 12.2.2 the view is classified as VALID and is commonly referenced by Oracle Forms, OAF pages, and time-entry APIs that require a validated list of chargeable or user-selectable tasks. A key element of the design is the TASK_DETAILS column, a concatenation of TASK_NUMBER and TASK_NAME. This is the descriptive label users typically see in task selection lists, and it has historically been a focus of searches and customization requests.

Underlying Base Objects

The view selects from PA_TASKS (T), PA_PROJECTS_ALL (P), PA_IMPLEMENTATIONS (IMP), and PA_LOOKUPS (LU), and it references the packages FND_PROFILE and PA_TASK_UTILS. Documented related objects include PA_ALTERNATE_TASKS and PA_RBS_ELEMENTS, which participate in task and resource list validation in the broader Projects architecture.

  • PA_TASKS provides task-level attributes such as TASK_ID, TASK_NUMBER, TASK_NAME, dates, and the CHARGEABLE_FLAG and BILLABLE_FLAG.
  • PA_PROJECTS_ALL supplies the parent project and SEGMENT1 (PROJECT_NUMBER), joined on PROJECT_ID.
  • PA_IMPLEMENTATIONS supplies ORG_ID; the join permits cross-charge tasks when T.ALLOW_CROSS_CHARGE_FLAG = 'Y' or when the implementation org matches the project org.
  • PA_LOOKUPS with lookup type 'PA_TASKS_TO_DISPLAY' drives the display filter logic.
  • FND_PROFILE.VALUE('PA_TASKS_DISPLAYED') determines whether all tasks, only chargeable tasks, or only lowest-level (leaf) tasks are returned.
  • PA_TASK_UTILS.CHECK_CHILD_EXISTS is used to exclude parent tasks when the 'LOWEST' option is active.

Key Columns

  • PROJECT_ID / PROJECT_NUMBER – Identifiers for the parent project; PROJECT_NUMBER is derived from SEGMENT1.
  • TASK_ID / TASK_NUMBER / TASK_NAME – Core task identifiers and descriptive attributes.
  • START_DATE / COMPLETION_DATE – Task effective dates, useful for date-range validation.
  • CHARGEABLE_FLAG / BILLABLE_FLAG – Indicate whether the task may be charged and billed.
  • ORG_ID – Operating unit context from PA_IMPLEMENTATIONS.
  • TASK_DETAILS – Concatenation "TASK_NUMBER-TASK_NAME", the primary display value. Note that this column carries no index and is generally not ideal for direct filtering.

Common Use Cases and Queries

The view is typically queried to populate LOVs and timecard task selection lists. Filtering by TASK_NUMBER or TASK_ID is recommended over TASK_DETAILS for performance.

  • Retrieve selectable tasks for a project: SELECT task_number, task_name, task_details FROM pa_online_tasks_v WHERE project_id = :p_project_id ORDER BY task_number;
  • Locate a specific task by concatenated label: SELECT task_id, project_number, task_details FROM pa_online_tasks_v WHERE task_details LIKE 'TASK-001%';
  • Validate that only chargeable tasks are returned: the view already applies the CHARGEABLE filter when the PA_TASKS_DISPLAYED profile is set to 'CHARGEABLE'.
  • Reporting on billable tasks by operating unit: SELECT org_id, project_number, task_details, billable_flag FROM pa_online_tasks_v;

Because the view is explicitly customizable, clients may create a replacement view of the same name in a custom schema to alter filtering, additional columns, or display formatting without modifying Oracle-owned objects.