Search Results pa_report_workflow_client




Overview
Explore in AI Chat

Overview

PA_REPORT_WORKFLOW_CLIENT is an Oracle Projects client extension package owned by APPS and defined with AUTHID CURRENT_USER. Its purpose is to expose customizable hooks for the Workflow processes that govern the submission, approval, and publication of project status reports. The package is classified as a public, active extension under the PA (Oracle Projects) product and is associated with the business entities PA_PROJECT and PA_PERF_REPORTING. In Oracle EBS 12.1.1 and 12.2.2, the Project Status Report Workflow orchestrates routing of a report version through approvers and notification recipients; this package supplies the procedural logic that determines those participants at runtime. Customers may replace the seeded logic to align workflow routing with their own organizational hierarchies, approval matrices, or notification policies. The package is documented as compatible with standard (S) usage and is referenced by one other package, indicating it forms part of a small, cohesive extension layer rather than a broadly shared utility.

Key Procedures and Functions

The package exposes three documented entry points, all invoked as Workflow function activities:

  • start_workflow — Initiates the status report workflow process. It accepts the item type, process name, item key, and version identifier, and returns the message count, message data, and return status for the workflow engine.
  • set_report_approver — Determines the approver for a report. It receives the process name, item key, activity identifier, function mode, and an output result, allowing the approval routing step to resolve the appropriate approver.
  • set_report_notification_party — Resolves the notification party for a report. It receives the item type, item key, report status, activity identifier, function mode, and output result. This is the procedure most often customized to redirect status report notifications to specific users, roles, or project personnel based on the report status.

Parameter lists are not reproduced here; only documented purpose is described, consistent with the reference documentation.

Tables Accessed

The package reads and writes through APPS synonyms across several schemas. PA_PROGRESS_REPORT_VERS supplies the report version and its status. PA_PROJECT_PARTIES and PER_ALL_PEOPLE_F provide project team members and person records used to resolve approvers and notification recipients. FND_USER and WF_LOCAL_ROLES support resolution of workflow roles and users, while FND_ATTACHED_DOCUMENTS links supporting attachments to the report. PA_OBJECT_PAGE_LAYOUTS stores page layout configuration relevant to the report presentation, and PLITBLM is the standard PL/SQL integer table used in Oracle Forms-based APIs. Together these tables allow the package to derive the correct workflow participants from project staffing and status report data.

Usage Notes

PA_REPORT_WORKFLOW_CLIENT is typically invoked by the Workflow engine when the Project Status Report workflow executes its function activities, not directly by end users. Customizations are implemented by editing or wrapping the procedures, most commonly set_report_notification_party and set_report_approver, so that notification and approval routing reflect customer business rules. The package may also be called from custom PL/SQL that submits or drives status report workflow processes programmatically. Because the package is declared AUTHID CURRENT_USER, execution privileges follow the invoking schema, so customizations should be validated against the APPS execution context. The header indicates the file is seeded as noship (non-shipped) in later releases, and the referenced documentation is the Oracle Projects API's, Client Extensions, and Open Interfaces Reference (doccd 120pjapi.pdf). Changes should be reapplied after patching, since seeded extension packages may be overwritten during upgrades.