Search Results hr.per_addresses




The PER_ADDRESSES table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical component of the Human Resources (HR) module, serving as the primary repository for storing address-related information for employees, contingent workers, applicants, and other person types. This table is part of the Oracle HRMS (Human Resource Management System) data model and is extensively used in core HR, payroll, and talent management processes. Below is a detailed technical and functional overview of the PER_ADDRESSES table.

Table Structure and Key Columns

The PER_ADDRESSES table stores address details with the following key columns:
  • ADDRESS_ID: Primary key, uniquely identifying each address record.
  • PERSON_ID: Foreign key linking to PER_ALL_PEOPLE_F, associating the address with a person.
  • DATE_FROM and DATE_TO: Define the validity period of the address (effective-dated structure).
  • ADDRESS_TYPE: Categorizes the address (e.g., HOME, WORK, MAILING).
  • ADDRESS_LINE1 to ADDRESS_LINE4: Street or location details.
  • TOWN_OR_CITY, REGION_1 (County/State), POSTAL_CODE, COUNTRY: Geographic identifiers.
  • PRIMARY_FLAG: Indicates if the address is the primary address for the person.
  • STYLE: Defines the address format (e.g., US, UK, JP).
  • TELEPHONE_NUMBER, FAX_NUMBER: Contact details associated with the address.

Functional Role in Oracle EBS

The PER_ADDRESSES table supports multiple business processes:
  1. Employee Data Management: Stores residential, mailing, and work addresses for HR records.
  2. Payroll and Tax Compliance: Used for tax jurisdiction determination and statutory reporting (e.g., W-2 forms in the US).
  3. Global Localization: Address styles ensure compliance with regional formatting requirements.
  4. Integration: Interfaces with third-party systems (e.g., payroll vendors, background check providers).

Technical Considerations

  • Effective Dating: Addresses are time-sensitive, allowing historical tracking and future-dated changes.
  • Indexing: Key columns like PERSON_ID and ADDRESS_ID are indexed for performance.
  • Validation: Country-specific validation rules are enforced via Oracle HRMS flexfields or APIs.
  • APIs: The HR_ADDRESS_API package provides programmatic access for CRUD operations.

Integration Points

The table interacts with:
  • PER_ALL_PEOPLE_F: Core person table.
  • PER_PERIODS_OF_SERVICE: Links addresses to employment periods.
  • Oracle Payroll (PAY_ASSIGNMENTS_F) for tax calculations.
  • Oracle Self-Service HR (SSHR) for employee address updates.

Customization and Extensions

Organizations often extend the table via:
  • Descriptive Flexfields (DFFs) for additional attributes.
  • Triggers or workflows to enforce business rules (e.g., mandatory home address for remote workers).
  • Custom APIs for bulk address imports or geocoding.

Best Practices

  1. Use Oracle-delivered APIs instead of direct DML to maintain data integrity.
  2. Leverage PRIMARY_FLAG to avoid duplicate primary addresses.
  3. Archive obsolete addresses rather than deleting them for audit trails.
In summary, the PER_ADDRESSES table is a foundational element in Oracle EBS HRMS, enabling accurate person data management, compliance, and integration across modules. Its effective-dated structure and localization features make it adaptable to global deployments while maintaining data consistency.