Search Results per_requisitions

Overview

The PER_REQUISITIONS table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HR) module. It serves as the master repository for storing vacancy requisition details. A requisition represents a formal, approved request to fill a position or create a new one, initiating the recruitment and hiring workflow. This table is fundamental to the recruitment life cycle, as it defines the job, location, required qualifications, and other critical parameters against which candidates are sourced and vacancies are created. Its integrity is maintained by primary and unique key constraints, ensuring each requisition is uniquely identifiable within the system.

Key Information Stored

The table's structure is designed to capture comprehensive requisition data. The primary key, REQUISITION_ID, uniquely identifies each record. As indicated by the metadata, the table also enforces a unique key constraint (PER_REQUISITIONS_UK2) on the combination of NAME and BUSINESS_GROUP_ID, preventing duplicate requisition names within a single business group. The BUSINESS_GROUP_ID column is a critical foreign key linking the requisition to its governing HR organization unit (HR_ALL_ORGANIZATION_UNITS). While the provided excerpt lists only these key columns, a full implementation typically includes numerous other attributes such as the associated job (JOB_ID), position (POSITION_ID), organization (ORGANIZATION_ID), required start date, approval status, and detailed descriptive flexfield segments for organization-specific information.

Common Use Cases and Queries

This table is central to recruitment reporting and process management. Common operational and analytical queries include listing all active requisitions, tracking requisition status, and analyzing time-to-fill metrics. For instance, a report to find approved requisitions within a specific business group might use a SQL pattern like:

• SELECT pr.name, pr.requisition_id, pr.date_from FROM hr.per_requisitions pr WHERE pr.business_group_id = &bg_id AND pr.approved = 'Y' AND SYSDATE BETWEEN pr.date_from AND NVL(pr.date_to, SYSDATE);

Integration points include using the REQUISITION_ID to create vacancies in the PER_ALL_VACANCIES table, as mandated by the documented foreign key relationship. Data from this table is also frequently accessed via standard Oracle HRMS APIs for creating, updating, and managing requisitions programmatically.

Related Objects

PER_REQUISITIONS has defined relationships with several other key HR objects, forming the backbone of the recruitment data model. The primary foreign key relationship is with PER_ALL_VACANCIES, where a vacancy is a specific opening created from a requisition. This is a one-to-many relationship, as a single requisition can generate multiple vacancies. Secondly, the BUSINESS_GROUP_ID column establishes a foreign key relationship with HR_ALL_ORGANIZATION_UNITS, anchoring the requisition within the correct organizational and security context. In practice, this table is also closely linked to PER_JOBS, PER_POSITIONS, and HR_ALL_ORGANIZATION_UNITS_TL for descriptive information, and is accessed through public views like PER_REQUISITIONS_V for secure, translatable data access.