Search Results task_status_code




Overview
Explore in AI Chat

Overview

APPS.PA_STRUCT_TASKS_LITE_V is a lightweight reporting view in the Oracle E-Business Suite Projects (PA) module, shipped in release 12.1.1 and 12.2.2 under the APPS schema with FND Design Data registration PA.PA_STRUCT_TASKS_LITE_V. It presents a flattened, denormalized projection of the project structure hierarchy, exposing both the structural (WBS) elements and their associated tasks in a single rowset. Each row represents one project element — a work breakdown structure node or a task — together with its version identity, parentage, sequencing, and descriptive attributes.

The view is classified in the ETRM as Internal and carries the standard Oracle warning that it is not supported for direct customer access except from standard Oracle Applications programs. In practice it is widely consumed by concurrent programs, Oracle Business Intelligence Publisher reports, and custom operational reports that need an efficient read-only listing of the task structure without navigating the full versioning model in PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS. Because it exposes only a curated column set, it performs better than queries assembled directly against the base transaction tables.

Underlying Base Objects

The documented dependencies indicate that PA_STRUCT_TASKS_LITE_V is defined over the following objects, all reached through APPS synonyms except the lookup view:

  • PA_PROJ_ELEMENTS — the master project element record (structure nodes and tasks).
  • PA_PROJ_ELEMENT_VERSIONS — the versioned attributes of each element, including status and version identifiers.
  • PA_TASK_TYPES — the task type definitions that classify task elements.
  • PA_OBJECT_RELATIONSHIPS — the parent/child and structural relationship definitions linking elements within a structure version.
  • PA_LOOKUPS — supplies decoded lookup meanings, including the values surfaced through TASK_STATUS_CODE and related status columns.

The view therefore joins element identity to its current version, resolves the parent structure version through PA_OBJECT_RELATIONSHIPS, and translates coded status values via PA_LOOKUPS. ETRM confirms the view is not referenced by any other database object, so it is a terminal, read-only presentation layer rather than a component of further dependency chains.

Key Columns

Common Use Cases and Queries

Typical usage includes task structure listings, status dashboards, WBS reporting, and interfaces that require a fast enumeration of tasks per project. Because TASK_STATUS_CODE is the searched column, the most frequent query pattern filters on it.

  • List all tasks for a project with their status:
    SELECT wbs_number, element_name, wbs_level, financial_task_flag, task_status_code FROM apps.pa_struct_tasks_lite_v WHERE project_id = :p_project_id ORDER BY display_sequence;
  • Filter to tasks at a specific status (for example, released or approved) within a project.
  • Retrieve the immediate children of a given structure version by filtering DISPLAY_PARENT_VERSION_ID.
  • Identify financial tasks only, using the FINANCIAL_TASK_FLAG predicate.

Consumers should treat the view as internal, avoid DML, and rely on it only for read-only reporting. Any change to the underlying versioning or lookup configuration will be reflected automatically when the view is queried.