Search Results create_cust_site_use




Overview

APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT is an Oracle E-Business Suite private PL/SQL package that supports the customer account merge process within the Trading Community Architecture (TCA) and Receivables (AR) modules. It is declared with AUTHID CURRENT_USER and carries the "PVT" suffix convention, indicating it is a private implementation package rather than a public API. The package encapsulates the low-level operations required to read, construct, and persist the records that make up a customer's party, party site, site use, contact, and relationship data during merge processing.

Rather than presenting a single merge entry point, the package exposes granular helper procedures that create and retrieve the discrete components of a customer record — party records, relationships, contacts, sites, site uses, customer accounts, and profiles. These procedures are consumed by the higher-level merge engine, which orchestrates them to consolidate duplicate or related customer accounts. The package relies heavily on the TCA public API record types (for example, hz_party_v2pub.party_rec_type and hz_relationship_v2pub.relationship_rec_type), reusing the same structures that underpin the published party and customer APIs.

Key Procedures and Functions

The package documents 15 procedures spanning several functional groups:

The user's search term, get_party_site_use_rec, corresponds precisely to the GET_PARTY_SITE_USE_REC procedure documented above, which returns the site use record used to associate a party site with a usage context during merge operations.

Tables Accessed

The package reads and writes the core TCA and Receivables tables through APPS synonyms:

Usage Notes

As a private package, HZ_CUST_ACCOUNT_MERGE_V2PVT is not intended for direct customer invocation. It is referenced by two other packages within the EBS codebase and is typically executed from the customer account merge concurrent program or from the merge form logic. Custom code should never call this package directly because its interface may change without notice; integrators should instead use the corresponding public TCA APIs. It is present in both 12.1.1 and 12.2.2, though the file header dates to 2005 and is marked noship, reflecting its long-standing internal role.