Search Results hz_merge_batch_s




Overview
Explore in AI Chat

Overview

HZ_MERGE_BATCH_PKG is an Oracle E-Business Suite package body owned by the APPS schema that supports the party merge infrastructure within the Oracle Trading Community Architecture (TCA). The package is classified as an "OTHER" API and operates on the HZ_MERGE_BATCH and HZ_MERGE_BATCH_S tables, which store batch header records used to group and track large-scale merge operations of parties, party sites, or related entities. Its primary business purpose is to provide the standard data manipulation primitives used to maintain rows in the merge batch entity within the TCA data model.

The package body carries a status of VALID, confirming it compiles successfully in the documented environment. It does not appear as a referenced object in the dependency graph, meaning it is a top-level entry point rather than a subordinate library called by other database objects. Conversely, two other packages reference it, and it depends upon APP_EXCEPTION, FND_API, FND_MESSAGE, STANDARD, DUAL, and the HZ_MERGE_BATCH_PKG specification. These dependencies reflect a typical TCA public API pattern: layered error handling via FND_MESSAGE and APP_EXCEPTION, DML against the underlying TCA tables, and the mandatory declaration supplied by the package specification.

Key Procedures and Functions

The package body exposes four documented procedures, all of which implement the standard TCA row-maintenance contract:

  • INSERT_ROW — Creates a new row in the merge batch table, populating the documented columns from the caller-supplied record and stamping standard WHO columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.
  • UPDATE_ROW — Modifies an existing merge batch row, applying the changed attribute values while updating the audit columns and, where applicable, the object version number for optimistic locking.
  • LOCK_ROW — Acquires a row-level lock on a specific merge batch record, supporting concurrent access control when multiple sessions attempt to act on the same batch.
  • DELETE_ROW — Removes a merge batch row from the underlying table, allowing obsolete or completed batches to be purged.

No parameter signatures are documented in the ETRM metadata, so callers should consult the corresponding package specification or the TCA data model documentation for exact argument lists before invoking these procedures directly.

Tables Accessed

The package reads from and writes to two documented tables, both accessed through APPS synonyms:

  • HZ_MERGE_BATCH — The primary base table holding the merge batch header records. INSERT_ROW, UPDATE_ROW, LOCK_ROW, and DELETE_ROW all perform their DML against this table.
  • HZ_MERGE_BATCH_S — The sequence or supporting table associated with HZ_MERGE_BATCH, used to generate or store unique identifiers for each merge batch row. The presence of this table in the dependency list confirms the package participates in key generation for new batch records.

Usage Notes

HZ_MERGE_BATCH_PKG is an internal TCA row-handler package rather than a business-facing merge engine. It is typically invoked indirectly by higher-level merge orchestration code, by the two packages that reference it, or by the Oracle Forms user interface behind the party merge and merge batch maintenance screens. Because the procedures follow the standard FND_API and APP_EXCEPTION error-handling convention, any custom code that calls them must implement the usual API error-checking pattern: initialize the FND message stack, invoke the procedure, and check the returned status before committing.

Direct invocation from custom concurrent programs or SQL scripts is supported but should be treated with caution, since bypassing the calling forms or orchestration packages may skip validation, audit stamping, or downstream processing required for a consistent merge batch state. When customising TCA merge behaviour, Oracle recommends using the public package specification rather than re-implementing DML against HZ_MERGE_BATCH or HZ_MERGE_BATCH_S directly.