Results for “reminder_date”

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

Overview

The view APPS.PA_PROJ_STATUS_REMINDER_V is a Projects (PA) module reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the set of projects that are eligible to appear on the Project Status Reminder list — that is, projects whose status report action is permitted and whose object page layout carries an active next reporting date. The view is the driving query behind the "Project Status Reports" / Project Status Reminder functionality, which prompts project managers and administrators to submit periodic status reports for active projects.

The view is defined with status VALID in the APPS schema and is exposed as a standard Oracle EBS view. It returns one row per project per eligible object page layout, joining project master data to its page layout configuration. Its role in reporting and integration is to serve as a pre-filtered candidate list: only projects that pass the status-action entitlement check (via the PA_PROJECT_UTILS.CHECK_PRJ_STUS_ACTION_ALLOWED function) and that fall within the effective date range of a PPR layout are returned. This allows dashboards, concurrent programs, and OAF pages to consume the view without re-implementing the eligibility logic.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_PROJECTS_ALL (SYNONYM) — the project master table, aliased as PROJ. Supplies the project ID (PROJECT_ID), name, number (SEGMENT1), and PROJECT_STATUS_CODE.
• PA_OBJECT_PAGE_LAYOUTS (SYNONYM) — the page layout configuration table, aliased as LAYOUT. Supplies the OBJECT_PAGE_LAYOUT_ID, NEXT_REPORTING_DATE, and the effective dating columns EFFECTIVE_FROM / EFFECTIVE_TO.
• PA_PROJECT_UTILS (PACKAGE) — provides the PL/SQL function CHECK_PRJ_STUS_ACTION_ALLOWED, which returns 'Y' when the specified project status permits the given action.

The join is driven by LAYOUT.OBJECT_ID = PROJ.PROJECT_ID with LAYOUT.OBJECT_TYPE = 'PA_PROJECTS' and LAYOUT.PAGE_TYPE_CODE = 'PPR'. Rows are filtered so that a next reporting date exists, the layout is currently effective (EFFECTIVE_FROM <= SYSDATE and NVL(EFFECTIVE_TO, SYSDATE) >= SYSDATE), and the status action check returns 'Y'.

Key Columns

• PROJECT_NUMBER — maps to PROJ.SEGMENT1; the user-visible project number.
• OBJECT_ID — the object page layout identifier (OBJECT_PAGE_LAYOUT_ID) associated with the project.
• OBJECT_TYPE — a literal value of 'PA_PROJ_STATUS_REPORTS', identifying the functional area to which the row belongs.
• OBJECT_NAME — the formatted display name, constructed as PROJ.NAME || '(' || PROJ.SEGMENT1 || ')'.
• REMINDER_DATE — the NEXT_REPORTING_DATE from the layout; the date on which the next status report becomes due.
• PROJECT_STATUS_CODE — the current status of the project (e.g., Active, On Hold).
• STATUS_ACTION_ALLOWED — the result of CHECK_PRJ_STUS_ACTION_ALLOWED(PROJECT_STATUS_CODE, 'PA_PROJ_STATUS_REPORT'), which will be 'Y' for all returned rows.

Common Use Cases and Queries

The view is used to populate status report reminder dashboards, to drive notifications, and to list projects approaching their reporting date. A typical query listing projects due for a status report is:

• SELECT project_number, object_name, reminder_date, project_status_code FROM apps.pa_proj_status_reminder_v ORDER BY reminder_date;
• SELECT project_number, reminder_date FROM apps.pa_proj_status_reminder_v WHERE reminder_date BETWEEN SYSDATE AND SYSDATE + 30; — for a forward-looking reminder window.
• SELECT COUNT(*) FROM apps.pa_proj_status_reminder_v WHERE project_status_code = 'ACTIVE'; — to quantify active projects eligible for reporting.

Because the view already enforces the eligibility and effective-dating rules, callers do not need to re-check layout validity or status-action permission. Reports and integrations should treat the view as read-only and rely on the underlying PA tables for any write operations.