Results for “candidate_system_qualified”

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

Overview

APPS.PA_CANDIDATE_DETAILS_V is a reporting and integration view in the Oracle E-Business Suite Projects (PA) module that consolidates candidate-level resource staffing information. In Oracle EBS 12.1.1 and 12.2.2, this view presents each candidate record alongside its associated resource, project assignment, project status, job, and organization attributes, together with several computed indicators derived from PL/SQL package functions. It is primarily used by staffing, resource management, and project assignment workflows, including the Candidate Search and assignment nomination functionality surfaced through the Projects application and associated web-based UIs.

A defining characteristic of this view is its filtering logic. The view joins candidate rows to project statuses where the status type is 'CANDIDATE', and explicitly excludes records whose project system status code equals CANDIDATE_SYSTEM_QUALIFIED. It also restricts resources to those with a schedulable flag of 'Y' and validates that an assignment's start date falls within the resource effective date range. As a result, the view returns only viable, non-disqualified candidates who remain eligible for consideration.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_CANDIDATES — the driving table, supplying candidate details such as status, ranking, nomination metadata, and record version.
• PA_RESOURCES_DENORM — provides resource-level attributes including resource name, resource ID, person ID, job level, resource organization, and the schedulable flag.
• PA_PROJECT_ASSIGNMENTS — supplies assignment context: project ID, start and end dates, and record version number.
• PA_PROJECT_STATUSES — joined on status code and filtered to status type 'CANDIDATE', providing project status name and project system status code.
• PER_JOBS and HR_ALL_ORGANIZATION_UNITS — supply the job name and organization name; the organization join is outer (+) to preserve rows lacking organization data.

Two PL/SQL packages are referenced through scalar function calls embedded in the view text: PA_CANDIDATE_UTILS and PA_CANDIDATE_PUB. These compute derived values that cannot be expressed in pure SQL, making the view dependent on the integrity and performance of those packaged APIs.

Key Columns

• CANDIDATE_ID / ASSIGNMENT_ID — primary candidate and assignment identifiers.
• RESOURCE_ID / PERSON_ID / RESOURCE_NAME — identifiers and name of the staffing resource.
• PROJECT_ID / NAME — the project the assignment belongs to.
• STATUS_CODE / PROJECT_STATUS_NAME / PROJECT_SYSTEM_STATUS_CODE — candidate status and the corresponding project status; the system status code is the value filtered against CANDIDATE_SYSTEM_QUALIFIED.
• RESOURCE_JOB_LEVEL, RESOURCE_ORGANIZATION_ID, organization name (ORG.NAME) — qualification and organizational context.
• NOMINATED_BY_PERSON_ID, nominator resource ID and name, NOMINATION_DATE, NOMINATION_COMMENTS — nomination metadata resolved via PA_CANDIDATE_UTILS.
• CANDIDATE_RANKING, RECORD_VERSION_NUMBER — ranking and optimistic-locking version.
• PA_CANDIDATE_PUB.Is_Cand_On_Another_Assignment(...) — flags candidates already committed elsewhere.
• PA_CANDIDATE_PUB.Get_Competence_Match(...) — competence fit for the assignment.
• PA_CANDIDATE_PUB.Check_Availability(...) — availability indicator for the project.
• PA_CANDIDATE_UTILS.Get_Candidate_Score(...) — composite candidate score used for ranking.

Common Use Cases and Queries

Typical scenarios include reviewing eligible candidate pools for an assignment, auditing nomination activity, and feeding candidate data into external staffing reports.

SELECT candidate_id, resource_name, project_id, assignment_id,
       project_status_name, candidate_ranking, get_candidate_score
  FROM apps.pa_candidate_details_v
 WHERE project_id = :p_project_id
 ORDER BY candidate_ranking;

Because the search term candidate_system_qualified corresponds to the excluded system status, the view is often the reference point for confirming that records with that status are omitted:

SELECT candidate_id, status_code, project_system_status_code
  FROM apps.pa_candidate_details_v
 WHERE status_code = 'CANDIDATE_SYSTEM_QUALIFIED';

-- Returns no rows: the view definition filters these out.

Callers should note that the embedded PL/SQL function calls execute per row, so queries against large candidate sets can incur performance overhead and benefit from predicate pushdown on CANDIDATE_ID, ASSIGNMENT_ID, or PROJECT_ID.