Results for “pa_task_progress_reminder_v”

28 results




Overview
Explore in AI Chat

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

Overview

PA_TASK_PROGRESS_REMINDER_V is a PL/SQL-based view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Projects (PA) product family and surfaces projects for which a Task Progress Reminder (TPR) is due. The view is a reminder-generation mechanism rather than a transactional ledger: it identifies project records that are candidates for the Task Progress reporting workflow and exposes the values needed by downstream notification processes. Its design reflects the standard ETRM pattern of a status-gated, date-driven selection view that consolidates project identity, status, and reminder dates into a single queryable structure.

The view is currently VALID and is documented as part of the ETRM reference set. Because it calls a packaged utility function in its projection list, it behaves as a dynamic view whose output depends on both project data and the current system date.

Underlying Base Objects

The view is defined over two synonyms referencing base objects in the APPS schema, plus one package:

The join is on PROJ.PROJECT_ID = LAYOUT.OBJECT_ID, constrained to object type 'PA_PROJECTS' and page type 'TPR'. The predicate NVL(PROJ.START_DATE, SYSDATE) <= SYSDATE excludes projects not yet started, and LAYOUT.NEXT_REPORTING_DATE <= SYSDATE restricts results to reminders that are due.

Key Columns

  • PROJECT_NUMBER — the project segment1 value, the human-readable project identifier used in reporting and notifications.
  • OBJECT_ID — the project ID, mirrored from PA_PROJECTS_ALL.PROJECT_ID and used as the join key to the layout table.
  • OBJECT_TYPE — a literal 'PA_PROJECTS', identifying the owning object class for the reminder.
  • OBJECT_NAME — a concatenation of project name and project number in the form NAME(NUMBER), convenient for reminder subject lines.
  • REMINDER_DATE — sourced from PA_OBJECT_PAGE_LAYOUTS.NEXT_REPORTING_DATE; the date on which the next progress report is expected.
  • PROJECT_STATUS_CODE — the current status of the project, used to determine workflow eligibility.
  • PROJECT_START_DATE — the project start date, used for the not-yet-started exclusion predicate.
  • STATUS_ACTION_ALLOWED — the return value of PA_PROJECT_UTILS.CHECK_PRJ_STUS_ACTION_ALLOWED for action 'PA_TASK_PROGRESS'; effectively a Y/N gate.

Common Use Cases and Queries

The view is typically consumed by reminder and notification processes that need to enumerate projects with an overdue task progress report, and by support and DBA personnel validating reminder configuration.

  • Listing all projects with a currently due progress reminder.
  • Checking which projects have a layout configured (page type TPR) and what their next reporting date is.
  • Confirming that the project status permits the Task Progress action.

Representative query:

SELECT project_number, object_id, object_name, reminder_date, project_status_code, status_action_allowed FROM apps.pa_task_progress_reminder_v WHERE reminder_date <= SYSDATE ORDER BY reminder_date;

A second common pattern filters on status to isolate actionable rows: SELECT object_id, project_number, reminder_date FROM apps.pa_task_progress_reminder_v WHERE status_action_allowed = 'Y' AND project_status_code = 'ACTIVE';

Because the view evaluates CURRENT_DATE and the utility function at query time, results reflect the state of PA_PROJECTS_ALL and PA_OBJECT_PAGE_LAYOUTS at execution, and no rows are returned for projects with a missing TPR layout record.