Search Results f type usage per person




Deep Dive into Oracle EBS PER Tables and Views

Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 leverage a comprehensive set of tables and views within the PER (Human Resources) schema to manage workforce data, organizational structures, and employee lifecycle processes. These database objects form the backbone of Oracle HRMS (Human Resource Management System), enabling core functionalities such as personnel administration, payroll, benefits, and talent management.

Key PER Tables in Oracle EBS

  • PER_ALL_PEOPLE_F: Stores employee and contingent worker records with effective-dated attributes (e.g., name, gender, date of birth). This is the central table for person data.
  • PER_ALL_ASSIGNMENTS_F: Tracks assignment details (jobs, positions, departments) with effective dates, linking employees to organizational units.
  • PER_PERIODS_OF_SERVICE: Maintains employment history, including hire/termination dates and service periods.
  • PER_GRADES: Defines grade structures for compensation and career progression frameworks.
  • PER_JOBS: Contains job definitions with attributes like job codes, titles, and job families.
  • PER_POSITIONS: Manages position hierarchies, budgets, and reporting relationships.

Critical PER Views for Reporting

Oracle EBS provides views that simplify data extraction while enforcing security rules (VPD - Virtual Private Database):

  • PER_PEOPLE_F: Combines person data from PER_ALL_PEOPLE_F with additional descriptive flexfields (DFFs).
  • PER_ASSIGNMENTS_F: Aggregates assignment data with DFFs and joins to organization/job tables.
  • PER_ORG_STRUCTURE_V: Provides hierarchical organization structures for reporting.
  • PER_PERSON_TYPE_USAGES_F: Identifies employee classifications (e.g., full-time, contractor).

Technical Considerations

  • Effective Dating: Most PER tables use EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to track historical changes.
  • Multi-Org Security: Data access is controlled via ORG_ID columns and MOAC (Multi-Org Access Control) in 12.2.
  • Integration Points: PER tables interface with PAY (Payroll), BEN (Benefits), and IRC (Recruiting) modules.

Customization Best Practices

When extending PER objects:

  • Use Descriptive Flexfields (DFFs) for custom attributes rather than modifying core tables.
  • Leverage API packages (e.g., HR_PERSON_API, HR_ASSIGNMENT_API) for data modifications to maintain integrity.
  • Create custom views with HR_SECURITY predicates to ensure row-level security compliance.

Performance Optimization

For large-scale implementations:

  • Partition PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F by EFFECTIVE_END_DATE.
  • Create function-based indexes on frequently queried DFF attributes.
  • Use materialized views for complex organizational hierarchy reports.

Understanding these PER tables and views is essential for Oracle EBS HRMS implementations, custom reporting, and data migration projects. The schema's design supports global HR requirements while maintaining flexibility through extensibility features.