Search Results pa_workplan_workflow_client




Overview
Explore in AI Chat

Overview

PA_WORKPLAN_WORKFLOW_CLIENT is an Oracle EBS Applications (APPS) PL/SQL package that supports the workflow-driven approval and notification infrastructure of the Oracle Projects Workplan functionality. In Oracle EBS 12.1.1 and 12.2.2, the Workplan is the collaborative structure through which project managers assign tasks and deliverables to team members, and through which those assignments are routed for approval. This package functions as the client-side workflow integration layer: it initiates the Workplan approval workflow, resolves the appropriate approver, manages notification recipients, and renders the Workplan preview used by the notification content. It is classified in the ETRM as API classification OTHER, meaning it is an internal supporting package rather than a public, documented open interface. Its status is VALID in the APPS schema, and it is referenced by the parent package APPS.PA_WORKPLAN_WORKFLOW, which coordinates the higher-level workflow processing.

Key Procedures and Functions

The ETRM documents five procedures/functions within the package body:

  • START_WORKFLOW — Initiates the Workplan approval workflow process for the relevant Workplan or project structure, seeding the workflow with the context required for subsequent approval and notification activity.
  • SELECT_APPROVER — Determines and returns the approver responsible for a given Workplan submission, resolving project party and reporting relationships to identify the correct approver.
  • SET_NOTIFICATION_PARTY — Establishes the party or parties who should receive workflow notifications generated during the Workplan approval cycle.
  • SHOW_WORKPLAN_PREVIEW — Produces a preview rendering of the Workplan, typically used to populate notification bodies so recipients can review the structure being approved without opening the full form.
  • SET_LEAD_DAYS — Configures the lead-day offset applied to Workplan workflow scheduling or deadline notification logic.

Parameter lists and signatures are not published in the ETRM metadata and should be confirmed against the deployed package specification before direct invocation.

Tables Accessed

The package reads and writes through APPS synonyms. Project Workplan structures are held in PA_PROJ_WORKPLAN_ATTR, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_STRUCTURE, and PA_PAGE_CONTENTS, which supply the task hierarchy and page-level content rendered by the preview. PA_PROJECTS_ALL and PA_PROJECT_PARTIES provide project and party context, while PA_OBJECT_RELATIONSHIPS resolves the associations between Workplan objects and their approvers or notification recipients. PER_ALL_PEOPLE_F and FND_USER identify human resources and application users. FND_FORM_FUNCTIONS and FND_COMPILED_MENU_FUNCTIONS support function and menu-based navigation or security checks. DBMS_LOB and DUAL are used for large object handling and singleton queries respectively.

Usage Notes

PA_WORKPLAN_WORKFLOW_CLIENT is not a user-invoked API. It is called by APPS.PA_WORKPLAN_WORKFLOW and, per ETRM dependency data, by one additional referencing package. Typical invocation occurs indirectly when a project manager submits a Workplan for approval from the Oracle Projects Workplan form, or when the Workplan workflow background process executes. Administrators and developers should avoid calling these procedures directly unless replicating supported Workplan behavior; unsupported direct calls risk inconsistent workflow state. The package is schema-resident in APPS and should be treated as Oracle proprietary and confidential.