Results for “per_person_dlvry_methods_v”

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

Overview

PER_PERSON_DLVRY_METHODS_V is a reporting and user-interface view in the Oracle E-Business Suite Human Resources (PER) module. It presents the delivery method assignments associated with a person, exposing both the raw assignment record and the decoded lookup meaning for the communication delivery method. The view is documented in ETRM as being "Used to support user interface," meaning that its primary design intent is to feed Oracle Forms/HTML-based UI regions that display a person's delivery methods (for example, e-mail, fax, or print delivery of notifications and correspondence) rather than to serve as a standalone transactional API object.

The view is defined in the PER schema and is available in both EBS 12.1.1 and 12.2.2. Because it is a simple join view — not a multi-org secured or business-group filtered view — it returns all rows visible to the querying user subject to standard data security applied at the underlying table level. The PREFERRED_FLAG column, which the user specifically searched for, identifies which delivery method a person has designated as their default or preferred channel of communication, and is one of the most frequently referenced columns from this view in reporting and integration scenarios.

Underlying Base Objects

The view is defined over two objects:

• PER_PERSON_DLVRY_METHODS (aliased PDM) — the base transactional table that stores one row per person / delivery method / date-range combination. It holds the DELIVERY_METHOD_ID primary key, the PERSON_ID foreign key to PER_ALL_PEOPLE_F, the COMM_DLVRY_METHOD lookup code, the PREFERRED_FLAG, the effective dates DATE_START and DATE_END, the OBJECT_VERSION_NUMBER for optimistic locking, and the standard 20 descriptive flexfield attributes (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20).
• HR_LOOKUPS (aliased HL1) — joined on PDM.COMM_DLVRY_METHOD = HL1.LOOKUP_CODE with the fixed predicate HL1.LOOKUP_TYPE = 'PER_CM_MTHD'. This join supplies the translated MEANING text for the delivery method so that the UI can display a human-readable label instead of the internal lookup code.

No additional documented base objects are referenced. The join is effectively an inner join, so any delivery method code that does not exist as an enabled value under the PER_CM_MTHD lookup type will be excluded from the result set.

Key Columns

• ROW_ID — the ROWID of the underlying PER_PERSON_DLVRY_METHODS record, useful for direct row addressing.
• DELIVERY_METHOD_ID — surrogate primary key of the assignment row.
• PERSON_ID — identifies the person to whom the delivery method is assigned; joins to PER_ALL_PEOPLE_F.
• COMM_DLVRY_METHOD — the lookup code (e.g., the internal code for e-mail or fax) drawn from the PER_CM_MTHD lookup type.
• MEANING — the decoded, user-facing description of the delivery method, sourced from HR_LOOKUPS.
• PREFERRED_FLAG — indicates whether this delivery method is the person's preferred (default) method; typically 'Y' or 'N'.
• DATE_START / DATE_END — effective date range for the assignment.
• OBJECT_VERSION_NUMBER — used by the UI and concurrent processes for optimistic locking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield segments available for client-specific extensions.

A D_COMM_DLVRY_METHOD column appears in the documented column list; this is a derived/display column (rather than one selected from the base table in the documented view text).

Common Use Cases and Queries

Typical uses include identifying each person's preferred delivery method, listing all delivery methods for a person, and validating that a person has exactly one preferred method configured. The following query returns the preferred delivery method for each person:

SELECT person_id, comm_dlvrry_method, meaning
FROM per_person_dlvry_methods_v
WHERE preferred_flag = 'Y';

A more comprehensive listing for a specific person, including all methods and their effective windows, would be:

SELECT person_id, comm_dlvrry_method, meaning, preferred_flag, date_start, date_end
FROM per_person_dlvry_methods_v
WHERE person_id = :p_person_id;

Because the view does not perform effective-date filtering internally, consumers that need only currently active assignments should add AND TRUNC(SYSDATE) BETWEEN NVL(date_start, TRUNC(SYSDATE)) AND NVL(date_end, TRUNC(SYSDATE)) or join to the effective-dated person record. Integration and reporting layers frequently reference this view when populating notification distribution lists or when validating delivery preferences supplied by external systems.