Search Results per_requisitions




Overview
Explore in AI Chat

Overview

PER_REQUISITIONS is a Human Resources (PER) module table in Oracle E-Business Suite that stores vacancy requisition details. It is owned by the HR schema and is valid in both EBS 12.1.1 and 12.2.2. In the Oracle HRMS recruitment workflow, a requisition represents an authorized request to fill one or more open positions within a business group. Requisitions function as the parent entity for vacancies: a single requisition may be linked to multiple vacancy records in PER_ALL_VACANCIES, each capturing a specific opening derived from the original hiring request.

Under the heuristic Data Vault classification shown in the ETRM metadata, PER_REQUISITIONS is described as satellite-leaning. This suggests that the object is best modeled as a descriptive satellite surrounding a requisition hub, with its business attributes and audit columns tracked over time. The classification is a modeling suggestion rather than a strict architectural mandate, but it reflects the table's role as a carrier of descriptive vacancy requisition detail rather than a pure relationship link or a standalone hub.

Key Information Stored

The table contains 39 documented columns. The most significant are summarized below.

Common Use Cases and Queries

Recruitment reporting frequently joins requisitions to their associated vacancies. The primary linkage runs through REQUISITION_ID:

  • Listing all open vacancies for a given requisition: SELECT v.VACANCY_ID, v.NAME FROM PER_ALL_VACANCIES v, PER_REQUISITIONS r WHERE v.REQUISITION_ID = r.REQUISITION_ID AND r.REQUISITION_ID = :id;
  • Reporting requisitions by business group: filter on BUSINESS_GROUP_ID and join HR_ALL_ORGANIZATION_UNITS for the organization name.
  • Extracting DFF context using ATTRIBUTE_CATEGORY combined with the ATTRIBUTE1–20 values for regulatory or departmental coding.
  • Auditing: querying LAST_UPDATED_BY and LAST_UPDATE_DATE to trace change history for compliance reporting.

Because the table is satellite-leaning, ETL and data-vault style extractions typically stage requisition rows keyed by REQUISITION_ID with associated audit metadata to preserve historical changes.

Related Objects

  • PER_ALL_VACANCIES — References PER_REQUISITIONS via PER_ALL_VACANCIES.REQUISITION_ID; this is the primary child table carrying vacancy-level detail.
  • HR_ALL_ORGANIZATION_UNITS — Referenced by BUSINESS_GROUP_ID; supplies the business group definition for the requisition.
  • EDW_HR_RQVC_REQUISTN_LTC and EDW_HR_RQVC_REQUISTN_LSTG — Enterprise Data Warehouse staging and load tables that reference REQUISITION_ID for requisition-level reporting.
  • EDW_HR_RQVC_VACANCY_LSTG and EDW_HR_RQVC_VACANCY_LTC — Warehouse staging tables joining requisitions to vacancy listings and load structures.
  • PER_REQUISITIONS_PK and PER_REQUISITIONS_UK2 — The unique indexes that enforce the surrogate and business keys respectively.

Together these objects support the end-to-end recruitment data model, from requisition creation through vacancy publication and downstream analytical reporting.