Results for “user_parties”

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

Overview

APPS.PO_SUPPLIER_USERS_V is a Purchasing (PO) module view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the association between Oracle Applications users (FND users) and the supplier organizations with which they are affiliated as contacts. The view joins FND_USER to the Trading Community Architecture (TCA) party model and to PO_VENDORS, returning a denormalized row set that combines user login attributes, party identity details, email contact points, and vendor (supplier) identifiers in a single queryable structure.

The view is primarily consumed for reporting and integration purposes — for example, identifying which application user corresponds to a supplier contact, populating supplier-facing self-service functionality, or driving iSupplier Portal and Supplier Lifecycle Management style queries. Because it wraps TCA relationship logic rather than storing data, it is a read-only construct with no DML support.

Underlying Base Objects

The documented base objects are FND_USER (synonym), HZ_CONTACT_POINTS (synonym), HZ_PARTIES (synonym), HZ_RELATIONSHIPS (synonym), and PO_VENDORS (view). The view text confirms the join topology:

• FND_USER joins to HZ_PARTIES via fnd_user.person_party_id = user_parties.party_id, linking the application user to their person party record.
• HZ_RELATIONSHIPS (aliased employment_relationship) supplies the contact linkage. The relationship is filtered on relationship_type = 'CONTACT', relationship_code = 'CONTACT_OF', object_type = 'ORGANIZATION', and subject_type = 'PERSON', with status = 'A'. The organization side is tied to po_vendors.party_id, and the person side to the user's party.
• PO_VENDORS provides supplier identifiers and the vendor name.
• HZ_CONTACT_POINTS is outer-joined ((+)) to supply the primary MAILTEXT email address for the party, restricted to contact_point_type = 'EMAIL', status = 'A', and primary_flag = 'Y'.

Key Columns

• FND_USER_ID — FND_USER.USER_ID; the application user identifier.
• FND_USER_NAME — FND_USER.USER_NAME; the login name of the user.
• FND_CUSTOMER_ID — FND_USER.CUSTOMER_ID; the customer account reference stored on the FND user record. This is the column most frequently sought by users searching for fnd_customer_id in relation to supplier-user mapping.
• USER_PARTY_ID / USER_PARTY_NAME — the TCA party identifier and name of the person associated with the user.
• USER_PARTY_FULL_NAME — concatenation of first, middle (conditionally), and last name from HZ_PARTIES.
• USER_PARTY_EMAIL_ADDRESS — primary email contact point.
• USER_PARTY_CITY / STATE / PROVINCE — address attributes from the party record.
• VENDOR_PARTY_ID — the supplier's party identifier (user_parties.party_id, aliased to the vendor side of the relationship).
• PO_VENDOR_ID / PO_VENDOR_NAME — supplier identifier and name from PO_VENDORS.

Common Use Cases and Queries

Typical scenarios include listing all users attached to a supplier, locating a user's email for supplier notification, and bridging FND user identity to supplier records for custom integrations or extracts.

SELECT fnd_user_name,
       fnd_customer_id,
       user_party_full_name,
       user_party_email_address,
       po_vendor_name
FROM   apps.po_supplier_users_v
WHERE  po_vendor_id = :vendor_id;

To retrieve a single user's supplier context by login:

SELECT po_vendor_id, po_vendor_name, fnd_customer_id
FROM   apps.po_supplier_users_v
WHERE  fnd_user_name = :user_name;

Note that the mandatory inner joins on HZ_RELATIONSHIPS and PO_VENDORS mean only active CONTACT_OF relationships to organizations that exist as suppliers are returned; users without a supplier contact relationship are excluded. No DML should be issued against the view.