Search Results hz_party_preferences_pkg




Overview
Explore in AI Chat

Overview

HZ_PARTY_PREFERENCES_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It operates within the Oracle Trading Community Architecture (TCA) and provides the low-level data access layer for party preferences—records that capture a trading party's stated choices, contact restrictions, communication channel opt-ins, and similar characteristics used in customer and supplier relationship processing. Party preferences are consumed by marketing, order management, and contact-center functions that determine how an organization prefers to be contacted or transacted with.

The package is classified as an OTHER API in the ETRM metadata. Its status is VALID, confirming it is compiled and available at runtime. It delegates internal dependencies to the SYS schema's STANDARD package, which is typical of packages relying on standard PL/SQL constructs and Oracle built-in datatypes.

Key Procedures and Functions

The ETRM documentation records four procedures and functions in this package. Each represents a distinct operation on the party preference record set, and the naming convention follows Oracle's standard DML wrapper pattern.

  • INSERT_ROW — Creates a new party preference record in the underlying table. It is the entry point for capturing a preference for a party, such as a do-not-contact flag or a preferred communication channel.
  • UPDATE_ROW — Modifies an existing party preference record, supporting changes to preference values without creating a new row.
  • DELETE_ROW — Removes a party preference record, used when a preference is no longer applicable to the party.
  • LOCK_ROW — Acquires a row-level lock on a party preference record, typically used to serialize concurrent modifications and ensure that update and delete operations act on a consistent snapshot of the row.

The metadata does not document parameter signatures for these procedures; consumers should therefore rely on the package specification source rather than assuming argument lists. The uniform INSERT/UPDATE/DELETE/LOCK pattern strongly indicates that this package acts as a private or semi-private persistence helper rather than a richly abstracted business API.

Tables Accessed

The package accesses a single documented table, HZ_PARTY_PREFERENCES, through an APPS synonym. This table is the TCA repository for party-level preference data, keyed to the party entity within the HZ schema family. All four documented procedures map directly to operations against this table:

  • INSERT_ROW writes new preference rows into HZ_PARTY_PREFERENCES.
  • UPDATE_ROW modifies column values on existing rows.
  • DELETE_ROW removes rows no longer required.
  • LOCK_ROW performs a select-for-update style lock against the row to protect it during a transaction.

No other tables are documented as dependencies for this package, which reinforces its role as a narrow, single-table persistence wrapper.

Usage Notes

HZ_PARTY_PREFERENCES_PKG is referenced by HZ_PREFERENCE_PUB, the public TCA preference API. This arrangement indicates that application code, Oracle forms, and concurrent programs should invoke the public API (HZ_PREFERENCE_PUB) rather than calling HZ_PARTY_PREFERENCES_PKG directly. The public package provides validation and business-rule enforcement before delegating to this lower-level package for the actual DML.

Typical invocation paths include the Customer and Party maintenance forms in TCA, contact-center preference screens, and custom integrations that need to persist or amend party preference data. Because the package is a persistence-layer component, direct calls from custom code bypass validation logic embedded in the public API and should be avoided except in controlled migration or data-fix scenarios. The presence of LOCK_ROW confirms that the package anticipates concurrent access to the same party's preferences.