Search Results pa_utils4




Overview
Explore in AI Chat

Overview

The APPS.PA_TASKS_EXPEND_V view, part of the Oracle Projects (PA) module, presents the set of tasks within a given project against which expenditures may be charged. Rather than exposing every task record stored in the underlying PA_TASKS table, the view applies a configurable filtering and presentation layer so that only expendable tasks are surfaced to callers. This makes it the canonical reference for Oracle Projects expenditure entry, reporting, and integration scenarios where a valid, chargeable task must be resolved from a project context.

The view is owned by the APPS schema and is valid in both Oracle E-Business Suite 12.1.1 and 12.2.2. It is a read-only, query-only object. Form-driven expenditure entry, cross-charge processing, and custom reporting frequently rely on this view rather than querying PA_TASKS directly, because it encapsulates the business rule for which tasks are eligible for expenditure charging.

A distinguishing feature is that the view honours the PA_TASKS_DISPLAYED profile option via FND_PROFILE.VALUE. When the profile is set to ALL, all tasks are returned; when set to CHARGEABLE, only tasks whose CHARGEABLE_FLAG equals Y are returned; when set to LOWEST, only leaf tasks (those with no child tasks) are returned. The view also renders an indented task name and a WBS sort order in ALL mode, producing a hierarchical, tree-walked presentation suitable for LOVs and pickers.

Underlying Base Objects

The view is defined over several documented base objects. The primary fact source is PA_TASKS (referenced via synonym), which supplies task attributes such as TASK_ID, TASK_NUMBER, TASK_NAME, dates, flags, rate information, and work type. PA_PROJECTS_ALL (synonym) supplies project-level context including PROJECT_NUMBER (SEGMENT1) and ORG_ID, joined on PROJECT_ID.

PA_LOOKUPS (view) drives the profile-based filtering logic through the lookup type PA_TASKS_TO_DISPLAY. The PA_TASK_UTILS package provides the SORT_ORDER_TREE_WALK function used to build WBS_SORT_ORDER and the CHECK_CHILD_EXISTS function used to identify leaf tasks. The PA_UTILS4 package resolves the work type name and amount type code via GET_WORK_TYPE_NAME and GET_TP_AMT_TYPE_CODE. FND_PROFILE supplies the runtime profile value. PA_IMPLEMENTATIONS and PA_ALTERNATE_TASKS are also documented as referenced, supporting org-level validation and cross-charge logic. The cross-charge predicate allows a task where ALLOW_CROSS_CHARGE_FLAG = Y or where an implementation row exists for the project's organization.

Key Columns

  • PROJECT_ID / PROJECT_NUMBER — project identifier and the user-visible project number.
  • TASK_ID / TASK_NUMBER / TASK_NAME — task identity and descriptive attributes.
  • INDENTED_TASK_NAME — task name padded according to WBS level when the ALL display profile is active, producing a hierarchical label.
  • START_DATE / COMPLETION_DATE — task scheduling dates.
  • CHARGEABLE_FLAG / BILLABLE_FLAG — indicators governing whether the task accepts expenditures and is billable.
  • WBS_SORT_ORDER — sortable key returned by PA_TASK_UTILS.SORT_ORDER_TREE_WALK, truncated to 2000 characters.
  • ALLOW_CROSS_CHARGE_FLAG — controls cross-charge eligibility, also used in the view's join predicate.
  • PROJECT_RATE_DATE / PROJECT_RATE_TYPE — rate determination attributes.
  • WORK_TYPE_ID / WORK_TYPE_NAME / TP_AMT_TYPE_CODE — work type and associated amount type resolution.
  • TASK_DESCRIPTION — descriptive text for the task.
  • ORG_ID — operating unit identifier inherited from PA_PROJECTS_ALL.

Common Use Cases and Queries

The most frequent use is resolving chargeable tasks for a project during expenditure entry or interface validation. A typical query filters by PROJECT_ID and orders by WBS_SORT_ORDER to present a hierarchical task list:

  • SELECT task_number, indented_task_name, chargeable_flag FROM pa_tasks_expend_v WHERE project_id = :p_project_id ORDER BY wbs_sort_order;
  • SELECT project_number, task_name, work_type_name FROM pa_tasks_expend_v WHERE org_id = :p_org_id AND chargeable_flag = 'Y';

Because the view already enforces the profile-driven and cross-charge filters, custom expenditure interfaces can rely on it to reject invalid task combinations, and reporting tools can join it to expenditure fact tables on TASK_ID for consistent, policy-compliant output.