Search Results service_type_m




Overview
Explore in AI Chat

Overview

PA_TASKS_V_O is a Projects (PA) module view in Oracle E-Business Suite that exposes task-level information from the Project Management and Projects accounting schema. According to the ETRM metadata, the view is documented with the descriptor "10Sc only," indicating that it is a legacy object associated with the older Oracle Projects task structure and is not implemented in the reference database from which the metadata was extracted. The metadata explicitly records the implementation status as "Not implemented in this database," meaning that on many 12.1.1 and 12.2.2 instances the view will not exist as a deployed object, even though its definition is catalogued.

The view presents a denormalized, outward-facing projection of a project task, joining the core task record to organization, lookup, employee, and address information. It is intended to serve reporting, inquiry, and integration consumers that require a single row per task with descriptive attributes already resolved, rather than requiring the caller to perform multiple joins.

Underlying Base Objects

The ETRM metadata lists no documented referenced base objects. The view text, however, reveals the principal source table as PA_TASKS (aliased TASK), from which the ROWID is surfaced as ROW_ID and from which the majority of columns are drawn. Supporting joins are implied by the aliases present in the SELECT list: ORG for organization name (resolved from the carrying-out organization), LK for the service type lookup meaning, EMP for the task manager's full name, and ADDR for address components. These correspond to standard Projects and common reference tables such as HR organizations, FND lookups, PER people, and address tables.

Because the documentation records no formal base-object mapping and the view is marked as not implemented, administrators should treat the object as informational for migration and upgrade analysis rather than as a guaranteed runtime dependency.

Key Columns

Common Use Cases and Queries

Typical uses include task inquiry reports, integration extracts feeding external scheduling systems, and migration scripts that must flatten task attributes. A representative query retrieves billable tasks with manager and organization context:

  • SELECT task_id, task_number, task_name, wbs_level, organization_name, task_manager_name, service_type_m, chargeable_flag, billable_flag FROM pa_tasks_v_o WHERE project_id = :project_id ORDER BY wbs_level;

For scheduling analysis, consumers select the date columns to compare early and late start/finish against actual dates. Because the metadata records the object as not implemented in the reference database, deployers should first verify existence via ALL_VIEWS before relying on it in 12.1.1 or 12.2.2 environments; where absent, equivalent results can be assembled directly from PA_TASKS with the corresponding lookups and joins.