Search Results known_as2




Overview
Explore in AI Chat

Overview

UMX_PERSON_PVT_V is a private view owned by the APPS schema in Oracle E-Business Suite, classified under the FND – Application Object Library product. It is documented in ETRM as a private view used by UMX (User Management) to secure person records stored in the TCA (Trading Community Architecture) data model. The view exposes a curated projection of person-type party records, presenting both identity attributes and a denormalized primary address, and is intended for internal consumption by UMX components rather than for direct customer extension. The view exists in both 12.1.1 and 12.2.2, and its metadata status is VALID.

The object is significant because it bridges user-management identity functions with TCA party data, which is the authoritative repository for persons, organizations, and relationships in EBS. When the user searched for "known_as3," the relevant fact is that KNOWN_AS3 is one of the columns projected by this view, reflecting the "Known As" alternate-name fields (KNOWN_AS, KNOWN_AS2 through KNOWN_AS5) carried on HZ_PARTIES.

Underlying Base Objects

Per the documented metadata, UMX_PERSON_PVT_V is defined over HZ_PARTIES, accessed through a synonym. The defining query selects columns directly FROM HZ_PARTIES with the restrictive predicate WHERE PARTY_TYPE = 'PERSON'. Consequently, the view is a subset of the TCA party table containing only person rows; organization parties are excluded by the filter. No joins are declared in the view text, so the address columns (ADDRESS1 through EMAIL_ADDRESS) are sourced from HZ_PARTIES itself or from columns that are projected as part of the person's primary location attributes as stored at the party level.

Key Columns

Common Use Cases and Queries

The view is used internally by UMX to resolve person identity and display names, including known-as variants, when rendering user administration screens, approvals, and worklist attributes. It is equally useful as a read-only reporting source for person data where full HZ_PARTIES access is not warranted or where the consumer must be restricted to persons only.

Example — retrieve persons by known-as name:

  • SELECT party_id, party_name, known_as, known_as2, known_as3, known_as4, known_as5
  • FROM apps.umx_person_pvt_v
  • WHERE known_as3 IS NOT NULL
  • AND UPPER(known_as3) LIKE UPPER(:p_name)||'%';

Example — return person identity with primary address:

  • SELECT party_id, party_number, person_first_name, person_last_name,
  • city, state, postal_code, email_address
  • FROM apps.umx_person_pvt_v
  • WHERE party_type IS NULL
  • AND status = 'A';

Because the view is private and its filter enforces PARTY_TYPE = 'PERSON', customers should avoid building permanent customizations against it; unsupported changes to the view text in patches may alter column availability. Where stable access is required, referencing HZ_PARTIES directly with an equivalent person predicate is the recommended alternative.