Search Results pa_task_displayed

Overview

APPS.PJM_TASKS_MTLL_V is a reporting view in Oracle EBS Projects (PA) that exposes a filtered, display-ready list of project tasks. Its name and definition tie it directly to the profile-driven selection of tasks shown in Oracle Project Manufacturing and related task-loV (list of values) contexts. The view materializes the decision logic for which tasks should be presented to the user, driven by the PA_TASKS_TO_DISPLAY lookup type and the PA_TASKS_DISPLAYED profile option.

The view's defining behavior is the PA_TASKS_TO_DISPLAY lookup, whose code value (resolved through FND_PROFILE.VALUE('PA_TASKS_DISPLAYED'), defaulting to 'ALL') determines whether the view returns an indicator column: for 'ALL' every row gets '*'; for 'CHARGEABLE' only chargeable tasks (CHARGEABLE_FLAG = 'Y') get '*'; for 'LOWEST' only tasks with no child tasks (checked via PA_TASK_UTILS.CHECK_CHILD_EXISTS) get '*'. This makes the view a server-side implementation of task-display filtering rather than a simple join projection.

Underlying Base Objects

The view is defined over four documented base objects:

• PA_TASKS (SYNONYM) — aliased T; the source of task rows and columns PROJECT_ID, TASK_ID, TASK_NUMBER, TASK_NAME, and CHARGEABLE_FLAG.
• PA_LOOKUPS (VIEW) — aliased LU; provides the LOOKUP_CODE that resolves the active display mode via the PA_TASKS_TO_DISPLAY lookup type.
• FND_PROFILE (PACKAGE) — supplies FND_PROFILE.VALUE('PA_TASKS_DISPLAYED'), the runtime profile that selects the lookup code.
• PA_TASK_UTILS (PACKAGE) — its CHECK_CHILD_EXISTS function supports the 'LOWEST' branch by determining whether a task has subordinate tasks.

Because the join to PA_LOOKUPS is not correlated to a specific task, the view effectively multiplies or filters based on the single resolved lookup row, so the active profile value governs the entire result set.

Key Columns

• PROJECT_ID — the project identifier owning the task.
• TASK_ID — the unique task identifier; used as the join key in downstream integrations.
• TASK_NUMBER — the user-facing task number.
• TASK_NAME — the descriptive task name.
• DECODE(...) — the unnamed indicator column returning '*' or NULL, signifying whether the task qualifies for display under the current PA_TASKS_DISPLAYED mode. This column is the practical output of the view.

Common Use Cases and Queries

The view is typically consumed by task list-of-values and Project Manufacturing forms that must respect the PA_TASKS_DISPLAYED profile. A representative query retrieves displayable tasks for a project:

SELECT task_number, task_name, task_id
FROM apps.pjm_tasks_mtll_v
WHERE project_id = :p_project_id;

To isolate only tasks the view marks for display, filter on the DECODE output (commonly treated as the last, unnamed column or wrapped in an inline view). Integration and reporting developers query this view instead of PA_TASKS directly when they must replicate the exact EBS task-filtering semantics. Note that its output changes with the session's profile value, so results are non-deterministic across users unless the profile is pinned.