Search Results pa_task_prog_inquiry_pkg

Overview

PA_TASK_PROG_INQUIRY_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM as an "OTHER" API type. Its business purpose is to support the Task Progress Inquiry functionality within Oracle Projects, providing the programmatic backbone for launching inquiry or reporting requests that summarize task-level progress across projects and tasks. The package encapsulates the logic required to submit concurrent requests — either for a single task, all tasks belonging to a project, or a single project — and to handle the callback and notification behavior associated with those submissions.

Unlike transactional project APIs that create or update business data, this package is inquiry-oriented: it assembles and submits request submissions so that users can review progress information through the standard concurrent manager framework. It relies on the shared FND_API utility layer for standard API error handling and message propagation, and on PA_ACTION_SET_UTILS for action-set related processing, reflecting its integration with Oracle Projects action set architecture.

Key Procedures and Functions

The ETRM documents seven procedures and functions for this package. Their documented purposes are as follows:

• REQUEST_SINGLE_TASK — Initiates an inquiry or progress request scoped to a single task, driving the submission for that specific task record.
• REQUEST_ALL_TASKS_IN_PROJECT — Initiates the equivalent request across every task belonging to a given project, aggregating the inquiry at project level.
• GET_NOTIFICATION_MODE — Retrieves the notification mode setting that governs how request completion or status notifications are delivered to the requesting user.
• CALLBACK — Provides the callback entry point executed upon completion of the submitted request, allowing the package to process results or perform post-submission handling.
• LAUNCH_REQUEST — The general launch routine that submits the inquiry request to the concurrent manager.
• LAUNCH_SINGLE_PROJECT — Launches the request scoped to a single project.
• LAUNCH_SINGLE_TASK — Launches the request scoped to a single task.

The separation between the REQUEST_* routines and the LAUNCH_* routines indicates a two-tier design: request preparation and parameter resolution occur first, followed by submission of the concurrent request with the appropriate notification and callback configuration.

Tables Accessed

The ETRM dependency metadata supplied for PA_TASK_PROG_INQUIRY_PKG does not enumerate specific base tables accessed via APPS synonyms; only the package-level dependencies on FND_API, PA_ACTION_SET_UTILS, and the SYS.STANDARD library are documented. Because the package is an inquiry submission layer, any data access it performs is likely indirect — either through the concurrent program logic it launches or through supporting packages in the Oracle Projects schema — rather than through direct DML against project or task tables. Consumers should treat the absence of documented table references as an indication that the package's role is orchestration and submission rather than direct data manipulation.

Usage Notes

PA_TASK_PROG_INQUIRY_PKG is referenced by the PA_TASK_PROG_ACTSET package and is self-referenced, confirming that it participates in the Task Progress action set flow. It is typically invoked when a user triggers Task Progress Inquiry from the Oracle Projects user interface or through the associated action set mechanism, where the JSP or Forms layer calls the LAUNCH_* and REQUEST_* routines to submit the inquiry request. GET_NOTIFICATION_MODE and CALLBACK support the notification and post-processing contract expected by the concurrent manager.

Customizations should call these procedures through the supported action set path rather than invoking internal logic directly, and should respect the FND_API error-handling conventions. As with all APPS-owned packages in 12.1.1 and 12.2.2, the package is version VALID and should not be modified; extensions belong in custom packages that wrap the documented entry points.