Search Results hz_contact_points_s




Overview
Explore in AI Chat

Overview

HZ_CONTACT_POINTS_PKG is the core PL/SQL package that encapsulates the transactional logic for the HZ_CONTACT_POINTS entity within the Oracle E-Business Suite Trading Community Architecture (TCA). In Oracle EBS 12.1.1 and 12.2.2, contact points represent the communication channels associated with a party or party site: telephone numbers, e-mail addresses, fax numbers, web URLs, and similar contact mechanisms. This package body (owner APPS, status VALID) provides the low-level insert, update, lock, query, and delete operations that the higher-level TCA public APIs rely upon to persist contact point records.

The package exhibits the layered architecture typical of TCA: HZ_CONTACT_POINTS_PKG handles row-level persistence and concurrency, while its sibling package HZ_UTILITY_V2PUB and the PL/SQL API framework (FND_API, FND_MESSAGE, FND_MSG_PUB, APP_EXCEPTION) manage validation, error-stack propagation, and message resolution. The dependency list confirms that HZ_CONTACT_POINTS_PKG references HZ_CONTACT_POINTS_PKG recursively (internal calls) and calls into the TCA utility package, indicating that it is a foundational component rather than a public-facing entry point.

Key Procedures and Functions

The ETRM documentation identifies five procedures in the package body:

  • INSERT_ROW — Creates a new contact point record in the base table. It is the primary write path used when a new phone number, e-mail address, or other communication method is attached to a party or party site.
  • UPDATE_ROW — Modifies an existing contact point record, applying changes such as updated contact details, status flags, or primary/active indicators while maintaining audit columns.
  • LOCK_ROW — Acquires a row-level lock to enforce optimistic concurrency control. It is invoked before an update or delete to prevent conflicting modifications from concurrent sessions.
  • SELECT_ROW — Retrieves a single contact point row by its primary key, returning the entity's attributes through OUT parameters for use by callers performing read or validation logic.
  • DELETE_ROW — Removes a contact point record from the base table. Depending on the TCA convention, this may perform a logical or physical delete, with the _S shadow table maintaining referential consistency.

The presence of these procedures alongside FND_MSG_PUB and FND_API references indicates that each operation participates in the standard EBS API control pattern, raising and propagating messages through the FND message stack rather than returning raw exceptions.

Tables Accessed

All tables are accessed through APPS synonyms, consistent with standard TCA schema conventions:

  • HZ_CONTACT_POINTS — The primary base table holding contact point records. Insert, update, select, and delete operations on this table constitute the package's main purpose.
  • HZ_CONTACT_POINTS_S — The shadow (intersection/denormalized) table. Writes to the base table require corresponding maintenance of this structure to keep dependent processing and staged operations synchronized.
  • DUAL — The conventional Oracle dummy table, used for single-row queries such as sequence lookups, primary key resolution, or simple validation checks within the package logic.

No additional application tables appear in the documented dependency list, reinforcing that this package is tightly scoped to contact point persistence.

Usage Notes

HZ_CONTACT_POINTS_PKG is not intended for direct invocation from end-user forms. The ETRM metadata shows that it is referenced by two other packages, which act as the intermediaries: the TCA public APIs (for example, HZ_CONTACT_POINT_V2PUB) and internal TCA utility routines call these procedures after completing validation, relationship resolution, and messaging. Customer-facing forms and concurrent programs therefore reach this package indirectly.

Because the majority of its documented procedures are procedural mappings of standard EBS API behaviors, the package can also be invoked from custom PL/SQL in the same controlled fashion — that is, within the TCA API transaction boundary, with FND_MSG_PUB initialized, and without bypassing the validation performed by the calling public API. Direct DML against HZ_CONTACT_POINTS outside these entry points is not supported. Readers searching for "hz_contact_points_s" will typically encounter this shadow table in the context of bulk data movement, staging, and denormalized processing driven by the package body described above.