Results for “person_first_name”

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

Overview

UMX_USER_PVT_V is a database view owned by the APPS schema in Oracle E-Business Suite, registered under the FND - Application Object Library product. As its description states, it is a view used exclusively by the proxy user feature — the functionality that allows one application user to operate on behalf of another, typically for delegated administration, workflow routing, or restricted-privilege access scenarios.

The view presents a consolidated, privacy-safe projection of FND_USER records, joined to either human resources person data or trading community party data depending on how each user account is provisioned. Because it is scoped to the proxy user feature, it should be treated as an internal implementation object rather than a general-purpose reporting view. The ETRM metadata records its status as VALID in both 12.1.1 and 12.2.2, with the view text and column list unchanged across those releases.

The user's search term "person_first_name" maps directly to the view's PERSON_FIRST_NAME column, which is one of its three heterogeneous identity attributes.

Underlying Base Objects

The view is defined over three referenced synonyms pointed at base tables:

• FND_USER — the core application user account table, supplying USER_NAME, USER_ID, EMAIL_ADDRESS, and the PERSON_PARTY_ID and EMPLOYEE_ID discriminator columns.
• HZ_PARTIES — the Trading Community Architecture party table, joined when the user is linked to a party but not to an employee.
• PER_ALL_PEOPLE_F — the HR date-tracked person table, joined when the user is linked to an employee.

The definition is a three-branch UNION ALL that segments the user population by linkage: users with no party and no employee (identity columns null); users linked to a party (name from HZ_PARTIES); and users linked to an employee (name from PER_ALL_PEOPLE_F, filtered to the currently effective date-tracked row).

Key Columns

• USER_NAME — the FND_USER login name.
• USER_ID — surrogate primary key of the user account, used for joins to FND responsibilities, roles, and preferences.
• EMAIL_ADDRESS — the registered notification address.
• PERSON_FIRST_NAME — given name, populated from PER_ALL_PEOPLE_F.FIRST_NAME for employees or HZ_PARTIES.PERSON_FIRST_NAME for parties, and NULL for unlinked users.
• PERSON_LAST_NAME — family name, resolved from the same two sources.
• PARTY_ID — TCA party identifier, populated only in the HZ_PARTIES branch.
• PERSON_ID — HR person identifier, populated only in the employee branch.

Common Use Cases and Queries

The view is consumed by proxy-user setup and by diagnostics that must display a friendly identity for an account without knowing in advance whether it is party-linked or employee-linked.

Resolving a display name for a user:

• SELECT user_name, person_first_name, person_last_name FROM umx_user_pvt_v WHERE user_id = :p_user_id;

Listing proxy candidates by name fragment:

• SELECT user_name, person_first_name, person_last_name FROM umx_user_pvt_v WHERE UPPER(person_first_name) LIKE UPPER('%'||:fragment||'%');

Segregating identity sources for reconciliation:

• SELECT user_name, party_id, person_id FROM umx_user_pvt_v WHERE party_id IS NOT NULL OR person_id IS NOT NULL;

Because the employee branch reads PER_ALL_PEOPLE_F with an effective-date filter, historical names are not returned; only the currently effective person record appears. Any custom code should read this view rather than replicate its UNION logic.