Search Results launch_single_project




Overview
Explore in AI Chat

Overview

APPS.PA_TASK_PROG_INQUIRY_PKG is a PL/SQL package body that belongs to the Oracle Projects (PA) application family. Its name and procedure structure indicate that it supports task progress inquiry processing — specifically the mechanism by which a user, a form, or a workflow process requests that progress or status be recalculated and recorded for project tasks. The package wraps the standard Oracle EBS API conventions (FND_API versioning, message list initialization, commit control, validation-only mode, and message count/data output parameters), which confirms it is designed to be called as a server-side API rather than as a standalone report.

The header comment ($Header: PATPINQB.pls 120.1 2005/08/19 ... mwasowic noship $) shows the file has been at version 120.1 since 2005 and carries the "noship" designation, meaning it is an internal helper that is not shipped as a standalone product component but is installed with the Projects schema. Its primary business role is to serve as the request layer between the user interface or Oracle Workflow and the underlying task progress calculation logic.

Key Procedures and Functions

  • REQUEST_SINGLE_TASK — Initiates progress or status processing for one specific task, identified by task identifier. It follows the standard EBS API signature (API version, init message list, commit flag, validate-only flag, max message count) and returns an action-line audit table plus the usual return status and message outputs.
  • REQUEST_ALL_TASKS_IN_PROJECT — The project-level counterpart to the single-task request. It drives the same processing across every task belonging to a given project, again returning an audit table and API status information.
  • GET_NOTIFICATION_MODE — A workflow callback that determines how a notification related to the task progress request should be delivered, based on the workflow item type, item key, activity, and function mode.
  • CALLBACK — The generic Oracle Workflow callback entry point, invoked when the workflow engine needs to resume processing of a task progress request item.
  • LAUNCH_REQUEST — This is the procedure most relevant to the user's search term. It is the top-level launcher that submits or initiates the task progress inquiry request, acting as the entry point that custom code or a form calls to begin processing.
  • LAUNCH_SINGLE_PROJECT — Launches the progress request scoped to a single project.
  • LAUNCH_SINGLE_TASK — Launches the progress request scoped to a single task.

Several entry points in the source excerpt (REQUEST_SINGLE_TASK, REQUEST_ALL_TASKS_IN_PROJECT, GET_NOTIFICATION_MODE) contain NULL; bodies, indicating they are stubs in this version or that the real logic resides elsewhere in the package.

Tables Accessed

The documentation does not list any tables referenced via APPS synonyms. The source excerpt shows the package operates largely through parameter passing, notably the output parameter x_action_line_audit_tbl of type pa_action_set_utils.insert_audit_lines_tbl_type, which is an action audit structure defined in the PA schema. The actual task and project data reads and writes are presumed to occur in the procedures that implement the launch logic.

Usage Notes

PA_TASK_PROG_INQUIRY_PKG is referenced by one other package and is typically invoked from Oracle Forms, Oracle Workflow, or custom PL/SQL. Because the public procedures accept validation and commit flags, callers can invoke them in validate-only mode before committing. Custom integrations should supply a valid API version, initialize the message list when required, and inspect x_return_status, x_msg_count, and x_msg_data for error handling.