Search Results hz_party_sites_pkg




Overview
Explore in AI Chat

Overview

HZ_PARTY_SITES_PKG is the core PL/SQL package body in the Oracle E-Business Suite Trading Community Architecture (TCA) that provides the low-level data access layer for the HZ_PARTY_SITES entity. A party site represents the association between a party (a person or organization) and a physical location, and it is the anchor record from which addresses, contact points, and location assignments are derived. In EBS 12.1.1 and 12.2.2, this package encapsulates the insert, update, lock, select, and delete operations against the party site tables, allowing higher-level TCA APIs and forms to manipulate party site records without issuing direct DML.

The package is owned by the APPS schema and is classified as an OTHER API rather than a public, external-facing TCA API. Its implementation depends on the FND_API error-handling framework, FND_MSG_PUB and FND_MESSAGE for message management, FND_LOG for debug logging, FND_PROFILE for session context, and HZ_UTILITY_V2PUB for shared TCA utility routines. The ETRM metadata confirms the package body status is VALID and that it is referenced by two other database objects.

Key Procedures and Functions

The documented interface exposes five procedures, each addressing one facet of the party site record lifecycle:

  • INSERT_ROW — Creates a new party site row, populating the base HZ_PARTY_SITES record and its associated HZ_PARTY_SITES_S (secure/translated) row, and generating the party site number through HZ_PARTY_SITE_NUMBER_S.
  • UPDATE_ROW — Modifies an existing party site record, applying changes to the base table and the corresponding _S row while preserving appropriate audit columns.
  • LOCK_ROW — Obtains a row-level lock on a party site record to enforce concurrency control during concurrent updates.
  • SELECT_ROW — Retrieves a single party site record by its primary key, returning the full column set for use by callers such as forms or other TCA APIs.
  • DELETE_ROW — Removes a party site record and its dependent _S row from the underlying tables.

No parameter lists are published in the ETRM metadata; callers should reference the package specification for exact signatures.

Tables Accessed

The package operates against the following documented tables through APPS synonyms:

  • HZ_PARTY_SITES — The primary table storing party site records; subject to insert, update, lock, select, and delete operations.
  • HZ_PARTY_SITES_S — The secure/translated companion table holding language-dependent or secured attributes (such as the party site name), maintained in parallel with the base table.
  • HZ_PARTY_SITE_NUMBER_S — Used to generate and store the party site number identifier during insert operations.
  • DUAL — Referenced for single-row SQL expressions and sequence or number generation queries.

Usage Notes

HZ_PARTY_SITES_PKG is typically invoked indirectly rather than directly by end users. TCA forms such as the Party and Customer forms call higher-level public APIs, which in turn delegate to this package's row-level procedures. It is also consumed by other TCA packages and interfaces that need to create or maintain party site records during customer, supplier, or contact data loads.

Because the package is classified as OTHER and performs physical DML on the base tables, it is not the recommended entry point for external integrations. Custom code should prefer the supported public TCA APIs (for example, HZ_PARTY_SITE_V2PUB and related public packages) that enforce validation, business rules, and proper message handling. Direct calls to INSERT_ROW, UPDATE_ROW, or DELETE_ROW bypass these safeguards and should be reserved for controlled internal use. The dependency on FND_API and FND_MSG_PUB indicates that the procedures return standard API status and message information, and callers should check the returned status before proceeding.