Search Results create_hz_party_site_uses

Overview

APPS.WSH_SUPPLIER_PARTY is a PL/SQL package that belongs to the Oracle Shipping Execution (WSH) module of Oracle E-Business Suite. Its principal business function is to manage supplier address book information for the Oracle Shipping and Receiving application by creating and maintaining the underlying Trading Community Architecture (TCA) entities that represent a supplier's addresses, party sites, and contacts. In release 12.1.1 and 12.2.2, supplier shipping information is no longer stored in legacy WSH structures alone; it is modeled through the TCA registry using the HZ schema tables. This package provides the programmatic bridge between the shipping-facing supplier address book user interface and those HZ tables.

The header declaration specifies AUTHID CURRENT_USER, meaning the package executes with the privileges of the invoking user rather than the definer, and the version string indicates a source lineage dating to the 11i/R12.1 development stream (120.2). The API is classified as OTHER in the ETRM documentation and exposes nine documented subprograms.

Key Procedures and Functions

• PROCESS_ADDRESS — The primary public entry point. It validates the incoming action code, determines whether address information already exists for the given shipping code and supplier, and dispatches to the correct internal routine. If a record exists it enforces that the action code is not an insert and calls the update path; if no record exists it enforces that the action code is not an update and calls the create path. It accepts parameters passed from the UI, the supplier address book record, and returns success and error message collections along with a standard return status.
• CREATE_ADDRESS — Creates address information. It builds the location and party site records, validates the location, creates party site uses, and creates contact information.
• UPDATE_ADDRESS — Modifies an existing supplier address book record.
• VALIDATE_SUPPLIER — Validates that the supplier referenced by the request is known and eligible for address maintenance.
• VENDOR_PARTY_EXISTS — Determines whether a TCA party record already exists for the vendor, preventing duplicate party creation.
• CREATE_VENDOR_PARTY — Creates the HZ party record representing the supplier when one does not yet exist.
• CREATE_HZ_PARTY_SITE — Creates the HZ party site associated with the supplier party and location.
• PROCESS_HZ_CONTACT — Creates or maintains the contact information attached to the supplier party site.
• CREATE_HZ_PARTY_SITE_USES — Creates the party site use rows that define the business purpose (for example, shipping) of a party site.

Tables Accessed

The package operates on the following tables, referenced through APPS synonyms:

• HZ_PARTIES — Stores the party record for the supplier; created by CREATE_VENDOR_PARTY and checked by VENDOR_PARTY_EXISTS.
• HZ_LOCATIONS — Stores the validated address lines for the supplier address book entry.
• HZ_PARTY_SITES — Associates a party with a location; created by CREATE_HZ_PARTY_SITE.
• HZ_PARTY_SITE_USES — Defines the purpose of each party site; populated by CREATE_HZ_PARTY_SITE_USES.
• HZ_ORG_CONTACTS and HZ_CONTACT_POINTS — Hold contact records and their communication points, maintained through PROCESS_HZ_CONTACT.
• HZ_RELATIONSHIPS — Stores relationships between parties, such as contact-to-organization links.
• HZ_CODE_ASSIGNMENTS — Holds classification and code assignment data for TCA entities.
• PLITBLM — A PL/SQL index-by table type used internally for collection handling.

Usage Notes

WSH_SUPPLIER_PARTY is typically invoked indirectly. Supplier address book maintenance originates from the Shipping Transactions or supplier address book forms in Oracle Shipping Execution, which call PROCESS_ADDRESS to persist user changes. It may also be called from concurrent programs and from custom integration code that must create or refresh supplier ship-to addresses in bulk. Because the package delegates all real work to TCA (HZ) tables, callers must ensure that TCA setup, location validation, and party numbering are correctly configured before invocation. The package is referenced by four other packages, confirming its role as a shared utility rather than a standalone API. Error and success collections returned by PROCESS_ADDRESS should always be inspected, since partial failures can leave party, site, or contact records in an inconsistent state.