Results for “add_information17”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PER_ADDRESSES is the Human Resources (PER) module table that stores address information for people in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the HR schema and holds one row per address record associated with a person, allowing multiple addresses per person over time and across address types. The table is central to HR, Payroll, and iRecruitment functionality where person-level mailing, home, and correspondence addresses are required.

From a Data Vault modeling perspective, the documented foreign key structure classifies PER_ADDRESSES as hub-leaning. The primary key ADDRESS_ID functions as a surrogate key for the address entity itself, while BUSINESS_GROUP_ID anchors the record to a business group. This makes the table a natural candidate for a hub, with attribute columns such as address lines, postal code, telephone numbers, and descriptive flexfield attributes forming a satellite around it.

Key Information Stored

PER_ADDRESSES contains 63 columns in the documented 12.2.2 schema. The most significant are:

• ADDRESS_ID — the surrogate primary key, defined by the unique index PER_ADDRESSES_PK. This is the identifier referenced by downstream tables.
• PERSON_ID — the person to whom the address belongs, the principal business-key candidate linking addresses to people.
• BUSINESS_GROUP_ID — foreign key to HR_ALL_ORGANIZATION_UNITS, scoping the address to a business group.
• DATE_FROM and DATE_TO — effective dating that supports historical tracking of address changes.
• PRIMARY_FLAG — indicates the primary address for the person.
• STYLE and ADDRESS_TYPE — classify the address format and usage.
• ADDRESS_LINE1, ADDRESS_LINE2, ADDRESS_LINE3 — the street-level address components.
• TOWN_OR_CITY, REGION_1, REGION_2, REGION_3, POSTAL_CODE, COUNTRY — the geographic breakdown of the address.
• TELEPHONE_NUMBER_1 through TELEPHONE_NUMBER_3 — associated contact numbers.
• PARTY_ID — links the address to the trading community party model.
• ADDR_ATTRIBUTE_CATEGORY and ADDR_ATTRIBUTE1 through ADDR_ATTRIBUTE20 — the descriptive flexfield structure for extensible address data.
• OBJECT_VERSION_NUMBER — used for optimistic locking on updates.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, and related audit columns — standard EBS who-columns.

Common Use Cases and Queries

Typical reporting and integration scenarios retrieve a person's current primary address, historical addresses, or addresses for mailing and payroll purposes. A common pattern joins PER_ADDRESSES to PER_PEOPLE_F (or PER_ALL_PEOPLE_F) on PERSON_ID and filters on effective dates and PRIMARY_FLAG:

• Listing the current primary address for an employee: SELECT * FROM per_addresses WHERE person_id = :p AND primary_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN date_from AND NVL(date_to, TRUNC(SYSDATE)+1);
• Extracting mailing addresses by business group for correspondence runs, joining on BUSINESS_GROUP_ID.
• Feeding iRecruitment notification and offer processes, which reference ADDRESS_ID from IRC_NOTIFICATION_PREFERENCES and IRC_OFFERS.
• Auditing address changes over time using DATE_FROM and DATE_TO to build a slowly changing dimension.
• Bulk loading addresses via the HR Person Addresses API or SQL*Loader, validating against the descriptive flexfield columns.

Related Objects

• HR_ALL_ORGANIZATION_UNITS — referenced via PER_ADDRESSES.BUSINESS_GROUP_ID, defining the owning business group.
• IRC_NOTIFICATION_PREFERENCES — references PER_ADDRESSES.ADDRESS_ID for recruitment notifications.
• IRC_OFFERS — references PER_ADDRESSES.ADDRESS_ID for offer correspondence.
• PER_ALL_PEOPLE_F — the principal person table joined on PERSON_ID.
• PER_PERSON_ADDRESSES_V — a common view exposing address data for forms and reports.
• HZ_LOCATIONS and HZ_PARTIES — linked through PARTY_ID for trading community integration.