Search Results check_duplicate_ece_code




Overview

AP_VENDOR_SITES_PKG is an Oracle APPS schema PL/SQL package within Oracle E-Business Suite 12.1.1 and 12.2.2 that encapsulates the core business logic for maintaining supplier site records in Oracle Payables. Supplier sites represent the specific addresses, payment terms, currencies, tax reporting attributes, and purchasing associations tied to a supplier, and they form the foundation for invoice entry, payment processing, and purchasing transactions. The package provides the updateable PL/SQL interface used to validate, insert, and modify rows in the supplier sites tables while enforcing the business rules that Oracle Payables requires.

The package is classified in ETRM as an "OTHER" API and is a supporting package rather than a public API in the same sense as the Oracle-supplied public APIs in the AP_VENDOR_PUB_PKG family. The ETRM dependency listing documents that AP_VENDOR_SITES_PKG references AP_VENDOR_PUB_PKG and MO_GLOBAL, and that it is referenced by AP_VENDOR_DISP_V, AP_VENDOR_PUB_PKG, AP_VENDOR_SITES_V, and WIP_OSP_SHP_I_WF. Users searching for "ap_vendor_pub_pkg" are commonly directed to AP_VENDOR_SITES_PKG because the public supplier API delegates site maintenance to this package.

Key Procedures and Functions

ETRM documents 13 procedures and functions. The row maintenance procedures include INSERT_ROW, UPDATE_ROW, and LOCK_ROW, which respectively create a new supplier site record, modify an existing supplier site record, and acquire a row-level lock on a supplier site for concurrency control. FORMAT_ADDRESS assembles the address components of a supplier site into the formatted address representation used by Payables.

The validation procedures enforce specific supplier site business rules. CHECK_VENDOR_OFFSETS validates vendor offset configuration. CHECK_DUPLICATE_VENDOR_SITE detects duplicate supplier site entries. CHECK_MULTIPLE_TAX_SITES validates tax site configuration when a supplier holds multiple tax reporting sites. CHECK_SITE_CURRENCIES validates the currency assignments associated with the site. CHECK_STATE_CODES validates state code values against defined territories. CHECK_DUPLICATE_ECE_CODE validates duplicate ECE (electronic commerce) codes. GET_TAX_SITE retrieves the designated tax reporting site for a supplier. Together these routines centralize the validation logic that would otherwise be duplicated across forms, interfaces, and interface tables.

Tables Accessed

ETRM documents access through APPS synonyms to AP_SUPPLIERS, which stores supplier header information; AP_SUPPLIER_SITES and AP_SUPPLIER_SITES_ALL, which store the supplier site and site-level organization assignment records; PO_VENDOR_SITES_S, the purchasing view of supplier sites; and FND_TERRITORIES, which supplies territory validation for address and state code checks. PO_LOCATION_ASSOCIATIONS supports the relationship between purchasing locations and supplier sites, and AP_INCOME_TAX_REGIONS supports income tax region validation for tax reporting sites. These tables are read and written to enforce the validation rules and to persist supplier site changes.

Usage Notes

AP_VENDOR_SITES_PKG is typically invoked indirectly. The Supplier entry forms in Oracle Payables and Oracle Purchasing route site-level insert, update, and validation requests through this package, and the public supplier API AP_VENDOR_PUB_PKG delegates to it as documented in the dependency listing. Interface and conversion programs that load supplier sites through the Payables interface tables also depend on its validation routines. Custom code should avoid calling INSERT_ROW or UPDATE_ROW directly, because the package assumes the calling context, concurrency handling, and dependent columns have been prepared by the standard forms or the public API layer. Because the package references MO_GLOBAL, it participates in multi-org security and organization context handling in 12.2.2 and 12.1.1. Developers extending supplier site functionality should use the public API where available and treat AP_VENDOR_SITES_PKG as an internal implementation component whose signature and validation behavior are subject to change between releases.