Results for “task_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_TASKS_AP_V is a reporting view owned by the APPS schema in Oracle E-Business Suite. ETRM documents its product context as AP - Payables, with the description qualified as "(Release 10SC Only)". The release qualifier indicates that the view was catalogued for the older 10SC code line and persists in the 12.1.1 / 12.2.2 data dictionary as a VALID object rather than being dropped. Its continued existence reflects the conservative upgrade behavior of EBS, in which legacy database objects remain available even when the originating release is no longer supported.

Functionally, the view exposes a compact, Payables-facing projection of project task information. Rather than surfacing the full depth of the Projects task model, it presents four columns covering the task identifier, the parent project identifier, the task number, and a description. The view therefore acts as a lightweight lookup that downstream Payables-style reporting can join to without navigating the complete PA_TASKS_EXPEND_V column set.

Underlying Base Objects

The view text is a simple single-source SELECT over PA_TASKS_EXPEND_V, aliased PAT, with column renames applied at the projection layer:

• PA_TASKS_EXPEND_V — the sole FROM-clause object; supplies all four output columns.
• PA_TASK_UTILS (package) — utility routines for task validation and retrieval used in the Projects task model.
• PA_UTILS4 (package) — shared Projects utility package supporting task-related logic.
• FND_PROFILE (package) — profile option access, commonly invoked for multi-org and security context resolution.

The three packages are documented dependencies of PA_TASKS_AP_V in ETRM 12.2.2, reflecting the dependency chain inherited through PA_TASKS_EXPEND_V. The view itself is described as "Release 10SC Only"; sourcing all data from a single Projects view limits exposure to schema changes in the task tables. It is important to note that PA_TASKS_AP_V is a distinct object from PA_TASKS_AP_V2, which is the later-listed variant, so references should be verified against the exact view name in use.

Key Columns

• TASK_ID — sourced from PAT.TASK_ID; the unique system identifier for the task, typically used as the join key to other task-aware views and tables.
• PROJECT_ID — sourced from PAT.PROJECT_ID; identifies the project to which the task belongs, allowing task rows to be grouped or filtered by project.
• TASK — sourced from PAT.TASK_NUMBER; the user-visible task number within the project structure, used for display and reference as an alternative to the internal TASK_ID.
• DESCRIPTION — sourced from INDENTED_TASK_NAME; the formatted task name with indentation preserved to reflect the hierarchical position of the task in its work breakdown structure. This is the column most closely associated with the search term "indented_task_name", which maps to the DESCRIPTION output rather than a standalone column name.

Common Use Cases and Queries

The view is suited to lookups and report joins that require a readable, hierarchical task label keyed to project context. A typical retrieval lists task rows for a given project in indent order:

• Project task listing: SELECT task_id, project_id, task, description FROM apps.pa_tasks_ap_v WHERE project_id = :project_id ORDER BY description;
• Join to task-keyed data: SELECT v.task, v.description, x.* FROM apps.pa_tasks_ap_v v, some_task_table x WHERE x.task_id = v.task_id;
• Ad hoc search: SELECT task_id, project_id, task, description FROM apps.pa_tasks_ap_v WHERE UPPER(description) LIKE UPPER('%' || :search_term || '%');

Because the DESCRIPTION column carries the indented task name, any search for "indented_task_name" should be translated to DESCRIPTION in queries against this view. Reporting on newer functionality should prefer the current Projects task views, but where legacy assets reference PA_TASKS_AP_V the mapping above remains valid.