Search Results g_init_version

Overview

OKL_VENDORMERGE_GRP is a group-type PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that centralizes vendor merge processing for Oracle Lease and Finance Management (OKL). When two vendor records are consolidated into a single surviving vendor during a supplier merge operation, the operational and financial data held against the duplicate vendor must be reassigned so that contract, asset, and accounting relationships remain intact. This package provides the single public entry point — MERGE_VENDOR — through which that reassignment is performed across the OKL and OKC table set.

The package follows the standard EBS API group (GRP) pattern: it declares package-level constants for the package name (G_PKG_NAME), application short name (G_APP_NAME), API type suffix (G_API_TYPE), and an initialization version marker (G_INIT_VERSION, set to 1.0). The G_INIT_VERSION constant is the object most often located through a search on that identifier; it identifies the API version expected by the merge routine and is referenced when callers or dependent code validate that the correct group API revision is available in the instance.

Key Procedures and Functions

The package exposes exactly one documented procedure, MERGE_VENDOR. Its stated purpose is to update OKL data when two vendors are merged. The procedure accepts the standard EBS API control parameters — API version, initialization of the message list, commit flag, and validation level — and returns the standard outcome triplet of return status, message count, and message data. On the business side, it receives the identifiers that describe both sides of the merge: the surviving and duplicate vendor identifiers, the corresponding vendor site identifiers, and the equivalent party and party site identifiers. This parameter set reflects the fact that supplier merge operates at both the vendor (supplier) level and the party level in the Trading Community Architecture model.

No additional public functions or procedures are documented for this package, so all merge logic is contained within this single entry point. The procedure is not documented as returning a value; results are communicated through the OUT parameters in the standard FND_API convention.

Tables Accessed

The package reads and writes a broad cross-section of OKL and OKC tables through APPS synonyms. Contract structures are represented by OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_K_PARTY_ROLES_B, and OKC_RULES_B, which carry the contract header, line, item, party role, and rule definitions that may be tied to vendor parties. Asset and cost data is handled through OKL_ASSET_COMPONENTS_B and OKL_COST_ADJUSTMENTS_B. Consolidated payables invoices are located in OKL_CNSLD_AP_INVS_ALL.

The cure-related tables — OKL_CURE_FUND_SUMS_ALL, OKL_CURE_FUND_TRANS_ALL, OKL_CURE_REFUNDS_ALL, OKL_CURE_REFUND_HEADERS_B, OKL_CURE_REFUND_STAGE, and OKL_CURE_REPORTS_ALL — carry funding, transaction, refund, staging, and reporting data that must be repointed when the vendor changes. FND_LOG_MESSAGES is used for debug and error logging consistent with the FND logging framework.

Usage Notes

OKL_VENDORMERGE_GRP is typically invoked indirectly, as part of the supplier merge process initiated from Oracle Payables or the supplier merge concurrent program, rather than being called directly by end users. The ETRM metadata records that the package is referenced by one other package, indicating that a higher-level orchestration routine or API wrapper calls MERGE_VENDOR after the merge event is detected. Customizations that extend vendor merge behavior should preserve the standard API parameter contract and honor the commit and validation-level flags, since the caller controls transaction boundaries. Because the procedure touches contract, asset, cure, and payables invoice data in a single unit of work, it should be invoked with an appropriate validation level and with commit deferred until the full merge set has been processed.