Results for “po_vendor_contacts_s”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_VENDOR_PARTY_MERGE_PKG is a PL/SQL package body in the APPS schema that supports the Supplier (Vendor) merge process in Oracle E-Business Suite. Its central business function is to programmatically merge duplicate supplier records registered in the AP_DUPLICATE_VENDORS_ALL table, consolidating the associated party, supplier site, supplier contact, and party-site data into a single surviving vendor. In the Oracle EBS 12.1.1 and 12.2.2 architectures, supplier records are modelled as TCA (Trading Community Architecture) parties, so the merge operation must reconcile both the legacy Payables supplier tables and the underlying HZ party model. This package acts as the Payables-side orchestrator that calls sub-processes across multiple applications — Procurement, Payables, Financials, Treasury, and the horizontal TCA APIs — and it is the layer that drives contact-level and contact-point-level re-pointing during the merge, including the affected PO_VENDOR_CONTACTS_S supplier contacts that users frequently query in this context.

Key Procedures and Functions

• OTHER_PRODUCTS_VENDORMERGE — the single documented entry point. It performs the cross-product portion of the vendor merge, i.e. the re-assignment of supplier contacts and related records owned by applications other than the core Payables merge. It coordinates with the group handlers PO_VENDORMERGE_GRP, PON_VENDORMERGE_GRP, POS_VENDORMERGE_GRP, and the other installed product groups (AHL, FA, FUN, IRC, JL, MRP, OKL, OZF, WSH) so that contact rows and supplier mappings owned by each product are migrated to the surviving party. The procedure is not intended for direct customer invocation; it is called from the merge orchestration framework.

Tables Accessed

• AP_DUPLICATE_VENDORS_ALL, AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, AP_SYSTEM_PARAMETERS_ALL — sources of the duplicate/surviving vendor identifiers, site definitions, and Payables system options used to drive merge logic.
• AP_SUPPLIER_CONTACTS and PO_VENDOR_CONTACTS_S — supplier contact records, including the contact table that users search for when tracing contact re-pointing after a merge.
• POS_CONTACT_REQUESTS and POS_SUPPLIER_MAPPINGS — iSupplier Portal supplier mappings and contact request rows that must reference the surviving vendor.
• HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, HZ_PARTY_SITES, HZ_PARTY_SITE_NUMBER_S, HZ_PARTY_USG_ASSIGNMENTS, HZ_CONTACT_POINTS — the TCA entities updated via the corresponding V2PUB APIs to move contacts, contact points, and party-site usage to the surviving party.

Usage Notes

This package is invoked indirectly through the standard Oracle Payables supplier merge program, not through a direct user action. It participates in the merge setup workflow where users select duplicate vendors, choose whether to merge contacts and sites, and submit the merge. The package uses FND_API, FND_MSG_PUB, FND_LOG, and FND_PROFILE for error handling, message propagation, logging, and organizational context (via MO_GLOBAL), and it relies on APPS.AP_VENDOR_PARTY_MERGE_PKG as an internal reference. It is also referenced by one other APPS package. Because merge operations are irreversible and touch multi-org and TCA data, usage is restricted to authorized merge administrators; any custom code that queries PO_VENDOR_CONTACTS_S or supplier contacts should account for the re-pointing performed here.