Search Results merge_vendor

Overview

IRC_VENDORMERGE_GRP is a PL/SQL package body owned by APPS in Oracle E-Business Suite, classified in ETRM as a "GRP" (group) API type. It exists to support supplier (vendor) merge operations within the Oracle iRecruitment module. When two supplier records are identified as duplicates — typically as the result of a third-party or Oracle-supplied supplier merge routine — the corresponding agency records referenced by iRecruitment must be repointed from the duplicate vendor to the surviving (master) vendor. IRC_VENDORMERGE_GRP performs exactly this consolidation of agency references, ensuring that recruitment data such as agency-linked vacancies and notification preferences remain valid after a vendor merge has been executed elsewhere. The package header carries an identifier dated 2006, placing it within the standard 11i/12.x code line, and it remains present and documented in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes a single documented procedure:

• MERGE_VENDOR — The core routine that performs the iRecruitment-side cleanup for a supplier merge. It accepts identifiers for both the surviving entity and the duplicate: the vendor and duplicate vendor, the vendor site and duplicate vendor site, the party and duplicate party, and the party site and duplicate party site. It follows the standard Oracle API error-handling pattern, accepting API version, initialization-message-list, commit, and validation-level control parameters, and returning status, message count, and message data as OUT parameters. All of the actual work performed is data repointing rather than any vendor-record creation; the procedure assumes the underlying supplier merge has already been or will be carried out by the calling process.

Tables Accessed

The procedure updates three base structures through APPS synonyms, and reads one:

• IRC_AGENCY_VACANCIES — Updated so that rows previously pointing to the duplicate agency (vendor) are reassigned to the surviving agency. This preserves the association between vacancies and the retained recruitment agency.
• IRC_NOTIFICATION_PREFERENCES — Updated for the same reason, so that notification settings configured against the duplicate agency follow the surviving agency.
• FND_PROFILE_OPTION_VALUES — Updated so that any stored value equal to the duplicate vendor identifier is replaced by the surviving vendor identifier, but only where the profile option is the iRecruitment agency profile (IRC_AGENCY_NAME). The FND_PROFILE_OPTIONS table is read to resolve the profile option ID for that name.

Usage Notes

MERGE_VENDOR issues a savepoint (IRC_MERGE_VENDOR) before performing its updates; if any error occurs, it rolls back to that savepoint and returns FND_API.G_RET_STS_ERROR, leaving the caller's surrounding transaction intact. It is not intended to be invoked directly by end users. It is normally called from a supplier merge flow — for example, a wrapper package or custom merge program that has already determined that the vendors being merged are used as iRecruitment agencies. ETRM records that the package is referenced by one other package, consistent with its role as a subordinate merge handler rather than a top-level entry point. Because it relies on the standard FND_API messaging and return-status conventions, callers should check p_return_status and inspect the message stack via FND_MSG_PUB, and should honor the p_commit and p_validation_level arguments in line with Oracle API coding standards.