Search Results get_cust_site_use_rec




Overview
Explore in AI Chat

Overview

APPS.HZ_CUST_ACCOUNT_SITE_V2PUB is a public PL/SQL API package in the Oracle Trading Community Architecture (TCA) and Oracle Receivables schema. It exposes the supported programmatic interface for creating, updating, and retrieving customer account sites and customer site uses within Oracle E-Business Suite. In the context of the ETRM documentation for 12.1.1 and 12.2.2, the package is classified as a PUB (public) API owned by the APPS schema, declared with AUTHID CURRENT_USER, and is registered under the business entity HZ_ADDRESS with the display name "Customer Account Site" and product code HZ.

The business function of the package is to provide a controlled, validated layer for maintaining the site-level records that link a customer account (HZ_CUST_ACCOUNTS) to a physical address or party site (HZ_PARTY_SITES) and to the functional uses defined for that site, such as bill-to, ship-to, and other Receivables site purposes. Customer account sites and site uses are fundamental to order management, invoicing, shipping, and tax determination. Any creation or amendment of such data through custom code, integration, or interface should be routed through this API rather than direct DML, so that TCA denormalization, context values, and cross-entity relationships remain consistent.

Key Procedures and Functions

The package exposes six documented public procedures and functions, organized as paired create, update, and query operations for account sites and site uses:

  • CREATE_CUST_ACCT_SITE — Creates a new customer account site, establishing the association between a customer account and a party site. It accepts site attribute and descriptive flexfield values through the cust_acct_site_rec_type record structure.
  • UPDATE_CUST_ACCT_SITE — Modifies an existing customer account site record, including attribute and global attribute flexfield columns defined in the record type.
  • GET_CUST_ACCT_SITE_REC — Retrieves an existing customer account site into the cust_acct_site_rec_type record, allowing callers to read current values before an update or to validate an existing relationship.
  • CREATE_CUST_SITE_USE — Creates a site use for a customer account site, defining the functional purpose (for example, bill-to or ship-to) that the site serves for the account.
  • UPDATE_CUST_SITE_USE — Modifies an existing customer site use record.
  • GET_CUST_SITE_USE_REC — Retrieves the current values of an existing customer site use.

Parameter lists are not reproduced here; callers should reference the package specification header and the Customer Account Site APIs chapter of the TCA Technical Implementation Guide (120hztig.pdf) for exact signatures and the record type definition.

Tables Accessed

The package reads and writes the principal TCA and Receivables tables that hold site and site-use data. HZ_CUST_ACCT_SITES and HZ_CUST_ACCT_SITES_ALL store the account-to-site relationship itself, including org-specific rows. HZ_CUST_SITE_USES and HZ_CUST_SITE_USES_ALL store the site uses and their organization assignments. HZ_CUST_ACCOUNTS holds the parent customer account, while HZ_PARTY_SITES, HZ_PARTY_SITE_USES, and HZ_LOCATIONS hold the underlying party address and location data referenced by the account site. HZ_CUSTOMER_PROFILES, HZ_CUST_PROFILE_AMTS, and FND_NEW_MESSAGES support profile validation and error message handling respectively.

Usage Notes

This package is typically invoked from Oracle Forms and from custom PL/SQL or concurrent programs that need to load or maintain customer account sites and site uses, for example during customer data conversion or integration with external order and billing systems. It is one of the more widely reused TCA public APIs, referenced by 26 other packages, so changes to calling code should account for its dependencies. Because the package uses AUTHID CURRENT_USER, invoking user or application must have appropriate privileges on the APPS-owned objects. The URL pattern referenced in the originating search (a /manageaccount endpoint) corresponds to a self-service or integration entry point; in an EBS context, such endpoints ultimately delegate site maintenance to this API rather than writing to HZ tables directly. Direct DML against the underlying site tables bypasses the validation and denormalization logic performed by this package and should be avoided.