Search Results validate_vendor_site




Overview

AP_VENDOR_PUB_PKG is the public PL/SQL API package that governs the creation, maintenance, and validation of supplier master data in Oracle EBS Release 12.1.1 and 12.2.2. It encapsulates the business logic required to register suppliers, supplier sites, and supplier contacts, and it exposes that logic through a stable public interface. The package body carries the header identifier appvndrb.pls 120.78.12010000.28, confirming it is the runtime implementation shipped by Oracle Application Object Library and owned by the APPS schema.

The package is classified as a standard EBS public API (API classification OTHER). Every procedure follows the Oracle API programming conventions, including p_init_msg_list, p_commit, x_return_status, x_msg_count, and x_msg_data style parameters, predictable error signalling, and structured logging through FND_MSG_PUB and FND_LOG. Constants such as G_MSG_SUCCESS, G_LEVEL_PROCEDURE, and G_LINES_PER_FETCH control message severity, debug tracing, and bulk fetch behaviour. It is referenced by 23 other packages, which makes it one of the more widely depended-upon interfaces in the Payables supplier domain.

Key Procedures and Functions

Tables Accessed

The package reads and writes the core supplier model: AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and AP_SUPPLIER_CONTACTS, with interface counterparts AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT, and AP_SUP_SITE_CONTACT_INT for the import routines. It references HZ_PARTIES, HZ_PARTY_SITES, and HZ_CONTACT_POINTS for party and address information, ZX_PARTY_TAX_PROFILE for tax profiles, HR_LOCATIONS_ALL_TL and AP_TERMS_TL for location and payment term descriptions, and AP_AWT_GROUPS, AP_DISTRIBUTION_SETS_ALL, and AP_TOLERANCE_TEMPLATES for withholding, distribution, and tolerance defaults.

Usage Notes

AP_VENDOR_PUB_PKG is invoked from the Suppliers and Supplier Sites forms, from concurrent programs that process the supplier interface tables, and from custom integrations that must create or update suppliers programmatically. The presence of VALIDATE_VENDOR, VALIDATE_VENDOR_SITE, and VALIDATE_VENDOR_CONTACT allows callers to perform a dry-run check before committing. Custom code should call these public procedures rather than writing directly to the base tables, ensuring that validation, event publication, and logging remain consistent.