Results for “candidate_score”

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

Overview

PA_CANDIDATE_DETAILS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PA (Projects) product family. It consolidates candidate nomination data for project assignments into a single denormalized row per candidate, joining candidate records to resource, assignment, project, status, job, and organization attributes. The view is defined with a filter that excludes candidates whose project system status code equals CANDIDATE_SYSTEM_QUALIFIED, so its result set represents active or in-progress nominations rather than fully qualified candidates.

Because the view text embeds calls to PL/SQL functions, it behaves as a computed presentation layer rather than a simple join. Each row returned carries derived columns such as competence match, availability, assignment conflict flags, and a numeric candidate score. This makes the view suitable for candidate review pages, nomination dashboards, and downstream extracts where a flat, functionally enriched record is preferable to querying PA_CANDIDATES directly. The presence of the NOMINATION_COMMENTS column means free-text nomination rationale authored by a nominator is exposed alongside structured attributes.

Underlying Base Objects

Documented references in the view definition include the following base objects and packages:

• PA_CANDIDATES (SYNONYM) — primary source of candidate records, including status code, nomination date, nomination comments, and candidate ranking.
• PA_RESOURCES_DENORM (SYNONYM) — denormalized resource attributes such as resource name, resource ID, person ID, job level, schedulable flag, and effective dating.
• PA_PROJECT_ASSIGNMENTS (SYNONYM) — assignment start and end dates, project ID, and record version number.
• PA_PROJECT_STATUSES (SYNONYM) — project status name and project system status code, restricted to status type CANDIDATE.
• PER_JOBS (SYNONYM) — job definition joined through the resource job ID.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) — organization name, joined with an outer join on resource organization ID.
• PA_CANDIDATE_UTILS (PACKAGE) — supplies GET_RESOURCE_ID, GET_NOMINATOR_NAME, and GET_CANDIDATE_SCORE.
• PA_CANDIDATE_PUB (PACKAGE) — supplies IS_CAND_ON_ANOTHER_ASSIGNMENT, GET_COMPETENCE_MATCH, and CHECK_AVAILABILITY.

The join between PA_CANDIDATES and PA_RESOURCES_DENORM is effective-dated: the assignment start date must fall between the resource effective start date and the nvl of the resource effective end date, ensuring the resource attributes are valid at the time of the nomination.

Key Columns

The view exposes candidate identity columns (candidate number, candidate name, candidate resource ID, candidate person ID), assignment context (project ID, assignment ID, assignment start and end dates), and project context (project name, project status name, project system status code). Resource attributes include resource name, resource job level, resource organization ID, and organization name. Nomination attributes include status code, nominated-by person ID, nominator resource ID and nominator name derived through PA_CANDIDATE_UTILS, nomination date, nomination comments, and candidate ranking. Versioning is preserved through record version numbers on both the candidate and assignment records. Computed columns include the another-assignment indicator, competence match, availability check, and candidate score. Record browsing can be protected by the cached record version number, and code that updates candidates through the view should use the correct version token.

Common Use Cases and Queries

Typical uses include listing nominations awaiting decision, surfacing nomination comments for review, and filtering candidates by competence or availability. A representative query is:

• SELECT candidate_name, project_id, assignment_id, nomination_date, nomination_comments, candidate_ranking FROM pa_candidate_details_v WHERE project_id = :project_id AND status_code = :status_code ORDER BY nomination_date DESC.
• SELECT candidate_name, project_name, nominated_by_person_id, nomination_comments FROM pa_candidate_details_v WHERE nomination_date >= :from_date.

Because several columns are function-derived, queries over large candidate populations can be costly; restricting by project ID, assignment ID, or status code before evaluating computed columns improves performance materially.