Search Results hz_user_party_utils




Overview
Explore in AI Chat

Overview

APPS.HZ_USER_PARTY_UTILS is a utility package in the Oracle E-Business Suite Trading Community Architecture (TCA) / Receivables stack, shipped under the ARHUSRPB.pls source file. Its stated purpose is to resolve or create a TCA party record based on a user's email address—the identifier referenced by the search term pv_email_address. In Oracle EBS 12.1.1 and 12.2.2, TCA separates "parties" (the master entity) from "users" (FND_USER login accounts) and from contact points (email addresses, phones). This package provides the bridge logic that finds whether a party already exists for a given email, and if not, creates one, returning the party identifier. This supports customer-facing self-service registration and guest checkout flows where a party must be established or reused before orders, relationships, or contact points can be recorded.

Key Procedures and Functions

ETRM documents a single public entry point, plus a private helper declared in the package body. Note that parameter lists are not invented here; only documented names and purposes are described.

  • GET_USER_PARTY_ID — The primary public function. Per the embedded comments, it "tries to find a party based on email-address. If party is found the party id is returned. If the party is NOT found a new party is created and party id returned." Documented inputs include user name, first name, last name, and the email address (pv_email_address); it returns the party identifier and a return status. This is the routine most relevant to the pv_email_address search.
  • CREATE_PER_PERSON_PARTY — A package-body-level procedure (prototype declared in the body) that accepts a PER person identifier and returns a party identifier via an OUT NOCOPY parameter. It is used internally by GET_USER_PARTY_ID to materialize a party when no match is found, linking the HR/PER person record to the newly created TCA party.

The package also declares standard FND_MSG_PUB message-level constants (unexpected error, error, success, and debug high/medium/low) used for the return-status and message-stack conventions typical of TCA PL/SQL APIs.

Tables Accessed

The documented table list reflects the lookup-and-insert pattern described in the header comments:

  • HZ_PARTIES — Read to search for an existing party by name/email context and written when a new party must be created.
  • HZ_CONTACT_POINTS — Read to match the email address (pv_email_address); the contact point is what associates an email with a party, so this is central to the lookup.
  • HZ_PARTY_NUMBER_S — Sequence used to generate the party number for newly created parties.
  • HZ_RELATIONSHIPS — Establishes the relationship between the party and related entities (for example, person-to-organization or contact role associations).
  • FND_USER — Read to correlate the application user login with the party.
  • PER_ALL_PEOPLE_F — Read when resolving or creating a person party from an HR person record.
  • DUAL — Used for single-row scalar operations (sequence lookups, constant selection).

Usage Notes

This is a low-level utility rather than a form-bound API, so it is typically invoked from custom PL/SQL, other TCA packages, or self-service registration logic that must resolve a party from a user's email. ETRM records that it is referenced by two other packages, confirming its role as a shared internal dependency. When invoking it, callers should treat the party creation as transactional and check the returned status and FND_MSG_PUB message stack before committing. Because behavior differs subtly across 12.1.1 and 12.2.2 (12.2.x moved to a unified online patching model and Java-based OAF pages), the package should be used as shipped—modifying it directly invalidates its support status. The pv_email_address input maps to the email contact point lookup, which is the intended key for party resolution.