Results for “merge_trx_headers”

14 results




Overview
Explore in AI Chat

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

Overview

FUN_PARTY_MERGE_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports Oracle Receivables and the Trading Community Architecture (TCA) during party merge operations. Its central business purpose is to preserve referential integrity when two trading community parties—typically customers, suppliers, or related parties—are consolidated into a single surviving party record through the Oracle Trading Community Architecture (HZ) party merge process.

The package declares AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking schema rather than the defining schema. Its header retains the standard version identifier funptymerges.pls 120.0, indicating an early-generation Receivables source file. The package is an internal extension point consumed by the HZ Party Merge routine rather than a general-purpose API. Consequently, it is not intended for direct invocation by forms, concurrent programs, or custom code outside the sanctioned merge framework.

Key Procedures and Functions

ETRM documents five public procedures, each addressing a distinct Receivables entity that carries a party or party-site foreign key:

  • MERGE_TRX_BATCHES — Reassigns transaction batches from the losing (from) party to the surviving (to) party. It accepts the HZ entity name, source and target identifiers, the facility IDs before and after the merge, the party foreign-key values before and after, the parent entity name, and the batch identifiers, returning a status indicator.
  • MERGE_TRX_HEADERS — Updates transaction headers so that initiator and recipient references tied to the merged relationship party are consolidated onto the surviving party.
  • MERGE_DIST_LINES — Repoints Receivables distribution lines associated with the merged party to the surviving party identifiers, keeping accounting distributions aligned with the surviving entity.
  • MERGE_CUSTOMER_MAPS — Updates the customer mapping records that link Receivables customer identifiers to TCA party records, ensuring mapped identifiers reflect the surviving party.
  • MERGE_SUPPLIER_MAPS — Performs the equivalent remapping for supplier mappings, aligning supplier references held in Receivables with the surviving party.

Each procedure follows the HZ party merge calling convention and signals outcome through a return-status output parameter rather than raising exceptions for routine conditions.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

  • FUN_TRX_BATCHES — Transaction batch records whose owning party reference is updated by MERGE_TRX_BATCHES.
  • FUN_TRX_HEADERS — Transaction header rows holding initiator and recipient party identifiers.
  • FUN_DIST_LINES — Distribution line records carrying party references that must follow the surviving party.
  • FUN_CUSTOMER_MAPS — Mapping between Receivables customer identifiers and TCA parties.
  • FUN_SUPPLIER_MAPS — Mapping between supplier references and TCA parties.
  • HZ_MERGE_BATCH — The HZ merge batch control table that drives and coordinates the merge, providing batch context to the procedures.

Usage Notes

FUN_PARTY_MERGE_PUB is invoked exclusively by the HZ Party Merge routine through the registered merge-handler mechanism. The header comments explicitly state that its procedures "should not be called by any other application." The package is referenced by zero other packages per ETRM, confirming it is a leaf-level handler rather than a shared utility. In practice it is triggered when an administrator submits a party merge from the TCA party merge interface; the merge engine calls each registered handler, including this package, to propagate identifier changes across Receivables tables. Direct invocation in custom code, concurrent programs, or forms is not supported and risks corrupting party references and mapping tables.