Results for “user_party_id”

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

Overview

PO_SUPPLIER_USERS_V is a Purchasing (PO) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, reporting-friendly projection of the relationship between Oracle EBS application users (FND_USER records) and the supplier organizations with which they are affiliated. The view resolves the trading community data model — the HZ_PARTIES and HZ_RELATIONSHIPS constructs introduced with Oracle Trading Community Architecture (TCA) — into a single denormalized row per active supplier user, exposing both the user's party identity and the associated vendor identity.

The object is frequently referenced during reporting and integration work involving supplier self-service, iSupplier Portal user provisioning, and procurement analytics. Users searching for po_vendor_name are typically attempting to resolve a vendor name from a user record or to join user-level data to supplier data; PO_SUPPLIER_USERS_V exposes exactly this mapping through the PO_VENDOR_NAME and PO_VENDOR_ID columns.

Underlying Base Objects

The documented base objects referenced by this view are FND_USER (SYNONYM), HZ_PARTIES (SYNONYM), HZ_RELATIONSHIPS (SYNONYM), HZ_CONTACT_POINTS (SYNONYM), and PO_VENDORS (VIEW). The view text confirms the core joins:

• FND_USER.CUSTOMER_ID is joined to HZ_PARTIES.PARTY_ID to obtain the user's party record (aliased USER_PARTIES).
• HZ_RELATIONSHIPS with RELATIONSHIP_TYPE = 'POS_EMPLOYMENT' and RELATIONSHIP_CODE = 'EMPLOYEE_OF' links the user party (SUBJECT_ID) to the company party (OBJECT_ID), constrained to the current date range.
• HZ_RELATIONSHIPS with RELATIONSHIP_TYPE = 'POS_VENDOR_PARTY' and RELATIONSHIP_CODE = 'PARTY_OF_VENDOR' links the company party (SUBJECT_ID) to the vendor (OBJECT_ID), also date-constrained.
• PO_VENDORS supplies VENDOR_ID and VENDOR_NAME, joining PO_VENDORS.VENDOR_ID to the vendor-side relationship OBJECT_ID.

Because PO_VENDORS is itself a view rather than a base table, the resolution chain ultimately reaches PO_VENDORS_ALL and the underlying supplier tables. All EMPLOYMENT and VENDOR relationships are filtered by START_DATE <= SYSDATE and END_DATE >= SYSDATE, so only currently effective affiliations are returned.

Key Columns

• FND_USER_ID, FND_USER_NAME — the application user identifier and login name from FND_USER.
• FND_CUSTOMER_ID — the user's CUSTOMER_ID value, which is the party identifier used in TCA relationships.
• USER_PARTY_ID, USER_PARTY_NAME — the TCA party ID and party name for the user.
• USER_PARTY_FULL_NAME — concatenation of first, middle (optional), and last person names.
• USER_PARTY_EMAIL_ADDRESS — the user party's registered email address.
• USER_PARTY_CITY, USER_PARTY_STATE, USER_PARTY_PROVINCE — address attributes of the user party.
• VENDOR_PARTY_ID — the TCA party ID of the supplier company.
• PO_VENDOR_NAME, PO_VENDOR_ID — the supplier name and vendor identifier from PO_VENDORS; PO_VENDOR_NAME is the column most directly relevant to the po_vendor_name search term.

Common Use Cases and Queries

Typical scenarios include identifying which application users belong to a given supplier, extracting supplier user contact details for iSupplier Portal administration, and joining procurement data to the responsible supplier user. A basic query retrieving the vendor name for a specific user is:

• SELECT fnd_user_name, po_vendor_name, po_vendor_id, user_party_email_address FROM po_supplier_users_v WHERE fnd_user_name = :user_name;
• SELECT po_vendor_id, po_vendor_name, COUNT(*) FROM po_supplier_users_v GROUP BY po_vendor_id, po_vendor_name; — counts active users per supplier.
• SELECT fnd_user_name, user_party_full_name, po_vendor_name FROM po_supplier_users_v WHERE po_vendor_id = :vendor_id ORDER BY fnd_user_name;

Because the view enforces current-date relationship filters, results reflect only presently active supplier-user employment affiliations; historical reporting should query HZ_RELATIONSHIPS directly with appropriate date predicates.