Results for “per_person_dlvry_methods”

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

Overview

PER_PERSON_DLVRY_METHODS is a Human Resources (PER) module table in the Oracle E-Business Suite, owned by the HR schema. It stores the communication delivery method associated with a person, effectively recording how an individual prefers or is configured to receive communications such as email, fax, SMS, or print. The table is classified as VALID in the ETRM metadata for releases 12.1.1 and 12.2.2.

From a heuristic Data Vault modeling perspective, PER_PERSON_DLVRY_METHODS is classified as standalone. This suggests that the object functions largely as an independent entity within the mined foreign-key structure, rather than participating in an explicit hub-and-link topology. In practice it behaves as a satellite-like record of a person's delivery preferences, keyed to the person and the delivery method, and does not appear to be a hard dependency target for other tables in the subset analyzed.

Key Information Stored

The table is physically documented with 37 columns. The most important columns for functional and reporting use are:

• DELIVERY_METHOD_ID — The surrogate primary key, defined by the PER_PERSON_DLVRY_METHODS_PK index. Uniquely identifies each delivery method row.
• PERSON_ID — The person for whom the delivery method is recorded. This is the primary business-key component in PER_PERSON_DLVRY_METHODS_UK1.
• COMM_DLVRY_METHOD — The communication delivery method itself (for example, the delivery method type). This is the second component of the unique business key PER_PERSON_DLVRY_METHODS_UK1.
• PREFERRED_FLAG — Indicates whether this delivery method is the preferred option for the person.
• DATE_START and DATE_END — Define the effective date range during which the delivery method record is active.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent updates.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard WHO audit columns.
• REQUEST_ID, PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID — Concurrent program and request traceability columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — The standard Oracle EBS descriptive flexfield (DFF) columns for extensibility.

The surrogate key DELIVERY_METHOD_ID is distinct from the business-key candidate PER_PERSON_DLVRY_METHODS_UK1, which enforces uniqueness on the combination of PERSON_ID and COMM_DLVRY_METHOD.

Common Use Cases and Queries

Typical scenarios include retrieving the preferred delivery method for a specific person, auditing delivery method history using the effective dates, and generating reports on preferred communication channels across a population.

A representative query to return all active delivery methods for a person is:

• SELECT delivery_method_id, person_id, comm_dlvry_method, preferred_flag FROM per_person_dlvry_methods WHERE person_id = :p_person_id AND SYSDATE BETWEEN date_start AND NVL(date_end, SYSDATE);

To identify the preferred method:

• SELECT person_id, comm_dlvry_method FROM per_person_dlvry_methods WHERE person_id = :p_person_id AND preferred_flag = 'Y';

For reporting, joining to the person and delivery method lookups by PERSON_ID and COMM_DLVRY_METHOD provides the descriptive names needed for analytics and downstream communication processes.

Related Objects

The following objects are most significant when working with PER_PERSON_DLVRY_METHODS, based on the documented relationship data and standard PER schema conventions:

• PER_ALL_PEOPLE_F — Joins on PERSON_ID to supply person identifying information.
• PER_ALL_ASSIGNMENTS_F — Joins on PERSON_ID for assignment context in HR reporting.
• FND_COMMUNICATION_DELIVERY_METHODS (or equivalent delivery method lookup) — Provides the description for COMM_DLVRY_METHOD.
• PER_PERSON_DLVRY_METHODS_PK and PER_PERSON_DLVRY_METHODS_UK1 — The indexes enforcing the surrogate primary key and business-key uniqueness.
• PER_PEOPLE_API — Public HR APIs that can maintain person-level delivery method data.

The table is treated as standalone in the mined FK structure, so dependent objects should be verified against the PER module's documented interfaces for a given implementation.