Search Results fun_vendormerge_grp




Overview
Explore in AI Chat

Overview

The APPS.FUN_VENDORMERGE_GRP package is a public PL/SQL group package in Oracle E-Business Suite that provides a programmatic interface for merging duplicate supplier (vendor) records within Oracle Payables and the underlying supplier data model. The package exposes a single documented entry point, MERGE_VENDOR, which allows an application or custom code to consolidate two supplier records — an active vendor and a duplicate vendor — along with their associated supplier sites, into a single surviving entity. This functionality is central to supplier master data cleansing, where duplication caused by manual entry, conversion loads, or multiple trading partners must be resolved without breaking existing transactions, purchase orders, invoices, or payment relationships that reference the duplicate.

The GRP suffix in the API classification indicates that this is a group-level API, meaning it conforms to the standard Oracle EBS API conventions: it accepts the standard p_api_version, p_init_msg_list, p_commit, and p_validation_level parameters, and returns status and message information through the standard p_return_status, p_msg_count, and p_msg_data OUT parameters. This convention allows callers to perform bulk merge operations within a single transaction and to inspect the outcome through the standard FND message stack.

Key Procedures and Functions

  • MERGE_VENDOR — The sole documented procedure in this package. It performs the supplier merge operation, taking the identifiers of the active supplier, the duplicate supplier, the active supplier site, and the duplicate supplier site as its merge input parameters. Based on the documented signature, the procedure expects p_vendor_id and p_dup_vendor_id to identify the surviving and the duplicate supplier respectively, with p_vendor_site_id and p_dup_vendor_site_id narrowing the operation to specific sites. It returns the standard API outcome through the return status and message parameters. The procedure serves as the sanctioned, supported mechanism for vendor de-duplication, ensuring that referential integrity and dependent objects are updated consistently rather than relying on ad hoc table updates.

Tables Accessed

  • FUN_NET_SUPPLIERS_ALL — The base supplier table underlying the Oracle Payables supplier model. The merge procedure reads and updates this table to consolidate the duplicate supplier record into the surviving supplier record, describing the canonical supplier identity. All dependent supplier sites, contacts, and transactional references are expected to be resolved as part of this operation. This is the only table documented as referenced through APPS synonyms for this package.

Usage Notes

This package is typically invoked by the Supplier Merge concurrent program or by standard Oracle Payables forms that provide the supplier merge user interface, where the end user selects the source and target suppliers and sites to combine. Custom integrations, data-cleansing scripts, and conversions may call MERGE_VENDOR directly following the standard Oracle API invocation pattern: initialize the message list, set the validation level, call the API, check p_return_status for FND_API.G_RET_STS_SUCCESS, and handle any error messages returned in the message stack. Because the procedure defaults p_commit to FND_API.G_FALSE, callers are responsible for committing the transaction explicitly when they supply their own commit logic; passing FND_API.G_TRUE allows the API to commit on success. Given that the package is documented as being referenced by one other package, custom code should avoid reimplementing vendor merge logic and instead depend on this group API to preserve supported behavior, as direct DML against supplier tables risks orphaning dependent records and violating the supplier data model integrity maintained by the merge process.