Search Results check_unique_vendor_name




Overview

APPS.AP_VENDORS_PKG is a server-side PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the maintenance and validation of supplier records within Oracle Payables. In EBS 12.1.1 and 12.2.2, supplier data is stored in the AP_SUPPLIERS and related tables (including the AP_SUPPLIER_SITES_ALL entity), and this package provides the low-level procedural logic that forms and concurrent programs use when inserting, updating, and validating that data. The ETRM metadata classifies the package under an "OTHER" API classification, distinguishing it from the published, externally supported PL/SQL APIs such as AP_VENDOR_PUB_PKG. It is a VALID object owned by APPS, with documented dependencies on the APPS.AP_VENDOR_PUB_PKG and SYS.STANDARD packages, and it is itself referenced by AP_VENDOR_PUB_PKG.

Key Procedures and Functions

The ETRM documentation identifies twelve procedures and functions, of which the following are named:

Parameter lists are not reproduced here, as the metadata does not document them.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

  • AP_SUPPLIERS — the primary supplier master, written by INSERT_ROW and UPDATE_ROW.
  • AP_SUPPLIER_SITES_ALL — supplier site records associated with a supplier.
  • AP_SELECTED_INVOICES — queried by CHECK_SELECTED_INVOICES.
  • AP_PRODUCT_SETUP — read for Payables setup and option information.
  • PO_HISTORY_VENDORS and PO_VENDORS_S — Purchasing supplier and vendor history tables referenced during validation and denormalization.

Usage Notes

AP_VENDORS_PKG is invoked internally by the Oracle Payables supplier entry forms and by AP_VENDOR_PUB_PKG, the published API that wraps much of this functionality. It is not intended as a public interface for custom development, and Oracle generally recommends that customizations call the supported AP_VENDOR_PUB_PKG APIs rather than AP_VENDORS_PKG directly. Because it is referenced by only one other package and is classified as OTHER, changes to its logic are subject to Oracle's internal upgrade path in both 12.1.1 and 12.2.2. Developers may inspect it for diagnostic purposes, but direct invocation in custom code risks breaking across patches and is not covered by Oracle support.