Search Results pa_tasks_amg_v

Overview

PA_TASKS_AMG_V is an Oracle E-Business Suite view owned by the APPS schema within the PA (Projects) product family. It exposes project task and WBS (Work Breakdown Structure) information sourced from the PA_TASKS table. The view is documented in ETRM with the description "10Sc only," indicating that it was originally introduced for the Oracle Projects self-service (10Sc) user interface rather than as a general-purpose reporting object. It remains VALID in both 12.1.1 and 12.2.2, and functions primarily as a convenience layer that presents task rows together with a computed WBS expansion indicator.

Because the view surfaces the full PA_TASKS column set—including the descriptive LONG_TASK_NAME and TASK_NAME fields—it is frequently discovered by users searching for LOV or descriptive query objects that return a task's long name alongside its identifiers. In practice it behaves as a read-only projection over project tasks, useful for integration and lightweight reporting where the complete PA_TASKS attribute set is acceptable.

Underlying Base Objects

The view is defined over two documented base objects:

• PA_TASKS (SYNONYM) — The primary table supplying every persistent column. The view text aliases this table as TASK.
• PA_TASK_UTILS (PACKAGE) — Referenced indirectly through the expression DECODE(PA_TASK_UTILS.CHECK_CHILD_EXISTS(TASK.TASK_ID), 1, '+', 0, ' '), which invokes the package function to determine whether a child task exists for the current row.

The view performs a single-table SELECT from PA_TASKS with no joins, defining ROW_ID as TASK.ROWID and applying the CHECK_CHILD_EXISTS call to produce a dynamic WBS indicator column. There is no aggregation or filtering; the view simply surfaces all task rows with their attributes.

Key Columns

The view exposes the complete PA_TASKS column list plus the derived indicator. Notable columns include:

• ROW_ID / TASK_ID / PROJECT_ID — Row identifier, primary task key, and owning project.
• TASK_NUMBER / TASK_NAME / LONG_TASK_NAME — Task numbering and descriptive naming fields; LONG_TASK_NAME supports extended descriptions.
• TOP_TASK_ID / PARENT_TASK_ID / WBS_LEVEL — WBS hierarchy structure, allowing top-level and parent-child traversal.
• READY_TO_BILL_FLAG / READY_TO_DISTRIBUTE_FLAG / CHARGEABLE_FLAG / BILLABLE_FLAG — Billing and transaction control indicators.
• SERVICE_TYPE_CODE / TASK_MANAGER_PERSON_ID / CARRYING_OUT_ORGANIZATION_ID — Operational and organizational context.
• START_DATE / COMPLETION_DATE / ACTUAL_START_DATE / ACTUAL_FINISH_DATE / EARLY_/LATE_/SCHEDULED_ dates — Planned, actual, and schedule-adjusted date metrics.
• LABOR_ / NON_LABOR_ rate schedule and discount columns — Billing rate configuration.
• REVENUE_ACCRUAL_METHOD / INVOICE_METHOD / CUSTOMER_ID — Revenue and invoicing attributes.
• Attribute1–15 and Attribute_Category — Descriptive flexfield (DFF) values.
• The DECODE(...CHECK_CHILD_EXISTS...) column returns '+' when a child task exists and a space otherwise, enabling WBS tree expansion.

Common Use Cases and Queries

Typical uses center on listing tasks with their long names, identifying hierarchically expandable tasks, and pulling billing or organizational attributes:

• Retrieving tasks by long name for a project.
• Determining which tasks have children, for tree rendering in custom UIs.
• Extracting billing flags and rate schedule identifiers for project reporting.

Sample query:

SELECT task_id, project_id, task_number, long_task_name, wbs_level, ready_to_bill_flag
FROM apps.pa_tasks_amg_v
WHERE project_id = :p_project_id AND long_task_name LIKE '%' || :p_search || '%';

Because the object is documented as "10Sc only," it should be treated as a legacy convenience view rather than a formally recommended reporting interface; for new development, direct querying of PA_TASKS is generally preferable to avoid dependency on an undocumented self-service artifact.