Search Results pa_progress_reports




Overview
Explore in AI Chat

Overview

PA_REPORT_WORKFLOW_CLIENT is an Oracle Projects package body owned by APPS that supplies client extension logic for the Oracle Workflow activities associated with project status reporting. In Oracle EBS 12.1.1 and 12.2.2, status reports — the progress reports surfaced through the Project Status Reporting pages and menu path commonly searched as pa_progress_reports — are routed through Oracle Workflow for approval and notification. The workflow definition defines the process; this package provides the PL/SQL callbacks that the workflow engine invokes at specific activity nodes.

The package is classified as OTHER in the ETRM repository, reflecting that it is an internal implementation package rather than a published integration API. Its file, PAPRWFCB.pls, carries the header comment dated 2012 (version 120.9.12020000.3), which corresponds to the 12.2 code line. Its responsibilities are narrow and well defined: start the status report approval workflow, resolve which party should approve a given report version, and determine which party should receive the report notification.

Key Procedures and Functions

The package body documents three procedures, each mapping to a Workflow function activity or a workflow-invoked client extension:

  • START_WORKFLOW — Initiates the status report workflow process. It receives the workflow item type, the process name, and the item key that together identify the specific workflow instance to launch, along with a version identifier for the report being submitted. It returns the standard message count, message data, and return status out parameters used by Oracle Projects for error propagation. This is the entry point through which a submitted progress report enters the approval cycle.
  • SET_REPORT_APPROVER — A Workflow function activity that determines and assigns the approver for a report version. It is invoked with the process name, item key, activity identifier, function mode, and result out parameter. The procedure resolves the approver from the project parties and assignment data for the report, and populates the notification recipient used by the approval activity. The documented history shows this procedure has required ongoing maintenance for assignment validation rules, including assignment type and primary flag conditions, and an enhancement to set the correct role name in the notification's recipient field.
  • SET_REPORT_NOTIFICATION_PARTY — A Workflow function activity that resolves the notification recipient for the status report based on the report's current status. It accepts the workflow item type, item key, report status, activity identifier, function mode, and result out parameter, allowing the workflow to route notifications to the appropriate party as the report advances through its lifecycle.

Tables Accessed

The package reads and writes the following objects through APPS synonyms. PA_PROGRESS_REPORT_VERS holds the report version rows that drive approver and notification resolution. PA_PROJECT_PARTIES and PER_ALL_PEOPLE_F supply the project party and person data used to identify approvers and recipients. WF_LOCAL_ROLES and FND_USER provide the Workflow role and application user identity information required to formulate notification addresses. FND_ATTACHED_DOCUMENTS and PA_OBJECT_PAGE_LAYOUTS support attachment and page layout context associated with the report, and PLITBLM is the standard Oracle Projects message table used for the message-count and message-data returns.

Usage Notes

PA_REPORT_WORKFLOW_CLIENT is not intended for direct invocation by end users or custom integrations. It is called by the Oracle Workflow engine when the status report workflow process reaches the client extension activities that reference these procedures. In practice it is exercised whenever a progress report is submitted for approval through the Project Status Reporting pages in Oracle Projects, and whenever the workflow subsequently evaluates approver and notification routing. Because the procedure signatures and internal logic are tied to the shipped workflow definition, modifications should be avoided; upgrades and patches to Oracle Projects may replace PAPRWFCB.pls, and any customization that reuses these procedures risks conflict with the delivered workflow configuration. Administrators troubleshooting stalled report approvals should inspect the workflow item in the Workflow Administrator responsibility rather than calling this package directly.