Search Results hz_org_contacts_s




Overview
Explore in AI Chat

Overview

HZ_ORG_CONTACTS_PKG is the primary PL/SQL package for managing organization contact records within the Oracle E-Business Suite Trading Community Architecture (TCA) data model. The organization contact entity represents the relationship between a contact person (a party of type PERSON) and a specific organization (a party of type ORGANIZATION), including the contact's role, job title, department, and status at that organization. This package encapsulates the low-level CRUD (Create, Read, Update, Delete) operations performed against the HZ_ORG_CONTACTS and HZ_ORG_CONTACTS_S tables, shielding callers from the underlying multi-table TCA structure and providing a controlled interface for manipulating association records.

The package body is documented as VALID in the APPS schema and is classified under the TCA API category. It is a foundational utility layer leveraged by higher-level TCA public APIs and by the Oracle Forms-based Contacts and Customers user interfaces.

Key Procedures and Functions

The package exposes five documented procedures, each mapped to a standard operation against the organization contact entity:

  • INSERT_ROW — Creates a new organization contact association, inserting the base record into HZ_ORG_CONTACTS and propagating the associated translation/denormalized segments into HZ_ORG_CONTACTS_S. The procedure establishes the party relationship between the contact and the organization.
  • UPDATE_ROW — Modifies an existing organization contact record, updating contact role, responsibility, title, or other descriptive attributes on both the base and supplemental tables.
  • LOCK_ROW — Obtains a row-level lock on the specified organization contact record to enforce optimistic concurrency control, preventing conflicting updates when multiple sessions operate against the same contact.
  • SELECT_ROW — Retrieves the column values of a single organization contact record into PL/SQL out-parameters, allowing callers to read the record without issuing ad-hoc SQL.
  • DELETE_ROW — Removes an organization contact association, deleting the corresponding rows from the base and supplemental tables and thereby severing the relationship between the contact person and the organization.

Parameter lists are not reproduced here; callers should always reference the actual package specification to confirm argument order, mandatory parameters, and any WHO-column context values.

Tables Accessed

  • HZ_ORG_CONTACTS — The primary base table storing organization-to-contact associations. It is the central target of the INSERT_ROW, UPDATE_ROW, SELECT_ROW, and DELETE_ROW operations.
  • HZ_ORG_CONTACTS_S — The supplemental table holding denormalized or translation-related columns for the organization contact. The package maintains consistency between the base and supplemental rows on insert, update, and delete.
  • DUAL — The standard Oracle single-row utility table, used for trivial lookups and constant evaluation within the package logic.

The package additionally depends on APP_EXCEPTION, FND_API, FND_MESSAGE, FND_MSG_PUB, and HZ_UTILITY_V2PUB, which provide error handling, the common TCA API framework, and message retrieval. These dependencies confirm that the package follows the standard EBS API error-stack and message conventions.

Usage Notes

HZ_ORG_CONTACTS_PKG is typically invoked indirectly by higher-level TCA public APIs (such as the contact creation and update routines) and by Oracle Forms used within the Customers, Contacts, and Trading Community modules. It is not referenced by any database object, meaning it is intended to be called from PL/SQL code and Forms triggers rather than from triggers or views.

Because it is a lower-level utility package rather than a public, committed interface, customizations should generally call the documented TCA public APIs instead of this package directly. Where direct use is required — for example, in custom data-migration or integration routines that must load organization contacts in bulk — developers must supply the correct WHO columns, handle FND_API exceptions, and honor the LOCK_ROW/UPDATE_ROW concurrency protocol to avoid lost updates. The object name users search for as "hz_org_contacts_s" corresponds both to this supplemental table and, in practice, to the table manipulated by this package.