Search Results pv_return_status




Overview

APPS.HZ_USER_PARTY_UTILS is a PL/SQL utility package in the Oracle E-Business Suite Trading Community Architecture (TCA) layer. Its documented responsibility is the resolution and provisioning of party records for system users. The package exposes a single public procedure, GET_USER_PARTY_ID, which attempts to locate an existing TCA party based on a user's email address and, when no matching party exists, creates a new party and returns the newly generated party identifier. The package is declared with AUTHID CURRENT_USER, meaning that name resolution and privilege checking for unqualified references execute under the privileges of the invoking schema rather than the package owner.

The package header carries the source control identifier ARHUSRPS.pls, revision 120.1, dated 16-June-2005, and the original procedure was authored on 25-May-2001. This provenance places the package within the Receivables/TCA family of user-party integration utilities, and its presence in the ETRM 12.2.2 metadata confirms that it remains available in the later 12.2.x code line as well as the 12.1.1 release.

Key Procedures and Functions

The package exposes exactly one documented public program unit:

  • GET_USER_PARTY_ID — Searches for a party record associated with a supplied email address. If a party is found, the corresponding party identifier is returned to the caller. If no party is found, the procedure creates a new party and returns the identifier of that newly created record. The procedure accepts the user name, first name, last name, and email address as input, and returns the party identifier and a return status indicating the outcome of the operation. It is declared with NOCOPY OUT parameters for the party identifier and return status.

The documented parameter names confirm the relevance of the search term "pv_user_name": PV_USER_NAME, PV_FIRST_NAME, PV_LAST_NAME, and PV_EMAIL_ADDRESS are the inbound values, while PN_PARTY_ID and PV_RETURN_STATUS are the outbound values. No other public procedures or functions are documented for this package.

Tables Accessed

The ETRM metadata lists the following tables as referenced through APPS synonyms:

  • HZ_PARTIES — The master party entity. This is the primary table read during the email-based lookup and written when a new party must be created.
  • HZ_CONTACT_POINTS — Stores the email address contact point associated with a party; used to match the supplied email address to an existing party.
  • HZ_PARTY_NUMBER_S — The sequence source used to generate a unique party number when inserting a new party record.
  • HZ_RELATIONSHIPS — Records relationships between parties, which may be established or referenced as part of party provisioning.
  • FND_USER — The EBS application user repository, linking the EBS user account to the TCA party.
  • PER_ALL_PEOPLE_F — The HR person denormalized view, referenced to correlate user records with person and party data.
  • DUAL — Used for scalar evaluations and sequence-style selection within the procedure logic.

Usage Notes

The package is intended for internal TCA and user-provisioning flows. It is referenced by two other packages in the ETRM inventory, indicating that it functions as a shared helper rather than a standalone entry point. Typical invocations arise from custom PL/SQL that must guarantee a party exists for a given user identity before creating relationships, contact points, or account assignments. Because the procedure creates a party when none is found, callers should be aware that invocation has a side effect: repeated calls with the same email address resolve to the same party, but calls with previously unseen email addresses will insert new party records. The return status parameter should always be checked by callers before using the returned party identifier. In 12.1.1 and 12.2.2 deployments, the package is owned by APPS and should be invoked with the standard EBS initialization and MOAC considerations applied to TCA API calls.