Search Results pjm_wf_seek_task_mgr




Overview
Explore in AI Chat

Overview

PJM_INTEGRATION_PROJ_MFG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the integration between Oracle Projects and Oracle Manufacturing for project-driven manufacturing and scheduling flows. In EBS 12.1.1 and 12.2.2, it functions as a supporting utility layer within the Project Manufacturing integration framework, providing shared validation, lookup, and workflow-seeking logic used by scheduling and integration workflows rather than by end-user forms directly.

The package operates as an OTHER-classified API rather than a formally published open interface. Its role is internal: the documented metadata shows it depends on SYS.STANDARD and is referenced by PJM_SCHED_INT_WF, PJM_SCHED_INT_WF_PRIV, and itself, confirming that it is a subordinate component of the PJM Scheduling Integration workflow infrastructure. The package does not expose a public open interface for external data loading.

Key Procedures and Functions

The ETRM documentation lists seven documented subprograms. Their names indicate the following purposes:

  • PJM_VALIDATE_DATE — Validates a date value supplied during project manufacturing integration processing, ensuring the value meets the expected format and business rules before it is used in downstream scheduling logic.
  • PJM_EXCEPTION_DAYS — Determines or returns exception day information used when calculating or excluding non-working periods within project manufacturing scheduling.
  • PJM_SELECT_PROJECT_MANAGER — Retrieves the project manager associated with a project, used to route workflow notifications or approvals to the correct individual.
  • PJM_SELECT_TASK_MANAGER — Retrieves the task manager associated with a project task, used for task-level routing of workflow or approval activity.
  • SELECT_DOCUMENT_TYPE — Returns the applicable document type, used to classify integration or workflow messages within the Project Manufacturing flow.
  • PJM_WF_SEEK_PROJECT_MGR — A workflow-oriented routine that seeks the project manager as part of the PJM workflow participant resolution process.
  • PJM_WF_SEEK_TASK_MGR — The task-level counterpart, seeking the task manager to resolve workflow participants at the task level.

No parameter lists are documented for these subprograms, and none should be assumed. Their names, however, clearly reflect role resolution and validation responsibilities within the workflow integration stack.

Tables Accessed

The package references three documented tables through APPS synonyms:

  • FND_USER — The Oracle Applications user repository, consulted to resolve project and task managers to valid application user accounts, most likely from the PJM_SELECT_PROJECT_MANAGER, PJM_SELECT_TASK_MANAGER, PJM_WF_SEEK_PROJECT_MGR, and PJM_WF_SEEK_TASK_MGR routines.
  • PA_PROJECTS_ALL — The Oracle Projects project master table, read to identify the project and its attributes, including the project manager.
  • PA_TASKS — The Oracle Projects task table, read to identify task-level attributes and the associated task manager.

The package is documented as reading these tables; no write operations are indicated by the metadata. Access is read-only resolution and validation of project, task, and user data.

Usage Notes

PJM_INTEGRATION_PROJ_MFG is not intended for direct invocation by end users or by custom open-interface routines. It is invoked indirectly by the PJM Scheduling Integration workflow packages — PJM_SCHED_INT_WF and PJM_SCHED_INT_WF_PRIV — which call it to resolve workflow participants and validate integration data. In this capacity it participates in the internal notification and routing logic of the Project Manufacturing integration flow.

Because the package is classified as OTHER and exposes no documented parameters, customizations should avoid calling it directly. Any extension of its behavior should instead be layered on the calling workflow packages or on supported Oracle Projects and Manufacturing APIs. Its validity status in both 12.1.1 and 12.2.2 confirms that no online patching or editioning changes affect its basic structure across the two releases. As always, review the actual package specification in the target instance before relying on any specific subprogram signature.