Search Results mail_destination




Overview
Explore in AI Chat

Overview

APPS.PER_ALL_PEOPLE_D is a supplementary database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema and registered in FND Design Data as PER.PER_ALL_PEOPLE_D. Its status is VALID. Oracle classifies it as a supplementary view used to simplify Forms coding, and the ETRM documentation explicitly warns that Oracle does not recommend querying or altering data through this view, since its definition may change dramatically in subsequent minor or major releases. Despite this caveat, the view is widely referenced in custom reports, extracts, and integrations that require a flat, denormalized presentation of person records.

Within the Oracle EBS reporting model, PER_ALL_PEOPLE_D acts as a presentation-layer convenience object rather than a base table. It projects the core person attributes from the HR person model, including name components, employment identifiers, and personal information, into a single row-per-effective-date structure. The view is populated through the referenced HR packages and views rather than by direct DML, which reinforces its read-only, reporting-oriented intent. Users searching for the column MAIL_DESTINATION will find it exposed here as a VARCHAR2(80) attribute, typically used to identify an internal or external mail routing destination associated with the person record.

Underlying Base Objects

The ETRM metadata for PER_ALL_PEOPLE_D lists the following referenced base objects: FND_USER (SYNONYM), HR_API (PACKAGE), HR_GENERAL (PACKAGE), HR_LOOKUPS (VIEW), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), PER_PEOPLE_F (VIEW), PER_PERSON_TYPES (SYNONYM), and PER_PERSON_TYPES_TL (SYNONYM).

The primary source of person rows is PER_PEOPLE_F, the date-tracked (effective-dated) base view over the PER_ALL_PEOPLE_F table, which supplies PERSON_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and most descriptive person attributes. PER_PERSON_TYPES and PER_PERSON_TYPES_TL provide the person type classification and its translated system name, which the view uses to filter and label records. HR_LOOKUPS supplies decoded lookup values for attributes such as MARITAL_STATUS, SEX, DISABLED, and STUDENT_STATUS. HR_PERSON_NAME and the HR_API, HR_GENERAL, and HR_SECURITY packages are invoked to derive formatted name elements (FULL_NAME, KNOWN_AS, PRE_NAME_ADJUNCT, SUFFIX) and to enforce row-level security, restricting visible person records according to the querying user's security profile. FND_USER links the person to an application user account where applicable. Because the view is a stored definition rather than a materialized object, all results are resolved at query time from these underlying objects.

Key Columns

The view exposes thirty-three columns. The most significant include:

  • PERSON_ID — NUMBER(10); the primary identifier for the person record, joining to PER_PEOPLE_F and other HR tables.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-track boundaries for each row, essential for point-in-time reporting.
  • LAST_NAME, FIRST_NAME, MIDDLE_NAMES, FULL_NAME, KNOWN_AS, PREVIOUS_LAST_NAME, PRE_NAME_ADJUNCT, SUFFIX — name components and the derived formatted name.
  • EMPLOYEE_NUMBER — VARCHAR2(30); the business-facing employee identifier.
  • EMAIL — VARCHAR2(240); the person's electronic mail address.
  • MAIL_DESTINATION — VARCHAR2(80); the internal or external mail routing designation, often populated from location or assignment data, and the column of interest to users searching this term.
  • BIRTH_DATE, DATE_LAST_VERIFIED, SOCIAL_SECURITY_NUMBER, NATIONALITY — personal and identification attributes.
  • MARITAL_STATUS, DISABLED, SEX, TITLE, WORK_SCHEDULE, STUDENT_STATUS, HONORS — decoded descriptive attributes sourced from HR_LOOKUPS.
  • FTE_CAPACITY — NUMBER; full-time equivalent capacity for the person.
  • ON_MILITARY_SERVICE, SECOND_PASSPORT_EXISTS — status indicators.
  • OFFICE_NUMBER, INTERNAL_LOCATION, MAILSTOP — physical work location attributes.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY — audit columns reflecting the most recent change to the underlying record.

Common Use Cases and Queries

Typical scenarios include employee directory and contact extracts, mail routing and distribution-list reconciliation using MAIL_DESTINATION, identity and personal-data audits, and third-party or interface feeds requiring a denormalized person record. A basic lookup by person identifier might appear as:

SELECT person_id, full_name, employee_number, email, mail_destination, effective_start_date, effective_end_date FROM apps.per_all_people_d WHERE employee_number = :emp_num AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

To list current mail destinations for active persons:

SELECT p.person_id, p.full_name, p.mail_destination, p.email FROM apps.per_all_people_d p WHERE SYSDATE BETWEEN p.effective_start_date AND p.effective_end_date AND p.mail_destination IS NOT NULL ORDER BY p.full_name;

Because HR_SECURITY is referenced, results are automatically constrained by the querying user's security profile, which must be accounted for when validating row counts. Given the documented Oracle warning, custom code should treat PER_ALL_PEOPLE_D as an unstable interface and, where long-term stability is required, prefer querying PER_PEOPLE_F directly or the public HR APIs.