Search Results person_previous_last_name




Overview
Explore in AI Chat

Overview

UMX_PERSON_PVT_V is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 view owned by the APPS schema. It presents a filtered projection of party records that represent individual people rather than organizations. The view is defined over the HZ_PARTIES table (accessed through a synonym) and restricts its output using the predicate PARTY_TYPE = 'PERSON'. As a result, every row returned corresponds to a person party, making the view a ready-made source of person identity data without the caller needing to remember or re-apply the party type filter.

Within the Oracle EBS data model, person parties are the foundation of contacts, employees, users, suppliers' contacts, customers' contacts, and other human entities. The UMX prefix associates the object with the user management and person infrastructure introduced and expanded in the 12.x releases. Because the view is a private (PVT) object, it should be treated primarily as an internal or convenience access layer rather than a formally supported public API. Reporting and integration solutions that require person attributes can use it to obtain a consolidated person record spanning name, identifiers, contact details, and audit columns.

For the searched term person_previous_last_name, the view exposes the corresponding column PERSON_PREVIOUS_LAST_NAME. This is significant because prior-name information is frequently needed for identity verification, customer due diligence, and audit reporting, and it is not always surfaced in simpler person views.

Underlying Base Objects

The view is defined over a single documented base object: HZ_PARTIES, referenced through a synonym. HZ_PARTIES is the central table in the Oracle Trading Community Architecture (TCA) model and stores both person and organization parties. The view applies the PARTY_TYPE = 'PERSON' filter directly against this table, and it selects a subset of HZ_PARTIES columns without performing joins to related tables such as HZ_PERSON_PROFILES or HZ_CONTACT_POINTS.

Consequently, the view inherits the update semantics, audit triggers, and partitioning behavior of HZ_PARTIES. Columns sourced from HZ_PARTIES remain subject to the underlying table's constraints and validation rules, and no denormalization or transformation is applied beyond the party type restriction and column selection.

Key Columns

Common Use Cases and Queries

Typical uses include person lookups by name or identifier, extraction of contact and address data for interfaces, audit reporting on who last changed a person record, and identification of prior-name data for compliance review.

Retrieve a person by party identifier, including the prior last name:

  • SELECT party_id, party_name, person_first_name, person_last_name, person_previous_last_name FROM apps.umx_person_pvt_v WHERE party_id = :p_party_id;

Search by last name and phonetic match:

  • SELECT party_id, party_name, person_last_name, person_last_name_phonetic FROM apps.umx_person_pvt_v WHERE person_last_name = :p_last_name;

List persons whose previous last name is populated, useful for name-change audits:

  • SELECT party_id, party_name, person_last_name, person_previous_last_name, last_updated_by, last_update_date FROM apps.umx_person_pvt_v WHERE person_previous_last_name IS NOT NULL ORDER BY last_update_date DESC;

Extract contact and address details for an interface:

  • SELECT party_id, party_number, email_address, address1, city, state, postal_code, country FROM apps.umx_person_pvt_v WHERE status = 'A';

Because the object is a private view over TCA data, query performance depends on the indexes on HZ_PARTIES, and callers should filter on indexed columns such as PARTY_ID or PARTY_NUMBER wherever possible.