Results for “party_of_vendor”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_SUPPLIER_PARTY is a PL/SQL package body owned by the APPS schema that provides the supplier and party data-management layer for Oracle Shipping Execution (WSH). Its central responsibility is to synchronize supplier information originating in Oracle Payables and Purchasing into the Trading Community Architecture (TCA) registry, so that shipping, receiving, and warehouse operations can reference accurate vendor addresses, contact points, and party sites. The package performs duplicate checks against existing TCA locations, creates and updates address records, and validates that a supplier exists as a party before downstream shipping transactions are processed. In Oracle EBS 12.1.1 and 12.2.2, this logic is essential because shipping documents — bills of lading, packing slips, and delivery details — depend on validated party-site data rather than ad hoc address text.

Key Procedures and Functions

ETRM documents nine public units in the package:

• PROCESS_ADDRESS — Orchestrates address handling, routing the request to the appropriate create or update path.
• CREATE_ADDRESS — Inserts a new supplier address into the TCA model.
• UPDATE_ADDRESS — Modifies an existing location or party-site record when supplier data changes.
• VALIDATE_SUPPLIER — Confirms that a supplier record is valid and eligible for shipping use.
• VENDOR_PARTY_EXISTS — Boolean-style existence check that determines whether a vendor already has a corresponding party.
• CREATE_VENDOR_PARTY — Creates the HZ_PARTIES record for a vendor that does not yet exist in TCA.
• CREATE_HZ_PARTY_SITE — Creates the party-site record linking a party to a location.
• PROCESS_HZ_CONTACT — Handles contact information associated with the supplier party.
• CREATE_HZ_PARTY_SITE_USES — Creates party-site usage records that designate the business purpose of a site.

The private function Check_Hz_Location, visible in the source excerpt, searches HZ_LOCATIONS for a location code and party combination and returns the location and party-site identifiers. The package also maintains a global PL/SQL table (g_error_tbl) for translated messages from the FND stack and a line-number variable tied to the Supplier Address Book.

Tables Accessed

All access is through APPS synonyms. HZ_PARTIES stores the party (vendor) records created by CREATE_VENDOR_PARTY. HZ_LOCATIONS and HZ_PARTY_SITES hold address and site data written by CREATE_ADDRESS, UPDATE_ADDRESS, and CREATE_HZ_PARTY_SITE. HZ_PARTY_SITE_USES records site purposes, HZ_CONTACT_POINTS and HZ_ORG_CONTACTS support contact processing, and HZ_RELATIONSHIPS and HZ_CODE_ASSIGNMENTS maintain party relationships and coded classifications. PLITBLM is used for temporary PL/SQL table storage.

Usage Notes

WSH_SUPPLIER_PARTY is referenced by four other packages, indicating it is invoked indirectly rather than directly from a form. Typical callers are shipping execution flows that resolve supplier addresses during delivery and receipt processing, and concurrent programs that bulk-load or reconcile vendor party data against TCA. Custom code extending supplier address handling should call PROCESS_ADDRESS or VALIDATE_SUPPLIER rather than manipulating the HZ tables directly, because the packaged logic performs the duplicate-location check and applies the C_CREATED_BY_MODULE value of 'WSH' for audit purposes. Because the code was last updated in the 12.1.1 code line (version 120.7), it behaves identically on both 12.1.1 and 12.2.2, and the TCA APIs it wraps remain compatible across both releases.