Search Results start_task_execution_wf

Overview

PA_WORKPLAN_WORKFLOW is an Oracle EBS Application Object Library PL/SQL package body owned by APPS that provides the workflow integration layer for the Oracle Projects workplan and project/task execution features. It is responsible for creating and managing the Oracle Workflow process instances (items) that drive workplan approval cycles and task/project execution flows initiated from the Project Manager and Team Member responsibility pages. The package abstracts the underlying WF_ENGINE calls, encapsulates generation of workflow item keys, and exposes wrapper procedures that application forms, concurrent programs, and other PL/SQL modules can invoke. The package depends on workflow definitions registered in PA_WF_PROCESSES and relies on the PA_WORKFLOW_ITEMKEY_S sequence to mint unique item keys for each process started. It is referenced by four other packages, indicating its role as a shared service within the Projects suite.

Key Procedures and Functions

The documented API surface comprises fourteen procedures and functions:

• START_WORKFLOW — Creates a workflow process instance by generating an item key from PA_WORKFLOW_ITEMKEY_S, calls WF_ENGINE.createProcess, delegates to PA_WORKPLAN_WORKFLOW_CLIENT.START_WORKFLOW for initialization, and then calls WF_ENGINE.startProcess when the prior call succeeds.
• CANCEL_WORKFLOW — Terminates an in-flight workplan workflow by invoking WF_ENGINE.ABORTPROCESS for the supplied item type and item key.
• CHECK_WORKPLAN_STATUS — Evaluates the current state of the workplan workflow to determine whether related processing should proceed.
• CHANGE_STATUS_WORKING, CHANGE_STATUS_REJECTED, CHANGE_STATUS_APPROVED — Update the workplan's approval status to the corresponding state (working, rejected, approved) as the workflow progresses.
• SELECT_ERROR_RECEIVER — Determines the recipient who should receive error notifications generated during workplan workflow execution.
• SHOW_WORKPLAN_PUB_ERR — Displays or surfaces the public error message associated with a workplan workflow failure.
• START_PROJECT_EXECUTION_WF, CANCEL_PROJECT_EXECUTION_WF — Start and cancel the workflow that governs project-level execution.
• START_TASK_EXECUTION_WF — Starts the workflow that governs execution of an individual task within a project structure.
• CANCEL_TASK_EXECUTION_WF, RESTART_TASK_EXECUTION_WF — Cancel and restart an existing task execution workflow item.
• IS_PROJECT_CLOSED — Returns whether the referenced project is in a closed status, allowing callers to suppress workflow actions on closed projects.

Tables Accessed

The package reads and writes through APPS synonyms to the following tables: PA_PROJECTS_ALL (project master data), PA_PROJECT_STATUSES (project status codes used by IS_PROJECT_CLOSED), PA_PROJECT_PARTIES (project team membership, used to resolve approvers and error receivers), PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS (workplan task elements and their versions), PA_PROJ_ELEM_VER_SCHEDULE (version scheduling), PA_PROJ_ELEM_VER_STRUCTURE (task hierarchy within a structure version), PA_PROJ_STRUCTURE_TYPES (classification of structures), PA_PAGE_CONTENTS (workplan page content), PA_PROJ_WORKPLAN_ATTR (workplan attributes), PA_WF_PROCESSES (registered workflow process definitions), PA_WORKFLOW_ITEMKEY_S (sequence supplying item keys), and the FND tables FND_USER, FND_FORM_FUNCTIONS, and FND_COMPILED_MENU_FUNCTIONS, which support responsibility, user, and function security context needed when launching workflow items.

Usage Notes

PA_WORKPLAN_WORKFLOW is normally invoked indirectly rather than called directly by end users. The START_WORKFLOW and CANCEL_WORKFLOW entry points are triggered from the Project Manager and Team Member workplan pages when a workplan is submitted for approval or withdrawn. The task execution procedures (START_TASK_EXECUTION_WF, CANCEL_TASK_EXECUTION_WF, RESTART_TASK_EXECUTION_WF) and the project execution equivalents are called by the Projects execution UI and by other PL/SQL packages in the Workplan/Execution product family — the metadata records four packages referencing this module. Because the procedures follow the FND_API error-handling convention (x_return_status, x_msg_count, x_msg_data) plus an OUT item key, custom integrations can call them safely from concurrent programs or from custom PL/SQL. Callers should always verify x_return_status equals FND_API.g_ret_sts_success before persisting or forwarding the returned item key, and should guard against starting execution workflows for projects for which IS_PROJECT_CLOSED returns TRUE.