Search Results update_party_site

Overview

APPS.CSL_HZ_PARTY_SITES_ACC_PKG is an Oracle E-Business Suite PL/SQL package that maintains party site information in the Trading Community Architecture (TCA) model, specifically in support of the Oracle Advanced Product Catalog (formerly the Collaborative Suite / iSupport family of modules, indicated by the CSL prefix). Its purpose is to encapsulate the create, modify, remove, and merge operations on party site records so that catalog or resource-related processes can synchronize party site data without directly manipulating the underlying HZ_PARTY_SITES table.

The package is declared with AUTHID CURRENT_USER, meaning it executes under the privileges of the calling schema rather than as definer rights. This places responsibility on the calling code to ensure the invoking user has appropriate access to the HZ synonyms and to the catalog tables that the package touches. In ETRM terms the package is classified as an "OTHER" API rather than a public or private Oracle API, indicating it is an internal, product-owned utility rather than a documented integration interface. It is referenced by four other packages, which confirms it functions as a shared subroutine consumed elsewhere in the same product family.

Key Procedures and Functions

The package exposes four documented procedures, all of which operate on a single party site identified by its primary key or on a pairing of old and new identifiers.

• INSERT_PARTY_SITE — Registers a new party site relationship for a given party site and resource, creating the catalog-side association that corresponds to a site that already exists (or is being created) in TCA.
• UPDATE_PARTY_SITE — Refreshes the catalog or resource data associated with an existing party site, keeping the product-specific record consistent with the TCA record.
• DELETE_PARTY_SITE — Removes the party site association for the supplied party site and resource, reversing the effect of the insert procedure.
• CHANGE_PARTY_SITE — Handles the case where one party site is replaced by another, accepting both the old and new party site identifiers plus the resource, so that dependent catalog references can be re-pointed rather than deleted and recreated.

No functions (as opposed to procedures) are documented, and the parameter lists are not reproduced here; the identifiers shown are name-only descriptions as recorded in the ETRM metadata.

Tables Accessed

Through APPS synonyms the package is documented as referencing three database objects:

• HZ_PARTY_SITES — the central TCA table holding party site records. The insert, update, delete, and change procedures read and write this table to keep site data aligned with the catalog.
• DBMS_SQL — the Oracle-supplied dynamic SQL package, used for runtime-constructed statements, which allows the procedures to build SQL against varying conditions without hard-coded cursors.
• PLITBLM — an Oracle Application Object Library index-by table type used for passing and manipulating collections of identifiers (typically primary key lists) within PL/SQL.

The combination of DBMS_SQL and PLITBLM suggests the package performs set-oriented, dynamically constructed DML against HZ_PARTY_SITES rather than simple static statements.

Usage Notes

CSL_HZ_PARTY_SITES_ACC_PKG is not a supported public API and should not be called directly from third-party or custom code without review. It is normally invoked indirectly by the four packages that reference it, which in turn are driven by Oracle Advanced Product Catalog forms, catalog item maintenance flows, or concurrent programs that synchronize catalog and TCA data.

Because the package runs with AUTHID CURRENT_USER, any custom caller must be granted the necessary object privileges on HZ_PARTY_SITES and its synonyms. When integrating, prefer the officially published TCA APIs (for example the HZ_PARTY_SITE_* public packages) for creating or merging party sites, and treat this package as an internal implementation detail whose signature may change between 12.1.1 and 12.2.2. Its header revision ($Header: cslpsacs.pls 115.3) marks it as a long-standing object, and the absence of a public API classification confirms it is intended for product-internal use only.