Search Results ego_user_attr_data_obj




Overview
Explore in AI Chat

Overview

POS_MERGE_SUPPLIER_PKG is an Oracle E-Business Suite purchasing package body owned by the APPS schema and classified as an "OTHER" API within the ETRM repository. Its principal business function is to support supplier merge and party consolidation operations within Oracle Purchasing and Oracle Payables. In Oracle EBS 12.1.1 and 12.2.2, supplier records and their associated Trading Community Architecture (TCA) party records may need to be merged—for example, when duplicate supplier records are identified or when two supplier organizations are consolidated following a corporate reorganization. When a merge occurs at the HZ_PARTIES level, the corresponding supplier, supplier site, business classification, product and service, bank detail, contact, and user-defined attribute (UDA) data must be reconciled or migrated consistently. POS_MERGE_SUPPLIER_PKG encapsulates that logic, coordinating changes across the purchasing supplier model while respecting TCA party integrity.

The package header carries the version marker "$Header: POSMRGSUPB.pls 120.1.12020000.3 2012/07/23" indicating this is a relatively recent, patched version shipped under the 12.2.x code line. The presence of NOCOPY OUT parameters in its internal procedure signatures (for example, x_return_status, x_msg_count, and x_msg_data) follows the standard PL/SQL API error-handling pattern used throughout EBS, allowing callers to inspect the outcome of each operation without raising exceptions into the calling form or concurrent program.

Key Procedures and Functions

  • BUSS_CLASS_MERGE — Handles the merge of supplier business classification records (such as minority-owned, small business, or veteran-owned designations) when two suppliers are combined. It depends on data in POS_BUS_CLASS_ATTR and coordinates with POS_SUPP_CLASSIFICATION_PKG.
  • PROD_SERVICE_MERGE — Merges product and service classification information associated with the source and target suppliers.
  • BANK_DTLS_MERGE — Reconciles external payee and payment instrument records, ensuring bank account details stored in IBY_EXTERNAL_PAYEES_ALL and IBY_PMT_INSTR_USES_ALL remain valid for the surviving supplier.
  • ENABLE_PARTY_AS_SUPPLIER — Ensures the merged party is enabled and recognized as a supplier in the purchasing schema.
  • PARTY_CONTACT_MERGE — Migrates contact and contact-point relationships between parties, preserving HZ_PARTY_SITES and contact associations.
  • SUPPLIER_UDA_MERGE — Merges user-defined attribute (UDA) values for the supplier. This is the procedure most closely related to the user's search term "ego_user_attr_data_obj": EGO user-defined attributes are stored in EGO extension tables and surfaced via the EGO_ATTRS_V view, and this procedure transfers those values between supplier profiles. The internal create_bus_attr procedure references attributes_rec and attributes_coll_tab structures built from EGO_ATTRS_V, demonstrating the package's direct dependency on ego_user_attr_data_obj semantics.
  • PARTY_SITE_UDA_MERGE — Merges UDA values at the party site level.
  • SUPPLIER_SITE_UDA_MERGE — Merges UDA values at the supplier site level.

Tables Accessed

The package reads and writes a broad set of purchasing, payables, and TCA tables through APPS synonyms. AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL hold the core supplier and site records. HZ_PARTIES, HZ_PARTY_SITES, HZ_ORIG_SYS_REFERENCES, HZ_MERGE_PARTIES, and HZ_MERGE_PARTY_DETAILS support TCA-level party identity and merge tracking. EGO_FND_DSC_FLX_CTX_EXT provides the descriptive flexfield context extension used for UDA storage. IBY_EXTERNAL_PAYEES_ALL and IBY_PMT_INSTR_USES_ALL store external payee and payment instrument data. FINANCIALS_SYSTEM_PARAMETERS and FND_LOOKUP_VALUES supply system configuration and lookup values. POS_BUS_CLASS_ATTR, POS_SUPPLIER_MAPPINGS, and POS_SUPPLIER_UDA_MERGE_GTT (a global temporary table) support classification, mapping, and staging operations. EGO_ATTRS_V, referenced in the package body, provides the attribute metadata used to construct UDA merging logic.

Usage Notes

POS_MERGE_SUPPLIER_PKG is typically invoked indirectly through the Oracle Supplier Merge concurrent program or the supplier merge user interface in Oracle Payables and Purchasing, rather than being called directly by end users. Customizations that extend supplier merge behavior may call the package from custom concurrent programs or PL/SQL scripts, but doing so requires careful handling of the standard API error outputs (x_return_status, x_msg_count, x_msg_data). Because the package operates on TCA party data as well as purchasing data, any invocation should be preceded by a validated TCA party merge and followed by verification that supplier, site, bank, contact, and UDA data were all transferred correctly. The package is referenced by one other package in the ETRM metadata, so dependency analysis should include that caller. In 12.1.1 and 12.2.2 the file version and patch level should be confirmed against the current AD patch set to avoid regression from known fixes in the 120.1.12020000 line.