Search Results create_party_site

Overview

PV_PARTNER_ACCNT_MGMT_PVT_W is an Oracle EBS PL/SQL package owned by the APPS schema and classified generically as an OTHER API within the E-TRM repository for releases 12.1.1 and 12.2.2. Its name and header ($Header: pvxwpams.pls 120.1 2005/09/08) identify it as a private wrapper belonging to the Oracle Partner Management (PV) product family, which governs channel partner and partner-account relationships. The package encapsulates the logic required to create party-site-level records on behalf of the partner account management subsystem, isolating the calling layer from the underlying Trading Community Architecture (TCA) APIs. Because the object is a "_PVT_W" wrapper (private, wrapper), it is not a public API surface; it is designed to be called by other PV modules, concurrent programs, or UI layers that need a controlled entry point for creating a party site when registering or managing a partner account. The presence of an explicit rather than boolean p_api_version, generic positional parameters (p3_a0 through p3_a19), and standard error-out arguments (x_return_status, x_msg_count, x_msg_data) confirms it follows the standard EBS concurrent/API wrapper convention of shielding internal argument changes from external callers.

Key Procedures and Functions

• CREATE_PARTY_SITE — the single documented procedure in the package. It implements the creation of a party site record associated with a partner account. It accepts the standard API envelope parameters (p_api_version, p_init_msg_list, p_commit), a set of positional data parameters that carry the site's identifying attributes, and out parameters for the resulting status and newly assigned x_party_site_id. In practice it delegates to the underlying TCA party-site creation interfaces, returning the generated site identifier, a return status, and stacked error messages through the standard x_msg_count/x_msg_data mechanism.

Tables Accessed

The available E-TRM metadata does not enumerate the base tables the package touches through APPS synonyms. Based on its function of creating a party site, the package operates on the TCA foundation tables — principally HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS — and their associated association tables (for example HZ_PARTY_SITE_USES and HZ_LOC_ASSIGNMENTS), which record the relationship between a party, its sites, and physical locations. Because it is a private wrapper of the Partner Management module, it may also read or write Partner Management configuration tables that map a partner account to a specific site context. Readers should query the actual source (pvxwpams.pls) or DBA_DEPENDENCIES for the authoritative dependency list in any given installation.

Usage Notes

This package is a private object and should not be invoked directly by custom integrations. It is typically called from within the Oracle Partner Management UI flow, from other PV packages that manage partner account registration, or from concurrent programs that provision partner sites in bulk. When called in custom code, the standard pattern applies: initialize the message list, supply a valid API version, set the commit flag to request the transaction boundary, and inspect x_return_status and the message stack before relying on x_party_site_id. It is sensitive to TCA profile options and to the correct setup of locations and party sites, and should be tested in a cloned instance before production use. It is referenced by no other packages in the documented metadata, which reinforces its role as a terminal wrapper rather than a shared utility.