Results for “mrp_vendormerge_grp”

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

Overview

The APPS.MRP_VENDORMERGE_GRP package body is a Group-type (GRP) PL/SQL API in Oracle E-Business Suite, residing in the APPS schema and validated on both release 12.1.1 and 12.2.2. Its principal business function is to support vendor consolidation within Oracle Advanced Supply Chain Planning (ASCP) and Oracle Purchasing sourcing configurations. When two supplier records are merged as part of a supplier merge operation, sourcing rules and their associated receipt and source organization assignments that reference the obsolete vendor must be repointed to the surviving supplier. This package encapsulates that maintenance logic, preserving the integrity of approved supplier lists and sourcing documentation that would otherwise become orphaned or point to an invalid vendor site after the merge completes.

The API is classified as a GRP package, indicating it exposes a single public entry point intended to be called programmatically rather than through a form-driven interface. It is not referenced by any other database object per the documented dependency graph, confirming that it is a self-contained utility invoked by external callers rather than embedded within a larger package hierarchy.

Key Procedures and Functions

The package body documents a single public program unit, MERGE_VENDOR. Its purpose is to update sourcing rule and organization assignment records so that references to a from-vendor are replaced with references to a to-vendor. The procedure operates as an atomic unit of work and is intended to be called after the core supplier merge has established the surviving supplier record.

• MERGE_VENDOR — Repoints vendor references held in ASCP sourcing rule definitions and their associated receipt organization and source organization rows from the obsolete supplier to the surviving supplier.

Because the metadata documents only the procedure name and no parameter list, callers should verify the exact signature against the deployed package specification in the target instance before invoking it. The absence of additional documented program units indicates that all supporting logic — validation, error capture, and message publication — is contained within MERGE_VENDOR or its private helpers.

Tables Accessed

The package body references three application tables through APPS synonyms, all belonging to the ASCP sourcing data model:

• MRP_SOURCING_RULES — Stores sourcing rule headers and lines that designate approved suppliers for items and organizations. The merge updates vendor references held on these rules.
• MRP_SR_RECEIPT_ORG — Defines the receipt organizations associated with a sourcing rule. Rows tied to the merged vendor must be reconciled so receipt routing remains valid.
• MRP_SR_SOURCE_ORG — Defines the source organizations for a sourcing rule. These records are likewise repointed during the merge.

In addition, the package depends on the FND_API, FND_MESSAGE, and FND_MSG_PUB utilities for error handling and message retrieval, and on DBMS_OUTPUT and PLITBLM for diagnostic output and PL/SQL table manipulation.

Usage Notes

MRP_VENDORMERGE_GRP is typically invoked as a programmatic step within a supplier merge flow, called after the standard supplier merge process has completed the core consolidation of vendor and vendor site records. It is not attached to a concurrent program or form in the documented metadata, so invocation is expected from custom PL/SQL, a wrapper concurrent program, or an extension to the purchasing supplier merge workflow. Because the ETRM record shows the package is not referenced by any other database object, integrators should treat it as a purpose-built API requiring explicit sequencing and commit management by the calling process. Testing on both 12.1.1 and 12.2.2 is advisable given the release-specific differences in sourcing and supplier merge behavior.