Search Results user_party

Overview

APPS.POS_SUPPLIER_USERS_V is a supplier-facing security and identity view in Oracle E-Business Suite, shipped under the Applications (APPS) schema. It resolves the relationship between a supplier organization and the individual Oracle EBS users who are authorized to act on that supplier's behalf, typically through the Oracle Supplier Network, iSupplier Portal, or other supplier-facing modules such as Purchasing and Payables. The view returns one row per supplier contact user that has an active trading relationship with a given vendor, exposing both the FND user identity (user_id, user_name) and the corresponding party-model identifiers (person_party_id, vendor_party_id, relationship_id).

The object is documented in ETRM 12.2.2 and is compatible with 12.1.1 through 12.2.2, since it depends on the Trading Community Architecture (TCA) and the FND security attribute framework that are present across those releases. Its practical role is to answer the question "which registered users belong to which suppliers," which underpins authorization checks in supplier self-service flows and is frequently joined into custom reporting or integration extracts where supplier-user mapping is required. The view is the natural target for a "user_party" search because the join condition FU.PERSON_PARTY_ID = USER_PARTY.PARTY_ID explicitly correlates the FND user's person party to the TCA party record.

Underlying Base Objects

Per the documented metadata, the view is defined over five referenced objects, all resolved through APPS synonyms except PO_VENDORS, which is itself a view:

• FND_USER — the EBS application user registry; supplies user_id, user_name, end_date, and person_party_id.
• HZ_PARTIES — the TCA party master, aliased as USER_PARTY, providing the person party record for the user.
• HZ_RELATIONSHIPS — the TCA relationship table linking the person party (subject) to the vendor organization party (object) via a 'CONTACT_OF' relationship.
• PO_VENDORS — the supplier view supplying vendor_id and the organization's party_id.
• AK_WEB_USER_SEC_ATTR_VALUES — the security attribute store; the filter on ATTRIBUTE_CODE = 'ICX_SUPPLIER_ORG_ID' and ATTRIBUTE_APPLICATION_ID = 177 confirms the user's security context is scoped to a specific supplier organization.

The join enforces that the relationship is active (HZR.STATUS = 'A'), typed 'CONTACT' / 'CONTACT_OF', and spans subject type 'PERSON' to object type 'ORGANIZATION'.

Key Columns

• USER_ID / USER_NAME — the FND_USER primary key and login identifier of the supplier contact.
• USER_END_DATE — FND_USER.END_DATE, indicating when the user login is deactivated.
• PERSON_PARTY_ID — the TCA party_id of the person behind the user; the pivot for joining HZ_PARTIES.
• VENDOR_PARTY_ID — the organization party_id of the supplier (PO_VENDORS.PARTY_ID).
• VENDOR_ID — the supplier identifier in PO_VENDORS, also matched against the security attribute value.
• RELATIONSHIP_ID / REL_PARTY_ID — the HZ_RELATIONSHIPS surrogate key and its party_id.
• END_DATE — the end date of the contact relationship, distinct from the user end date.

Common Use Cases and Queries

Typical uses include auditing which users are provisioned for a supplier, validating supplier-user access during integration testing, and populating responsibility or role assignments.

SELECT user_name, vendor_id, person_party_id, vendor_party_id
FROM   apps.pos_supplier_users_v
WHERE  vendor_id = :p_vendor_id;

To identify dormant users still holding supplier access:

SELECT user_name, vendor_id, user_end_date, end_date
FROM   apps.pos_supplier_users_v
WHERE  NVL(user_end_date, SYSDATE+1) <= SYSDATE
OR     NVL(end_date, SYSDATE+1) <= SYSDATE;

Because the view already encapsulates the FND, TCA, and security-attribute joins, it should be preferred over manually reconstructing those joins, ensuring consistent results with native supplier portal authorization logic.