Search Results get_party_phone

Overview

CSI_PARTIES_PKG is a lightweight PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite. It is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking session rather than the definer, a pattern typical of shared helper packages that must respect row-level security and MOAC (Multi-Org Access Control) policies enforced at the calling context. The package's documented source header ($Header: csixptss.pls 115.2 2002/11/12) indicates it originated in the late 11i era and has remained stable through 12.1.1 and 12.2.2 with no functional revision.

The package supplies simplified, single-purpose read accessors that return a Trading Community Architecture (TCA) party's primary communication channel data — telephone, e-mail, and facsimile — as scalar VARCHAR2 values. It exists to insulate callers from the structural complexity of the TCA contact model, where communication methods are stored as rows in HZ_CONTACT_POINTS with type, purpose, and primary-flag attributes rather than as simple columns. Code that needs "just the e-mail address" for a party can call one function instead of writing a multi-join query against the TCA contact point tables.

The API classification recorded in the ETRM metadata is OTHER, confirming that this is a documentation-level utility rather than a supported public interface with an API lifecycle and compatibility guarantee. It is intended primarily for internal use by Oracle application code and by extension developers who require the same conveniences.

Key Procedures and Functions

The package exposes three functions, all of which accept a party identifier and return a VARCHAR2. No procedures are documented.

• GET_PARTY_EMAIL — Returns the e-mail address associated with the specified party. This is the function most commonly located by developers searching for party e-mail retrieval logic. It encapsulates the lookup of the party's electronic contact point and returns the address as a string suitable for direct use in message generation, notification, or display.
• GET_PARTY_PHONE — Returns telephone information for the specified party. The documented signature includes both a party identifier and a telephone type parameter, allowing the caller to distinguish among the multiple phone designations TCA permits (for example, business, mobile, or fax-related entries) rather than assuming a single number exists.
• GET_PARTY_FAX — Returns the fax number associated with the specified party, using the party identifier alone.

Each function provides a stable, single-value return contract, which allows callers to embed the invocation directly in SQL SELECT lists, PL/SQL assignments, or report expressions without managing cursors or result sets.

Tables Accessed

The ETRM metadata documents a single underlying table accessed through an APPS synonym: HZ_CONTACT_POINTS. This is the central TCA table that stores all contact point instances for parties, locations, and contacts, including phone numbers, e-mail addresses, fax numbers, URLs, and other electronic channels. Each row carries a contact point type, a primary indicator, and the actual formatted value, along with time-zone and formatting attributes.

All three functions derive their results from this table. The type-specific functions effectively filter HZ_CONTACT_POINTS by the relevant contact point type — e-mail, telephone, or fax — for the given party, and typically prioritize the contact point flagged as primary when more than one exists. No insert, update, or delete activity is documented; the package is strictly read-only, making it safe to invoke from forms, concurrent programs, and queries without transactional side effects.

Usage Notes

Because the package functions return plain scalar values and perform no DML, they are suitable for a wide range of invocation contexts:

• Custom PL/SQL and SQL. The functions can be called directly from anonymous blocks, stored procedures, or the SELECT list of a query. Under AUTHID CURRENT_USER, the caller's session privileges and TCA security policies apply, so results are naturally constrained by the caller's data access.
• Concurrent programs and reports. Notification, correspondence, and extract processes frequently need a party's e-mail or fax for output generation; these are the archetypal consumers of GET_PARTY_EMAIL and GET_PARTY_FAX.
• Forms and personalizations. Oracle Forms code and form personalization actions can call the package to populate message text or default field values from a party identifier already held in the block.
• Dependency awareness. The metadata records that the package is referenced by one other package. Changes to TCA contact point semantics, particularly primary-flag behavior, could alter results for downstream consumers, so any review of e-mail or fax retrieval logic should account for this dependency chain.

Developers should treat CSI_PARTIES_PKG as a convenience wrapper rather than a supported public API. Where richer behavior is required — multiple e-mail addresses, contact-point purpose filtering, or time-zone handling — direct queries against HZ_CONTACT_POINTS using the standard TCA contact point views remain the recommended approach.