Search Results psp_wf_custom

Overview

PSP_WF_CUSTOM is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Enterprise Asset Management (eAM) / Project Resource Management family of modules. Its name associates it with the PSP module prefix, which in Oracle EBS corresponds to Oracle Services Procurement and project staffing functionality, while the WF component indicates that the package participates in the Oracle Workflow notification and approval framework. The package is classified as VALID in the ETRM repository, confirming that both the package specification and package body compile cleanly against the 12.1.1 and 12.2.2 code lines.

The package exists to supply custom organizational routing logic to workflow-driven approval processes. Rather than hard-coding approver and certifier resolution inside a seeded workflow function, Oracle delivers this package as an extension point so that implementations can override or supplement the default routing with site-specific rules. In this respect PSP_WF_CUSTOM behaves as a customization hook wrapped around standard Workflow attribute lookups.

Key Procedures and Functions

The ETRM metadata documents two public program units:

• EFFORT_SELECT_CERTIFIER — resolves the certifier responsible for an effort or timecard submission. In a services procurement or project effort workflow, the certifier is the individual who formally attests that recorded effort is accurate and chargeable. This function is invoked by the approval workflow to populate the certifier attribute on the notification activity, thereby determining the recipient of the certification step.
• EFFORT_SELECT_APPROVER — resolves the approver for the same effort record. The approver is the authority who grants final acceptance of the submitted effort, and this function returns the identity passed into the workflow as the approver attribute so that the standard approval notification is routed correctly.

Both units are selection routines: they encapsulate the lookup rules (for example, supervisory hierarchy traversal or assignment-based resolution) so that the calling workflow does not need to embed that logic. The metadata does not document parameter signatures; consult the package specification in the ETRM source viewer before extending or wrapping these routines.

Tables Accessed

The extracted ETRM metadata records no direct table references for PSP_WF_CUSTOM through APPS synonyms. The documented dependency list is limited to SYS.STANDARD, which reflects only standard PL/SQL compilation dependencies rather than application data access. In practice, the selection routines typically obtain their results through the Workflow directory services and HR assignment APIs rather than by issuing direct SQL against base tables, which is consistent with the absence of documented table references. Implementations that extend this package to enforce custom routing rules should be aware that any additional table access they introduce is not part of the seeded dependency footprint and must be validated independently.

Usage Notes

PSP_WF_CUSTOM is referenced by one other package, PSP_WF_EFF_PKG, which is the primary effort workflow integration package. The calling sequence is therefore expected to be: a workflow activity or concurrent process invokes PSP_WF_EFF_PKG, which delegates approver and certifier resolution to PSP_WF_CUSTOM. The package is not intended for direct invocation from forms or concurrent program definitions.

Because the package is seeded in the APPS schema, any customization should be performed as a layered override rather than by editing the delivered object, so that patching and upgrade cycles in 12.1.1 and 12.2.2 do not overwrite site-specific logic. Typical customization scenarios include redirecting certification to a project manager rather than a line supervisor, or applying delegation rules during absence. All such changes should be regression-tested against the effort approval workflow after each application of an EBS patch or family pack.