Search Results task_details

Overview

APPS.PA_ONLINE_TASKS_V is a reporting view in Oracle E-Business Suite that exposes project task information for online, list-of-values style display. It is defined in the APPS schema and is listed in ETRM documentation for both 12.1.1 and 12.2.2. The view consolidates task-level attributes across the Oracle Projects tables and filters the returned rows according to the profile option PA_TASKS_DISPLAYED, read at query time through FND_PROFILE.VALUE. Because the profile is resolved dynamically inside the view definition, the set of tasks visible to a user can vary by responsibility or user without any change to the underlying SQL. The view is commonly accessed by Oracle Projects forms and by custom reporting or integration code that must present a task selection list consistent with the standard application behavior.

Underlying Base Objects

The view is defined as a UNION of two SELECT statements. The documented base objects are PA_TASKS, PA_PROJECTS_ALL, PA_IMPLEMENTATIONS, PA_LOOKUPS, PA_ALTERNATE_TASKS, PA_RBS_ELEMENTS, the PA_TASK_UTILS package, and the FND_PROFILE package (referenced as synonyms or views in the APPS schema). PA_TASKS supplies the core task attributes, while PA_PROJECTS_ALL provides the project number via SEGMENT1 and the CBS_ENABLE_FLAG that controls which branch of the UNION applies. PA_IMPLEMENTATIONS supplies ORG_ID, which is joined to the project operating unit unless the task permits cross-charging. PA_LOOKUPS, with lookup type PA_TASKS_TO_DISPLAY, drives the filtering of chargeable-only, all, or lowest-level tasks; PA_TASK_UTILS.CHECK_CHILD_EXISTS is invoked for the 'LOWEST' option. The second SELECT branch additionally joins PA_ALTERNATE_TASKS and PA_RBS_ELEMENTS to expose CBS element and cost code information for projects where CBS is enabled.

Key Columns

The view exposes PROJECT_ID, PROJECT_NUMBER, TASK_ID, TASK_NUMBER, TASK_NAME, START_DATE, COMPLETION_DATE, CHARGEABLE_FLAG, BILLABLE_FLAG, ORG_ID, TASK_DETAILS, and TASK_MANAGER_PERSON_ID. TASK_DETAILS concatenates the task number and name for display. The alternate-task branch also returns CBS_ELEMENT_ID, COST_CODE, and COST_CODE_NAME, together with the base TASK_ID and TOP_TASK_ID that identify the parent task in the hierarchy. These columns support both simple lookup lists and reporting that must distinguish top-level tasks from their children.

Common Use Cases and Queries

Typical usage includes populating task list-of-values on expenditure and billing forms, driving custom inquiry pages, and validating task identifiers in interface programs. A basic query follows:

• SELECT task_id, task_number, task_name, task_details FROM apps.pa_online_tasks_v WHERE project_id = :project_id ORDER BY task_number;
• SELECT project_number, task_number, chargeable_flag, billable_flag FROM apps.pa_online_tasks_v WHERE org_id = :org_id AND chargeable_flag = 'Y';
• SELECT task_id, cost_code, cost_code_name FROM apps.pa_online_tasks_v WHERE project_id = :project_id AND cost_code IS NOT NULL;

Because PA_TASKS_DISPLAYED is evaluated during execution, users should confirm the profile setting in the target responsibility before relying on row counts. Performance is generally acceptable for single-project lookups, but the UNION and function call in the WHERE clause make set-based, all-project extracts more expensive and better suited to a materialized staging table when large volumes are required.