Search Results create_vendor_contact

Overview

APPS.AP_VENDOR_PUB_PKG, identified in the ETRM repository under the display name "Suppliers Package," is the primary public PL/SQL API for creating, updating, and validating supplier master data in Oracle Payables. The package header declares AUTHID CURRENT_USER and carries the Enterprise Repository scope tag public with a lifecycle status of active, classifying it under the business entity AP_SUPPLIER. Its stated purpose is to allow users to create supplier, supplier site, and supplier contact records directly into Payables, and to support the concurrent import of that same data from interface tables. Because it is the sole documented supported entry point for supplier contact creation—including the frequently referenced CREATE_VENDOR_CONTACT procedure—it is the canonical API for any external or custom integration that must populate supplier contacts without direct table writes. The package maintains global state for import processing, including source and multi-org indicators, default organization identifiers, and Federal Financials installation flags, along with cached FND_GLOBAL user and login identifiers.

Key Procedures and Functions

The package exposes seventeen documented program units grouped by entity and operation.

• Supplier operations: CREATE_VENDOR, UPDATE_VENDOR, and VALIDATE_VENDOR insert, modify, and pre-validate supplier header records respectively. RAISE_SUPPLIER_EVENT publishes the business event associated with supplier changes, and CHECK_GDF validates descriptive flexfield content.
• Supplier site operations: CREATE_VENDOR_SITE, UPDATE_VENDOR_SITE, and VALIDATE_VENDOR_SITE perform the equivalent lifecycle for purchasing and pay sites. IS_VENDOR_SITE_MERGED determines whether a site has been merged, and UPDATE_ADDRESS_ASSIGNMENTS_DFF maintains address-related flexfield assignments.
• Supplier contact operations: CREATE_VENDOR_CONTACT, UPDATE_VENDOR_CONTACT, and VALIDATE_VENDOR_CONTACT create, maintain, and validate contact records for a supplier or supplier site. This trio corresponds to the search term create_vendor_contact and represents the documented mechanism for programmatic contact creation.
• Interface import operations: IMPORT_VENDORS, IMPORT_VENDOR_SITES, and IMPORT_VENDOR_CONTACTS process rows staged in the corresponding AP interface tables.
• Taxpayer validation: IS_TAXPAYER_ID_VALID verifies taxpayer identifier validity against tax profile data.

Tables Accessed

The package reads and writes the core Payables supplier tables through APPS synonyms. Supplier headers reside in AP_SUPPLIERS, sites in AP_SUPPLIER_SITES_ALL, and contacts in AP_SUPPLIER_CONTACTS. Bulk import processing uses the interface tables AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT, and AP_SUP_SITE_CONTACT_INT. Supporting configuration data is drawn from AP_TERMS_TL, AP_AWT_GROUPS, AP_DISTRIBUTION_SETS_ALL, and AP_TOLERANCE_TEMPLATES. Location and party information is sourced from HR_LOCATIONS_ALL_TL, HZ_PARTIES, HZ_PARTY_SITES, and HZ_CONTACT_POINTS, reflecting the TCA-based architecture of Release 12. Tax data is validated against ZX_PARTY_TAX_PROFILE.

Usage Notes

AP_VENDOR_PUB_PKG is invoked from the supplier entry forms in Oracle Payables, from the Supplier Interface concurrent programs that consume the AP interface tables, and from custom PL/SQL integrations that require validated supplier, site, or contact creation. It is referenced by twenty-three other packages in the ETRM repository, confirming its role as a foundational dependency. Callers should invoke the VALIDATE procedures before their CREATE or UPDATE counterparts to surface errors predictably, and should anticipate that the import programs depend on the package's global source and multi-org state. Because the API is documented as public and active in both Release 12.1.1 and 12.2.2, it is the supported alternative to direct DML against AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and AP_SUPPLIER_CONTACTS.