Search Results select_project_approver

Overview

PA_CLIENT_EXTN_PROJECT_WF is an Oracle Projects client extension package body owned by the APPS schema. Its name and dependency profile establish it as the server-side integration layer between Oracle Projects and the Oracle Workflow engine (WF_ENGINE / WF_CORE). The package is responsible for initiating and driving the project approval workflow, which routes newly created or status-changed projects to the appropriate approver based on project type, project status, and the organizational hierarchy.

In the context of the Oracle EBS 12.1.1 and 12.2.2 releases, this package functions as the outer wrapper that the Projects forms and concurrent programs call when a project must enter an approval cycle. It resolves the workflow item key, determines routing, and hands control to the generic Workflow APIs. The object is documented as VALID and is classified as OTHER under the ETRM API classification scheme, reflecting that it is an internal client-extension routine rather than a formally published public API.

The mention of PA_WORKFLOW_ITEMKEY_S in the user's search is directly relevant: the package body is documented as referencing that database sequence, which generates the unique item keys that tie each project approval workflow instance back to its originating project record.

Key Procedures and Functions

• SELECT_PROJECT_APPROVER — Determines the approver to be assigned to a project approval workflow. It derives the responsible person from the project's type and status configuration and from the human resources assignment data available through PER_ALL_PEOPLE_F and PER_ASSIGNMENTS_F, combined with the organization units defined in HR_ORGANIZATION_UNITS. The result is consumed by the workflow launch logic so that the correct role receives the notification and approval responsibility.
• START_PROJECT_WF — Initiates the project approval workflow instance. It acquires a new workflow item key, assembles the workflow attributes required by the Oracle Projects workflow definition, and invokes the Workflow engine (WF_ENGINE) to create and start the process. The item key returned by this routine becomes the workflow identifier associated with the project throughout the approval lifecycle.

Both procedures are documented as the package's only two program units in the ETRM 12.2.2 metadata. No parameter lists are published, and none should be assumed.

Tables Accessed

• PA_PROJECTS / PA_PROJECTS_ALL — Source of project header information, including project number, name, and organizational attributes required to build workflow attributes.
• PA_PROJECT_TYPES — Provides the project type definition used to determine approval routing rules.
• PA_PROJECT_STATUSES — Supplies the status codes and meanings that govern whether and how the approval workflow is launched.
• PA_OBJ_STATUS_CHANGES — Records status transitions on the project object, supporting the trigger logic that starts or advances the workflow.
• PA_WORKFLOW_ITEMKEY_S — Sequence supplying unique item keys for each workflow instance.
• PER_ALL_PEOPLE_F / PER_ASSIGNMENTS_F / HR_ORGANIZATION_UNITS — Resolve the approver to a valid person and assignment within the correct organization.
• FND_USER — Maps the resolved person to an application user for notification delivery.
• DUAL — Used for sequence and utility selection statements.

Usage Notes

PA_CLIENT_EXTN_PROJECT_WF is invoked indirectly rather than from user code. It is reached when a project is submitted for approval from the Oracle Projects forms, or from concurrent programs that create and release projects on a scheduled basis. In customized implementations, the package is the intended extension point for overriding standard approver-selection behavior: the "client extension" designation indicates that customers may copy and modify the routing logic without altering core Projects code.

Because the package depends on FND_API, FND_GLOBAL, WF_CORE, and WF_ENGINE, any workflow activity generated by these procedures appears in the standard Workflow notification and status monitor screens. Administrators troubleshooting stalled approvals should examine the workflow item key produced by START_PROJECT_WF and correlate it to the project record. The ETRM metadata shows the package is referenced by one other database object, confirming its role as a dependant component in the project approval chain rather than a widely shared utility.