Search Results per_election_candidate_pk




Overview
Explore in AI Chat

Overview

The PER_ELECTION_CANDIDATES table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically for versions 12.1.1 and 12.2.2. As defined in the ETRM documentation, its primary function is to hold information of Election candidates. This table is integral to managing organizational elections, such as those for union representatives, works council members, or other formally elected positions. It operates within the HR schema and serves as the central repository for linking nominated individuals (candidates) to specific election events and the roles for which they are standing. Its status as a VALID table with a defined primary key underscores its operational importance in the application's data model.

Key Information Stored

The table's structure is designed to establish critical relationships within the HR data model. The primary key, ELECTION_CANDIDATE_ID, uniquely identifies each candidate record. As indicated by the foreign key constraints, the table stores several essential reference identifiers. The ELECTION_ID column links the candidate to a specific election event defined in the PER_ELECTIONS table. The ROLE_ID associates the candidate with the particular position or role (from PER_ROLES) they are contesting for. Furthermore, the BUSINESS_GROUP_ID ties the candidate record to the appropriate organizational security context within HR_ALL_ORGANIZATION_UNITS. While the explicit column list beyond the foreign keys is not detailed in the provided metadata, typical candidate information would include fields such as the person identifier (likely PERSON_ID), candidate status, nomination date, and result information (e.g., elected, votes received).

Common Use Cases and Queries

This table is primarily accessed for election administration and reporting. Common functional use cases include generating candidate nomination lists, creating ballots, and reporting election outcomes. From a technical perspective, frequent queries involve joining this table with related master data tables. A typical reporting query to list all candidates for an election would follow this pattern:

  • SELECT pec.election_candidate_id, per.full_name, prl.role_name, pel.election_name
  • FROM hr.per_election_candidates pec,
  • hr.per_all_people_f per,
  • hr.per_roles prl,
  • hr.per_elections pel
  • WHERE pec.person_id = per.person_id
  • AND pec.role_id = prl.role_id
  • AND pec.election_id = pel.election_id
  • AND pec.election_id = :p_election_id;

Data maintenance tasks, such as adding or inactivating candidates, are typically performed through the dedicated Oracle HRMS forms or APIs to maintain data integrity.

Related Objects

As explicitly documented in the foreign key metadata, PER_ELECTION_CANDIDATES has strong dependencies on several key HR tables. PER_ELECTIONS is the parent table for the election event definition. PER_ROLES defines the role or position being contested. HR_ALL_ORGANIZATION_UNITS (via BUSINESS_GROUP_ID) secures the data within the correct business group. It is also highly probable, though not listed, that the table references PER_ALL_PEOPLE_F or a similar person table to store the candidate's person identifier. The primary key constraint PER_ELECTION_CANDIDATE_PK ensures uniqueness. This table is likely referenced by other objects for reporting or to store subsequent election results, forming a key node in the HR elections data model.