Search Results per_addresses




Overview
Explore in AI Chat

Overview

The PER_ADDRESSES table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HR) module. It serves as the central repository for storing address information associated with people, which includes employees, applicants, contacts, and other person types managed within the HR system. Its primary role is to maintain a comprehensive and normalized record of all personal and business addresses, enabling critical HR functions such as payroll processing, benefits administration, compliance reporting, and internal communication. The table's design supports multiple addresses per person, allowing for distinctions between primary, mailing, and work locations.

Key Information Stored

The table's structure is designed to capture detailed address components and contextual metadata. The primary key is the ADDRESS_ID, a unique system-generated identifier for each address record. A critical foreign key is BUSINESS_GROUP_ID, which links the address to a specific HR business group, enforcing data security and partitioning. Other significant columns typically include PERSON_ID (linking to PER_ALL_PEOPLE_F), ADDRESS_TYPE (e.g., Home, Work), DATE_FROM and DATE_TO for effective dating, and the core address fields such as ADDRESS_LINE_1, ADDRESS_LINE_2, ADDRESS_LINE_3, TOWN_OR_CITY, REGION_1 (county/state), POSTAL_CODE, and COUNTRY. The table also commonly contains validation and telephony columns like VALIDATED_FLAG and TELEPHONE_NUMBER_1.

Common Use Cases and Queries

A primary use case is generating reports for tax authorities, benefits providers, or internal directories that require current employee addresses. Another is auditing address history for compliance. Common SQL queries involve joining to person tables. For example, to find the primary mailing address for active employees:

  • SELECT papf.employee_number, papf.full_name, pa.address_line1, pa.town_or_city, pa.region_1, pa.postal_code
  • FROM per_addresses pa, per_all_people_f papf
  • WHERE pa.person_id = papf.person_id
  • AND SYSDATE BETWEEN papf.effective_start_date AND papf.effective_end_date
  • AND pa.address_type = 'MAIL'
  • AND pa.date_to IS NULL;

Integration with other modules, such as iRecruitment (IRC), is also fundamental, as indicated by the foreign keys from IRC_OFFERS and IRC_NOTIFICATION_PREFERENCES.

Related Objects

PER_ADDRESSES has integral relationships with several key HR and related module objects. As per the provided metadata, it references HR_ALL_ORGANIZATION_UNITS via BUSINESS_GROUP_ID. It is referenced by the iRecruitment tables IRC_NOTIFICATION_PREFERENCES and IRC_OFFERS via ADDRESS_ID. Crucially, it is linked to the master person table, PER_ALL_PEOPLE_F (though not listed in the excerpt, this is a foundational relationship). The primary key constraint is PER_ADDRESSES_PK on ADDRESS_ID. For programmatic access and data integrity, key HR APIs such as PER_ADDRESS_API are used to maintain this table instead of direct DML operations.