Search Results update_supplier_address

Overview

POS_SUPPLIER_ADDRESS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides the public API layer for creating, updating, and managing supplier address information used by Oracle Purchasing and Oracle Payables. In the context of EBS 12.1.1 and 12.2.2, the package acts as a controlled gateway between supplier-facing application code and the underlying Trading Community Architecture (TCA) model, where supplier addresses are physically stored as party sites and party site uses on HZ_PARTY_SITES and HZ_PARTY_SITE_USES.

The package is classified in the ETRM repository as OTHER rather than as a standard Open Interface API, meaning it is intended primarily for internal application use — supplier registration, supplier management forms, and buyer-maintained address data — rather than as a bulk-loading interface. It respects the multi-org and multi-organization access controls enforced by AP_SYSTEM_PARAMETERS_ALL and the supplier/party relationships recorded in AP_SUPPLIERS and HZ_RELATIONSHIPS.

Key Procedures and Functions

The ETRM metadata documents seven procedures in the package:

• CREATE_SUPPLIER_ADDRESS — Creates a new supplier address. It accepts supplier and party identifiers together with the full descriptive address (lines 1–4, city, state, province, postal code, county, country) and purpose flags for RFQ, purchasing, and payment usage, including a primary pay flag. Contact details such as phone area code, number, extension, fax, and e-mail are also captured. The procedure returns a standard API return status, message count, message data, and the newly created party site identifier.
• UPDATE_SUPPLIER_ADDRESS — Updates an existing supplier address. It takes the same descriptive and purpose attributes as the create procedure, plus the party site identifier, and returns the standard return status, message count, and message data. This is the primary maintenance entry point for changes made through the Supplier Management forms.
• UNASSIGN_ADDRESS_TO_CONTACT — Removes the association between a supplier address (identified by organization party site) and a contact (identified by contact party identifier). It is used when a contact should no longer be linked to a specific location.
• UPDATE_ADDRESS_TO_CONTACT — Modifies an existing address-to-contact assignment, allowing the linkage details to be changed without removing and recreating the relationship.
• ASSIGN_ADDRESS_TO_CONTACT — Creates a new association between a supplier address and a contact party, populating the contact-site relationship used by purchasing documents and notifications.
• UPDATE_ADDRESS_ASSIGNMENT_DFF — Maintains descriptive flexfield (DFF) values attached to an address assignment. This supports customer-specific attribute extensions configured on the contact-address relationship.
• BUYER_UPDATE_ADDRESS_DETAILS — Allows purchasing buyers to update address details directly. This supports buyer-driven maintenance of supplier site information distinct from the standard supplier self-service path.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms:

• AP_SUPPLIERS — Supplier header information used to validate and relate the address to the correct supplier record.
• AP_SUPPLIER_CONTACTS — Supplier contact records that are associated with or dissociated from addresses.
• AP_SYSTEM_PARAMETERS_ALL — Organization-level Payables configuration that governs default behavior, including the default country and operating unit context.
• HZ_LOCATIONS — The TCA location record holding the physical address lines, city, state, postal code, and country.
• HZ_ORG_CONTACTS — Contact records linking contacts to organizations for assignment operations.
• HZ_PARTY_SITES — The party site entity that represents a supplier address at a specific location.
• HZ_PARTY_SITE_USES — The usage flags (RFQ, purchasing, payment, primary pay) that determine how an address may be used on transactions.
• HZ_RELATIONSHIPS — Relationship records that tie supplier parties to their addresses and contacts.
• POS_SUPPLIER_REGISTRATIONS — Supplier registration data used during the supplier onboarding flows that invoke this package.

Usage Notes

POS_SUPPLIER_ADDRESS_PKG is typically invoked from the Oracle Supplier Management and Purchasing forms, from the supplier registration and self-service flows, and from concurrent programs that maintain supplier address data. The ETRM metadata records that the package is referenced by three other packages, confirming its role as a shared API dependency within the supplier data model. Customizations and integrations that need to create or maintain supplier addresses programmatically should call these procedures rather than performing direct DML on HZ_PARTY_SITES and HZ_PARTY_SITE_USES, because the procedures enforce TCA validation rules, synchronize the location and party site records, maintain the relationship records in HZ_RELATIONSHIPS, and return consistent status and message outputs for error handling. Callers should always inspect the return status and message output parameters, since TCA validation failures are surfaced through those mechanisms rather than by raising exceptions.