Results for “adw_notify_flag”

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

Overview

The FII_PA_INTERFACED_TASKS view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the FII (Financial Intelligence) product family. It exposes a filtered, de-duplicated projection of Projects task history records that have been flagged for outbound interface to the Oracle Business Intelligence / Analytics (ADW) layer. The view isolates the most recent task history row per task identifier, ensuring the analytics staging layer receives a single, current snapshot of each task rather than the full audit trail maintained in the underlying transactional table.

This object is relevant in Oracle EBS 12.1.1 and 12.2.2 environments where Financial Intelligence extracts consume project task changes for reporting and notification workflows. It is not a base transactional entity and carries no independent storage; it functions purely as a read-only interface bridge between the Projects application and the downstream analytical model.

Underlying Base Objects

The view is defined solely over a single base table, PA_TASK_HISTORY (aliased PTH in the view text). Although the documented metadata lists no referenced base objects, the view definition confirms an exclusive dependency on PA_TASK_HISTORY. Two filters are applied to that source:

• Rows must carry ADW_INTERFACE_FLAG = 'Y', indicating the record has been marked for interface to the analytics warehouse.
• The row must satisfy a correlated subquery that returns the maximum TASK_HISTORY_ID for each TASK_ID among rows also flagged with ADW_INTERFACE_FLAG = 'Y'.

The net effect is that only the latest flagged history record per task survives into the view, eliminating duplicate or superseded change entries for the same task.

Key Columns

• TASK_HISTORY_ID — Primary surrogate key of the history record; drives the "latest row" selection logic.
• TASK_ID — Foreign reference to the underlying project task; the grouping key for the maximum-history filter.
• PROJECT_ID — Project to which the task belongs, enabling project-level aggregation and joins.
• TOP_TASK_ID — Top-level parent task, supporting task hierarchy rollups.
• SERVICE_TYPE_CODE and CARRYING_OUT_ORGANIZATION_ID — Service and performing organization attributes used for organizational reporting.
• ADW_INTERFACE_FLAG — The gating flag ensuring only interface-eligible rows are returned.
• ADW_NOTIFY_FLAG — Notification indicator used by analytics notification processes.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program execution metadata for audit and lineage.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns.

Common Use Cases and Queries

This view is typically consumed by extract processes that stage project task changes for the analytics warehouse, and by reports that need the latest task state without traversing the full history table. A representative query retrieving the current interfaced tasks for a given project follows:

• SELECT task_id, project_id, top_task_id, last_update_date FROM fii_pa_interfaced_tasks WHERE project_id = :project_id;
• SELECT service_type_code, carrying_out_organization_id, COUNT(*) FROM fii_pa_interfaced_tasks GROUP BY service_type_code, carrying_out_organization_id;
• SELECT task_id, MAX(last_update_date) FROM fii_pa_interfaced_tasks WHERE adw_notify_flag = 'Y' GROUP BY task_id;

Because the view already restricts output to the newest flagged record per task, consumers avoid additional de-duplication logic. It is important to note that rows disappear from the view once superseded, so point-in-time history must be sourced from PA_TASK_HISTORY directly rather than from this object.