Search Results hz_party_bo_pvt




Overview

HZ_PARTY_BO_PVT is a private PL/SQL package owned by the APPS schema within the Oracle E-Business Suite Trading Community Architecture (TCA) module. The suffix _PVT denotes an internal implementation package; it encapsulates the business-object logic that supports the public party APIs exposed across the Customer Relationship Management and Order-to-Cash application stacks. In Oracle EBS 12.1.1 and 12.2.2, HZ_PARTY_BO_PVT serves as the centralized engine that orchestrates creation, update, and retrieval of the composite structures that comprise a "party" — the master record representing a person or organization. Rather than acting as a directly callable interface, it functions as a shared internal service used by the HZ_*_BO_PUB packages, persisting relationships, classifications, certifications, financial profiles, preferences, and party usage assignments while managing message propagation and business events through the standard TCA framework.

Key Procedures and Functions

The package exposes nineteen documented procedures and functions, grouped by business object:

Tables Accessed

DML is performed against several TCA tables via APPS synonyms:

The package also references record/table types including HZ_RELATIONSHIP_OBJ_TBL, HZ_RELATIONSHIP_OBJ, HZ_CERTIFICATION_OBJ_TBL, HZ_CODE_ASSIGNMENT_OBJ_TBL, HZ_FINANCIAL_PROF_OBJ_TBL, HZ_MESSAGE_OBJ_TBL, HZ_PARTY_PREF_OBJ_TBL, and HZ_PARTY_USAGE_OBJ_TBL, and depends on FND_API.

Usage Notes

Because HZ_PARTY_BO_PVT is a private package, it is not intended for direct invocation by end users or custom code. It is invoked indirectly through the TCA public APIs — HZ_PERSON_BO_PUB, HZ_ORGANIZATION_BO_PUB, HZ_CONTACT_POINT_BO_PUB, HZ_CUST_ACCT_BO_PUB, HZ_LOCATION_BO_PUB, and related _BO_PUB packages, thirteen in total — that in turn drive it from Forms, concurrent programs, and the Trading Community Foundation import processes. Custom integrations should call the public _PUB interfaces rather than this package to preserve upgrade compatibility and validation logic. The presence of event- and message-related routines indicates it participates in TCA business events and error-stack handling, ensuring source-system references and messaging are propagated consistently across the 12.1.1 and 12.2.2 releases.