Search Results c_task_number

Overview

APPS.PJM_SCHED_INT_WF_PRIV is a private PL/SQL package within the Oracle E-Business Suite Project Manufacturing (PJM) module, specifically belonging to the Project Scheduling Integration Workflow component. Its principal business function is to serve as a centralized workflow launcher for Project Manufacturing scheduling events. The package abstracts the complexity of initiating Oracle Workflow processes by providing a common entry point (COMMON_START) and a set of specialized launch procedures, each tailored to a distinct scheduling or execution context such as work-in-process jobs, sales orders, forecasts, requisitions, quotations, master demand schedules, master production schedules, and purchase orders. The package is declared AUTHID CURRENT_USER, meaning that all unqualified object references resolve under the privileges of the invoking schema rather than the package owner, a design choice that supports flexible integration within the APPS environment. Its header reflects legacy Project Manufacturing code dating back to release 11.5, and it remains catalogued in ETRM 12.2.2 with an API classification of OTHER, indicating it is an internal (private) utility rather than a formally published public API.

Key Procedures and Functions

The package exposes eleven documented procedures. COMMON_START is the shared initialization routine that accepts a broad set of workflow context parameters — including item type, item key, process name, owner, requestor, tolerance days, notification recipients for project and task managers, project and task identification and dates, exception messaging, and document/item descriptive attributes. The remaining procedures are specialized launchers that build upon this common invocation pattern for specific business objects:

• LAUNCH_WIP — Launches the workflow for a Work in Process job, carrying additional job-level attributes such as WIP job name, organization, job start/end dates, status, job type, and start/completed quantities.
• LAUNCH_SO — Initiates the scheduling integration workflow in the context of a sales order.
• LAUNCH_FORECAST — Triggers the workflow for forecast-related scheduling events.
• LAUNCH_PR — Launches the workflow for a purchase requisition.
• LAUNCH_RFQ — Launches the workflow for a request for quotation.
• LAUNCH_QUOTATION — Launches the workflow for a quotation, the object associated with the user's search term.
• LAUNCH_MDS — Initiates the workflow for a Master Demand Schedule.
• LAUNCH_MPS — Initiates the workflow for a Master Production Schedule.
• LAUNCH_PO — Launches the workflow for a purchase order.
• LAUNCH_PO_RELEASE — Launches the workflow for a purchase order release.

Although the excerpt does not enumerate the parameter lists for procedures after LAUNCH_SO, the naming convention and the detailed signature of LAUNCH_WIP indicate that each launcher accepts the common workflow context parameters and adds object-specific attributes relevant to its document type.

Tables Accessed

The ETRM metadata does not document explicit table references for PJM_SCHED_INT_WF_PRIV via APPS synonyms. As a workflow integration package, it is not primarily a data-manipulation utility; instead it passes context to Oracle Workflow engine APIs, which persist runtime state in the standard Workflow tables (such as WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_NOTIFICATIONS) and generate notifications based on the exception subject and body parameters supplied by the caller. The project, task, item, and job attributes passed into each procedure originate from the calling application's own database structures rather than being read directly by this package.

Usage Notes

PJM_SCHED_INT_WF_PRIV is an internal package intended for invocation by Project Manufacturing scheduling integration logic, typically from other PL/SQL packages rather than directly by end users. The ETRM catalog records that it is referenced by one other package, confirming its role as a subordinate helper module. It may also be surfaced indirectly through Project Manufacturing forms or concurrent programs that process scheduling exceptions, but direct custom calls should be treated with caution: the PRIV suffix signals a private interface subject to change, and the AUTHID CURRENT_USER declaration means callers must ensure the invoking schema has appropriate privileges on any referenced objects. Customizations should prefer documented public APIs where available.