Search Results update_party_site_use

Overview

APPS.HZ_PARTY_SITE_V2PUB is a public PL/SQL package within the Oracle Trading Community Architecture (TCA) product family. It provides the canonical programmatic interface for creating and maintaining party site records and party site use records in Oracle E-Business Suite releases 12.1.1 and 12.2.2. A party site represents a physical address (location) associated with a party, such as a customer, supplier, or contact, while a party site use associates that site with a specific business purpose, such as a billing or shipping role. The package is classified as PUBLIC in the ETRM, meaning it is supported for direct invocation by customer and partner extensions.

The package header defines two record types that mirror the underlying TCA schema: party_site_rec_type, which carries identifiers, address attributes, descriptive flexfield columns (attribute1 through attribute20), language, addressee, and DUNS data, and party_site_use_rec_type, which carries site use identifiers, comments, site use type, primary flag, and status. These record structures form the primary input and output vehicle for the package APIs.

Key Procedures and Functions

The package exposes six documented procedures and functions:

• CREATE_PARTY_SITE — Creates a new party site record, establishing the association between a party and a location with associated descriptive attributes.
• UPDATE_PARTY_SITE — Modifies an existing party site record, including address attributes, status, and flexfield values.
• CREATE_PARTY_SITE_USE — Creates a party site use record, assigning a specific business purpose to an existing party site.
• UPDATE_PARTY_SITE_USE — Updates an existing party site use record. This is the procedure most directly associated with the user search term "update_party_site_use," and is the supported entry point for programmatic changes to site use attributes such as status, primary flag, and comments.
• GET_PARTY_SITE_REC — Retrieves a party site record into the party_site_rec_type structure, supporting read access for validation and integration scenarios.
• GET_PARTY_SITE_USE_REC — Retrieves a party site use record into the party_site_use_rec_type structure.

Tables Accessed

The package operates against the core TCA and related tables through APPS synonyms:

• HZ_PARTY_SITES — primary storage for party site records created and updated by the package.
• HZ_PARTY_SITE_USES — primary storage for party site use records.
• HZ_LOCATIONS — the address or location referenced by a party site.
• HZ_PARTIES — the party to which sites are attached.
• HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_CUST_SITE_USES — customer-facing site and site use tables, reflecting the package's role in propagating party site changes into customer account address structures.
• FND_NEW_MESSAGES — used for message handling and API return status reporting.

Usage Notes

HZ_PARTY_SITE_V2PUB is designed for programmatic maintenance of party site data outside of the standard TCA forms. Typical invocation scenarios include custom concurrent programs that bulk-load or synchronize address data, integration interfaces from external master data systems, and Oracle Forms or OAF pages that call the API rather than performing direct DML. The ETRM indicates the package is referenced by 68 other packages, underscoring its role as a foundational dependency within the TCA and Receivables (AR) stack. Developers should invoke UPDATE_PARTY_SITE_USE rather than writing directly to HZ_PARTY_SITE_USES, because the API enforces TCA business rules such as primary flag consistency and status validation, and preserves the integrity of dependent customer account site records. The header's $Header stamp (version 120.12) confirms the package lineage is common to both 12.1.1 and 12.2.2 codelines.