Search Results per_applications

Overview

The PER_APPLICATIONS table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically under the PER product family. It serves as the primary repository for storing records of applications for employment. This table is fundamental to the recruitment and hiring lifecycle, capturing the initial candidate submission and linking it to subsequent HR actions such as assignment creation. As a base table owned by the HR schema, it maintains the system of record for all job applications within an EBS implementation, forming a critical link between prospective candidates and the organization's workforce structure.

Key Information Stored

The table's primary key is the APPLICATION_ID, a unique system-generated identifier for each application record. A crucial foreign key relationship is maintained via the BUSINESS_GROUP_ID column, which links the application to a specific organizational unit defined in the HR_ALL_ORGANIZATION_UNITS table. This enforces data security and multi-organization support. While the provided metadata does not list all columns, typical data stored includes candidate personal details (name, contact information), the applied-for position, application source (e.g., referral, agency), application date, current status (e.g., Received, In Review, Hired), and associated supporting documents. The table tracks the lifecycle of an application from submission through to its final disposition.

Common Use Cases and Queries

This table is central to recruitment reporting and operational processes. Common use cases include generating applicant tracking reports, analyzing recruitment source effectiveness, and managing the candidate pipeline. A typical query might join PER_APPLICATIONS with PER_PEOPLE_F to retrieve detailed candidate profiles for applications within a specific business group and status. The direct foreign key relationship to PER_ALL_ASSIGNMENTS_F indicates that upon hiring, a successful application record is used to create an employee assignment. A critical reporting query often involves identifying applications that have transitioned to assignments to measure time-to-hire metrics.

• Sample SQL: SELECT pa.application_id, pa.last_name, pa.application_date, pa.status FROM hr.per_applications pa WHERE pa.business_group_id = :p_bg_id AND pa.application_date > SYSDATE - 30;
• Use Case: Auditing the application-to-hire process by joining PER_APPLICATIONS to PER_ALL_ASSIGNMENTS_F on APPLICATION_ID.

Related Objects

PER_APPLICATIONS is integrally connected to several other key HR objects. Its most significant relationship is with the PER_ALL_ASSIGNMENTS_F table, which holds assignment records for employees, contingent workers, and applicants. The APPLICATION_ID foreign key in PER_ALL_ASSIGNMENTS_F creates the definitive link between an application and the resulting employment assignment. Furthermore, the table is linked to the HR_ALL_ORGANIZATION_UNITS table via the BUSINESS_GROUP_ID foreign key, anchoring each application to the correct organizational context. For comprehensive candidate information, it is typically joined with person-related tables such as PER_PEOPLE_F. Customizations and integrations should utilize standard Oracle HR APIs rather than direct DML on this table to maintain data integrity.