Search Results buss_class_merge




Overview
Explore in AI Chat

Overview

APPS.POS_MERGE_SUPPLIER_PKG is a supplier-side merge handler package in Oracle E-Business Suite, owned by the APPS schema and classified as OTHER in the ETRM metadata. Its business purpose is to support Oracle Trading Community Architecture (TCA) party merge operations that involve supplier entities. When two parties (typically supplier-related parties) are merged through the standard TCA Party Merge process, the merge framework invokes registered entity handlers so that dependent supplier records are re-pointed from the "from" party to the "to" party. POS_MERGE_SUPPLIER_PKG provides those handler entry points for the supplier domain, covering business classifications, products and services, bank details, contacts, and descriptive flexfield based user-defined attributes at both the party and party site level. The package header uses AUTHID CURRENT_USER, and the source header indicates a file version of 120.1 dated 2010/11/25, consistent with its availability across Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes eight documented procedures, each following the TCA merge handler convention of accepting entity identification, from/to identifier, parent entity information, and batch context parameters, and returning a status. The documented procedures are:

  • BUSS_CLASS_MERGE — merges supplier business classification attribute records associated with the merged parties.
  • PROD_SERVICE_MERGE — merges supplier products and services data linked to the parties being consolidated.
  • BANK_DTLS_MERGE — merges supplier bank detail records, including payment instrument usage and external payee information.
  • ENABLE_PARTY_AS_SUPPLIER — the handler relevant to the user search; it ensures that the surviving (target) party is enabled and set up as a supplier following the merge, so that supplier functionality remains available on the merged party.
  • PARTY_CONTACT_MERGE — merges supplier party contact records between the source and target parties.
  • SUPPLIER_UDA_MERGE — merges supplier-level user-defined attributes.
  • PARTY_SITE_UDA_MERGE — merges user-defined attributes defined at the party site level.
  • SUPPLIER_SITE_UDA_MERGE — merges user-defined attributes defined at the supplier site level.

Each procedure returns a status through an output parameter, allowing the calling merge framework to detect and report success or failure.

Tables Accessed

The package reads and writes a range of supplier, party, and payment tables through APPS synonyms. Supplier master and site data are handled via AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL. Party-level information is managed through HZ_PARTIES, HZ_PARTY_SITES, HZ_MERGE_PARTIES, HZ_MERGE_PARTY_DETAILS, and HZ_ORIG_SYS_REFERENCES. Payment and payee data are accessed through IBY_EXTERNAL_PAYEES_ALL and IBY_PMT_INSTR_USES_ALL. Supplier classification and mapping records reside in POS_BUS_CLASS_ATTR and POS_SUPPLIER_MAPPINGS. Descriptive flexfield context data is read from EGO_FND_DSC_FLX_CTX_EXT and FND_LOOKUP_VALUES, while system-level defaults come from FINANCIALS_SYSTEM_PARAMETERS. Temporary staging for user-defined attribute merges uses POS_SUPPLIER_UDA_MERGE_GTT.

Usage Notes

This package is not intended for direct invocation by end users or custom code in normal operation. It is registered as a merge handler within the TCA Party Merge framework and is invoked automatically when a party merge is executed, including merges initiated from supplier-facing forms or concurrent programs. In Oracle EBS 12.1.1 and 12.2.2, the standard Party Merge concurrent program and related supplier merge flows call these procedures through the merge handler registration mechanism. Customizations should avoid calling the procedures directly because the parameters, particularly the batch identifiers and parent entity context, must be populated by the merge engine. Developers troubleshooting merge issues, especially failures to retain supplier enablement, should review the output status returned by ENABLE_PARTY_AS_SUPPLIER and verify that the target party retains valid HZ_PARTIES, AP_SUPPLIERS, and IBY payee associations after the merge completes.