Search Results get_relationship_rec
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:
- GET_PARTY_REC — retrieves a fully populated party record for a given party identifier, returning the record structure along with standard API return status, message count, and message data.
- CREATE_RELATIONSHIP and GET_RELATIONSHIP_REC — create a party relationship and retrieve an existing relationship record (respecting a directional flag), respectively.
- CREATE_ORG_CONTACT and GET_ORG_CONTACT_REC — create and retrieve organization contact records, including the associated party relationship and party identifiers.
- CREATE_PARTY_SITE and GET_PARTY_SITE_REC — create and retrieve party site records.
- CREATE_PARTY_SITE_USE and GET_PARTY_SITE_USE_REC — create and retrieve party site use records, which link a site to a specific purpose such as billing or shipping.
- CREATE_CUST_ACCT_SITE and CREATE_CUST_SITE_USE — create customer account site and customer site use records.
- CREATE_CUSTOMER_PROFILE and CREATE_CUST_PROFILE_AMT — create customer profile and customer profile amount records.
- CREATE_CONTACT_POINT and GET_CONTACT_POINT_REC — create and retrieve contact point records (phone, email, and similar contact mechanisms).
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:
- HZ_PARTIES — the master party entity record.
- HZ_PARTY_SITES and HZ_PARTY_SITE_USES — physical site addresses and their usage assignments.
- HZ_CUST_ACCT_SITES_ALL — customer account site associations.
- HZ_CUST_PROFILE_CLASSES — customer profile classification data.
- HZ_RELATIONSHIPS, HZ_RELATIONSHIPS_S, and HZ_RELATIONSHIP_TYPES — party relationship records, their intersection rows, and type definitions.
- HZ_CONTACT_POINTS — contact mechanism records.
- HZ_LOCATIONS — address location records.
- DUAL — used for single-row procedural queries.
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.
-
PACKAGE: APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT
12.1.1
-
PACKAGE: APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT
12.2.2
-
PACKAGE: APPS.HZ_RELATIONSHIP_V2PUB
12.1.1
-
PACKAGE: APPS.HZ_RELATIONSHIP_V2PUB
12.2.2
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on HZ_RELATIONSHIP_V2PUB
12.2.2
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on HZ_RELATIONSHIP_V2PUB
12.1.1
-
PACKAGE BODY: APPS.HZ_RELATIONSHIP_V2PUB
12.1.1
-
PACKAGE BODY: APPS.HZ_RELATIONSHIP_V2PUB
12.2.2
-
APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT dependencies on HZ_RELATIONSHIP_V2PUB
12.1.1
-
APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT dependencies on HZ_RELATIONSHIP_V2PUB
12.2.2
-
APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT dependencies on HZ_RELATIONSHIP_V2PUB
12.1.1
-
APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT dependencies on HZ_RELATIONSHIP_V2PUB
12.2.2
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on FND_API
12.1.1
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on FND_API
12.2.2
-
PACKAGE BODY: APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT
12.2.2
-
PACKAGE BODY: APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT
12.1.1
-
APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT dependencies on FND_API
12.2.2
-
APPS.ARP_CMERGE_ARCUS dependencies on HZ_CUST_ACCOUNT_MERGE_V2PVT
12.1.1
-
APPS.ARP_CMERGE_ARCUS dependencies on HZ_CUST_ACCOUNT_MERGE_V2PVT
12.2.2
-
APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT dependencies on FND_API
12.1.1
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on HZ_UTILITY_V2PUB
12.1.1
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on HZ_UTILITY_V2PUB
12.2.2
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on FND_LOG
12.2.2
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on FND_LOG
12.1.1
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on FND_API
12.1.1
-
APPS.HZ_RELATIONSHIP_V2PUB dependencies on FND_API
12.2.2
-
APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT dependencies on FND_API
12.1.1
-
APPS.HZ_CUST_ACCOUNT_MERGE_V2PVT dependencies on FND_API
12.2.2
-
PACKAGE BODY: APPS.ARP_CMERGE_ARCUS
12.2.2
-
PACKAGE BODY: APPS.ARP_CMERGE_ARCUS
12.1.1