Results for “program_application_id”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_ADW_CURRENT_TASKS is an Oracle E-Business Suite Applications (APPS) view owned by the Projects (PA) product module. It is classified in the ETRM as a VIEW with VALID status and is documented across EBS releases 12.1.1 and 12.2.2. The view presents a filtered subset of task-related event records that have been flagged for notification to the Applications Desktop Workflow (ADW) process. Specifically, it exposes only those rows in the underlying task history table where the ADW_NOTIFY_FLAG column carries the value 'Y', indicating that the given task event is pending or eligible for ADW notification handling.

Because the view is a simple, thin projection over a single base table with a single Boolean-style filter predicate, its role is primarily that of a convenience and integration object rather than a complex reporting structure. It allows reporting tools, workflow background processes, and custom extensions to retrieve the current set of notifiable project task events without re-implementing the filter logic against PA_TASK_HISTORY. The term "current tasks" in the object name reflects the fact that these are task records of active interest to the ADW interface, not a historical archive of all task activity.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the view is defined over a single referenced base object: PA_TASK_HISTORY, accessed through a synonym in the APPS schema. The view text selects all listed columns from PA_TASK_HISTORY (aliased PTH) and applies the restriction WHERE PTH.ADW_NOTIFY_FLAG = 'Y'. No joins, unions, or aggregations are present in the documented definition, meaning the view is essentially a filtered pass-through of PA_TASK_HISTORY columns.

PA_TASK_HISTORY is the transaction history table for project tasks, capturing changes and events associated with a task such as service type assignments, organization carrying out the work, and parent/top task relationships. Every row in PA_ADW_CURRENT_TASKS therefore corresponds one-to-one with a row in PA_TASK_HISTORY whose ADW notification flag has been set to 'Y'. Because the view does not restrict on dates, status codes, or project, the set of rows it returns depends entirely on the flag value in the base table, and consumers should expect the view to change as the ADW process consumes and clears notified records.

Key Columns

The view exposes the full set of documented PA_TASK_HISTORY columns relevant to ADW processing. Key columns include:

Common Use Cases and Queries

Typical uses include monitoring pending ADW task notifications, feeding workflow or integration routines, and diagnosing why a particular task event has or has not been picked up by the notification process. A basic query lists all currently notifiable task events:

SELECT TASK_HISTORY_ID, TASK_ID, PROJECT_ID, TOP_TASK_ID, SERVICE_TYPE_CODE, CARRYING_OUT_ORGANIZATION_ID, ADW_INTERFACE_FLAG, ADW_NOTIFY_FLAG, CREATION_DATE FROM APPS.PA_ADW_CURRENT_TASKS;

To focus on a single project, add an equality predicate on PROJECT_ID. To correlate with task definitions and project names, join PROJECT_ID and TASK_ID to the corresponding project and task entities. Because the view returns only flagged rows, a common diagnostic idiom is to compare its row count against PA_TASK_HISTORY filtered the same way, confirming the view logic is behaving as documented. All access should be granted through the APPS schema, and queries are typically executed with the standard EBS responsibility and MO: Operating Unit context where relevant.