Search Results pon_vendormerge_grp




Overview
Explore in AI Chat

Overview

PON_VENDORMERGE_GRP is a PL/SQL package owned by the APPS schema that supports supplier consolidation within Oracle Purchasing. The package name, together with its single documented entry point, indicates that it exists to allow buyer-facing purchasing records to be re-pointed from one supplier to another when two supplier records are merged in Oracle Payables and Oracle Purchasing. In Oracle E-Business Suite, supplier merging is a controlled administrative operation: duplicate or superseded supplier records are combined so that a single surviving supplier carries the transactional history of both. Because Purchasing maintains its own supplier-linked data — sourcing, bidding, acknowledgements, and supplier access records — a dedicated package is required to migrate those references safely.

The GRP suffix identifies the package as a group or driver unit rather than a base API. It is the orchestration layer that the higher-level vendor merge process calls, rather than a public API intended for direct invocation by end users or external integrations.

Key Procedures and Functions

The ETRM metadata documents a single entry point:

  • MERGE_VENDOR — the operational procedure that performs the Purchasing-side re-pointing of supplier references during a vendor merge. It is the procedure other components invoke when the surviving supplier has been determined by the merge driver.

No parameter lists are documented. The procedure is designed to be called from within an existing merge transaction so that all affected Purchasing records are updated consistently with the Payables-side merge.

Tables Accessed

The package references the following tables through APPS synonyms. Each has a clear role in the merge:

Usage Notes

PON_VENDORMERGE_GRP is not intended for direct invocation by end users. It is invoked by the supplier merge facility in Oracle Payables and Purchasing, and its documented dependents confirm this: AP_VENDOR_PARTY_MERGE_PKG and the package itself reference it, meaning the merge path drives it rather than external code. It depends in turn on FND_API and STANDARD, consistent with a package that uses the Oracle Application Object Library programming standards, including error handling and savepoint conventions.

When implementing custom supplier merge logic or extending merge behavior, the correct approach is to call the standard merge process rather than MERGE_VENDOR directly, so that transaction control, validation, and dependent Payables records remain synchronized. This behavior is consistent across Oracle EBS 12.1.1 and 12.2.2. Administrators performing merges should back up affected purchasing data beforehand, since a merge rewrites the supplier foreign key across many PON tables.