Results for “pa_prm_wf_item_key_s”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_CANDIDATE_PUB is a public PL/SQL package in the APPS schema that implements the candidate management and staffing workflow functionality of Oracle Project Resource Management (PRM), a component of Oracle Projects. The package body encapsulates the business logic used to nominate resources as candidates for project assignments, evaluate their availability and competence match, track candidacy through review, and drive the associated Oracle Workflow notifications. It is the programmatic interface behind the "Candidates" and "Staffing" pages used by project managers and resource managers in Oracle E-Business Suite 12.1.1 and 12.2.2.

The package is classified as a PUB (public) API, meaning it is intended to be called by other application modules — primarily the PRM OAF/Forms user interface, workflow background processes, and customer extensions — rather than being restricted for internal use. Its status in ETRM is VALID, and the package is referenced by eight other database objects while depending on a broad set of Oracle Projects, Oracle HR, Oracle Receivables (HZ) and Workflow (WF) packages.

Key Procedures and Functions

The package exposes twenty-one documented procedures and functions, organized around the candidacy lifecycle:

• ADD_CANDIDATE, UPDATE_CANDIDATE, DELETE_CANDIDATES, COPY_CANDIDATES — create, maintain, duplicate and remove candidate records on a project assignment.
• WITHDRAW_CANDIDATE, DECLINE_CANDIDATES — transition a candidate out of the active pipeline, either voluntarily or as a rejection.
• CHECK_CANDIDACY, CHECK_AVAILABILITY, IS_CAND_ON_ASSIGNMENT, IS_CAND_ON_ANOTHER_ASSIGNMENT, IS_ACTIVE_CANDIDATE, RESOURCE_IS_CANDIDATE — validation functions used to determine whether a resource may be, or already is, a candidate on a given assignment.
• GET_NUMBER_OF_CANDIDATES, GET_COMPETENCE_MATCH — retrieval helpers that return candidate counts and competence-match scores for a resource/assignment combination.
• UPDATE_NO_OF_ACTIVE_CANDIDATES, UPDATE_REMAINING_CANDIDATES, ADD_CANDIDATE_LOG — maintain denormalized candidate counters on the assignment and write audit/log records for candidacy events.
• START_WORKFLOW, GET_NF_RECIPIENT, GET_REVIEW_CHANGE_REASON — initiate the PRM candidate approval workflow, resolve notification recipients, and return review change reasons used in the workflow and UI.

All procedures delegate messaging and error handling to FND_MSG_PUB and FND_API, and use FND_GLOBAL and FND_PROFILE for session and profile-option context.

Tables Accessed

The package reads and writes the core PRM candidacy tables:

• PA_CANDIDATES / PA_CANDIDATES_S — the candidate header records and their primary-key surrogate sequence.
• PA_CANDIDATE_REVIEWS / PA_CANDIDATE_REVIEWS_S — review and feedback rows associated with a candidate.
• PA_PRM_WF_ITEM_KEY_S — the sequence that generates the workflow item key used to correlate a candidate with its Oracle Workflow process instance. This is the object most directly implicated by the search term pa_prm_wf_item_key_s.
• PA_PROJECT_ASSIGNMENTS, PA_PROJECTS_ALL, PA_PROJECT_CUSTOMERS, PA_PROJECT_STATUSES, PA_PROJECT_TYPES_ALL — project and assignment context used for validation and eligibility checks.
• PA_RESOURCES_DENORM — the denormalized resource view used for candidate searches and availability checks.
• FND_USER, HR_ALL_ORGANIZATION_UNITS, HZ_CUST_ACCOUNTS, HZ_PARTIES — party, resource and recipient information for workflow routing and notifications.

Usage Notes

PA_CANDIDATE_PUB is normally invoked indirectly. The PRM OAF/Forms staffing pages call it when a project manager adds, copies, withdraws or declines a candidate. The Oracle Workflow engine invokes START_WORKFLOW and the notification-recipient functions during candidate review, using PA_PRM_WF_ITEM_KEY_S to obtain the item key. Concurrent programs and interfaces, including those built on PA_INTERFACE_UTILS_PUB and PA_R_PROJECT_RESOURCES_PUB, use the package to load or synchronize candidate data. Custom code should call the public procedures rather than touching PA_CANDIDATES directly, so that candidacy counters, workflow entries and audit logs remain consistent.