Search Results c_item_description

Overview

PJM_SCHED_INT_WF_PRIV is a private PL/SQL package body owned by APPS within the Oracle E-Business Suite Project Manufacturing (PJM) application. Its documented API classification is OTHER, and it is referenced by one other package, indicating that it is an internal implementation unit rather than a public integration point. The package forms part of the Project Manufacturing scheduling integration framework, which links project and task structures to supply chain execution cycles. It encapsulates the Workflow (WF) engine invocations used to launch project-driven supply chain processes such as work in process jobs, sales orders, forecasts, requisitions, RFQs, quotations, master demand schedules, master production schedules, purchase orders, and purchase order releases. Its procedures act as the private engine room behind a public scheduling integration API, coordinating workflow item creation, purge handling, and notification routing to project managers, task managers, and requestors.

Key Procedures and Functions

The package exposes eleven documented procedures. COMMON_START is the shared workflow initiation routine. It accepts item type, item key, process, owner, requestor, tolerance days in numeric form, notification flags for the project and task managers, project number and name, project start and end dates, task number and name, task start and end dates, exception subject and body, document type, item number, and c_item_description. It resolves the project manager and task manager through PJM_INTEGRATION_PROJ_MFG helper calls, suppresses self-routing when the requestor matches the manager, purges prior workflow state, and creates the workflow process. Note that c_item_description is one of the parameters carried into the common_start signature, which is why a search for that term surfaces this object.

The remaining ten procedures are launch wrappers for specific supply chain documents: LAUNCH_WIP for work in process jobs, LAUNCH_SO for sales orders, LAUNCH_FORECAST for forecasts, LAUNCH_PR for purchase requisitions, LAUNCH_RFQ for requests for quotation, LAUNCH_QUOTATION for quotations, LAUNCH_MDS for master demand schedules, LAUNCH_MPS for master production schedules, LAUNCH_PO for purchase orders, and LAUNCH_PO_RELEASE for purchase order releases. Each wrapper supplies document-specific context to the workflow engine through the private common routines and is intended only for internal mediation between the scheduling integration layer and Oracle Workflow.

Tables Accessed

The provided ETRM metadata does not enumerate any directly referenced tables via APPS synonyms. Workflow persistence is handled indirectly through the standard WF_PURGE and WF_ENGINE APIs, which operate on the Workflow runtime tables rather than on application tables owned by PJM. Project manager and task manager lookups are delegated to the PJM_INTEGRATION_PROJ_MFG package and to PJM_PROJECT conversion functions such as val_proj_numtoid and val_task_numtoid. Diagnostic output is written through PJM_CONC.put_line, consistent with concurrent program logging conventions. Consequently, the package behaves as a coordinating layer that persists no business data of its own.

Usage Notes

PJM_SCHED_INT_WF_PRIV is a private package body and should not be called directly from forms, concurrent programs, or custom code. It is invoked by its public counterpart within the Project Manufacturing scheduling integration stack whenever a project-driven document must trigger a workflow notification or approval cycle. Typical invocation arises automatically when WIP jobs, sales orders, forecasts, requisitions, RFQs, quotations, MDS, MPS, purchase orders, or PO releases are created or changed and require the routing of exception messages to the project manager or task manager. Because its name is prefixed _PRIV and it appears only as a dependency of one other package, customization should be confined to the public scheduling integration API. The presence of the c_item_description parameter in common_start reflects its role in composing workflow notification content for the affected document.