Search Results per_requisitions

The PER_REQUISITIONS table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical data structure within the Human Resources (HR) module, specifically designed to manage and store requisition-related information. Requisitions in Oracle HRMS represent formal requests for new or replacement positions, enabling organizations to streamline workforce planning, recruitment, and hiring processes. This table serves as the backbone for requisition management, linking to other core HR tables to maintain data integrity and support business workflows. ### **Key Attributes of PER_REQUISITIONS** The table contains several essential columns that define requisition details, including: - **REQUISITION_ID**: The primary key, uniquely identifying each requisition. - **BUSINESS_GROUP_ID**: Associates the requisition with a specific business unit, ensuring organizational alignment. - **ORGANIZATION_ID**: Links the requisition to the department or division where the position is required. - **JOB_ID**: References the job definition from PER_JOBS, specifying the role being requisitioned. - **POSITION_ID**: Ties the requisition to a specific position in HR_ALL_POSITIONS_F (if position management is enabled). - **DATE_FROM** and **DATE_TO**: Define the active period of the requisition. - **STATUS**: Tracks the requisition lifecycle (e.g., "Draft," "Approved," "Closed"). - **APPROVED_FLAG**: Indicates whether the requisition has been authorized. - **DESCRIPTION**: Free-text field for additional requisition details. ### **Integration with Other Modules** The PER_REQUISITIONS table integrates with multiple Oracle EBS modules: 1. **Recruitment (PER)**: Links to PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F to track candidates and hires. 2. **Position Management**: References HR_ALL_POSITIONS_F if positions are used instead of jobs. 3. **Approvals (WF)**: Utilizes Oracle Workflow for requisition approval routing. 4. **Financials (GL, PO)**: May interface with General Ledger or Purchasing for budget validation. ### **Business Process Flow** 1. **Requisition Creation**: HR or hiring managers create requisitions, specifying job, location, and other criteria. 2. **Approval Workflow**: The requisition undergoes approval based on organizational hierarchy and budget checks. 3. **Recruitment**: Approved requisitions trigger recruitment activities, visible in PER_REQUISITIONS. 4. **Fulfillment**: Once filled, the requisition status updates to "Closed," and the candidate is assigned via PER_ALL_ASSIGNMENTS_F. ### **Technical Considerations** - **Indexes**: Key indexes on REQUISITION_ID, BUSINESS_GROUP_ID, and JOB_ID optimize query performance. - **Audit Trails**: Changes may be logged in PER_REQUISITIONS_ITL (interim table) for auditing. - **APIs**: Oracle provides PL/SQL APIs (e.g., HR_REQUISITION_API) for programmatic requisition management. ### **Customization and Extensions** Organizations often extend PER_REQUISITIONS via: - **Descriptive Flexfields (DFFs)**: Adding custom attributes like "Urgency Level" or "Hiring Manager Notes." - **Triggers**: Automating status updates or validations. - **Reports**: Leveraging BI Publisher or Oracle Reports for requisition analytics. ### **Conclusion** The PER_REQUISITIONS table is a foundational component of Oracle EBS HRMS, enabling structured workforce planning and recruitment. Its integration with core HR, position management, and workflow systems ensures seamless requisition lifecycle management. Understanding its structure and relationships is essential for HR administrators, implementers, and developers working with Oracle EBS 12.1.1 or 12.2.2.