Search Results hz_merge_dictionary




Overview
Explore in AI Chat

Overview

HZ_MERGE_DICTIONARY is a reference and control table owned by the AR (Receivables) schema in Oracle E-Business Suite, documented as valid in both 12.1.1 and 12.2.2. Its stated purpose is to identify the tables affected by the party merge concurrent program. In effect, the dictionary is a metadata registry: each row describes one participating table or entity, the key columns that drive the merge, and the procedural logic the merge engine must invoke when consolidating a "from" party into a "to" party. Because the party merge process touches a large and evolving set of dependent objects across Oracle Trading Community Architecture (TCA), this table allows the merge framework to remain extensible without hard-coding table names into program logic.

From a Data Vault modeling perspective, the mined relationship structure classifies this object as hub-leaning. This is a modelling suggestion rather than a documented constraint: the primary key MERGE_DICT_ID behaves in a business-key manner, identifying a discrete merge-target entity, and the two dependent history and log tables attach to it as satellites or links. The table carries a composite unique index, HZ_MERGE_DICTIONARY_U1 on (MERGE_DICT_ID, ZD_EDITION_NAME), reflecting edition-based redefinition support introduced with 12.2 online patching. The 23 documented columns cover identification, join construction, and procedural dispatch.

Key Information Stored

The surrogate primary key is MERGE_DICT_ID, enforced by HZ_MERGE_DICTIONARY_PK. The unique index HZ_MERGE_DICTIONARY_U1 (MERGE_DICT_ID, ZD_EDITION_NAME) is the business-key candidate when editioning is in scope. Other significant columns include:

Common Use Cases and Queries

Typical use cases include investigating why a party merge did not update a particular table, extending the merge framework to include a custom table, and auditing which entities the concurrent program processes. A common query lists entities and their execution order:

  • SELECT ENTITY_NAME, PK_COLUMN_NAME, FK_COLUMN_NAME, PROCEDURE_NAME FROM HZ_MERGE_DICTIONARY ORDER BY SEQUENCE_NO;
  • Locate rows by rule set: SELECT * FROM HZ_MERGE_DICTIONARY WHERE RULE_SET_NAME = :rule_set AND BULK_FLAG = 'Y';
  • Audit merge activity by joining to the log: SELECT d.ENTITY_NAME, l.* FROM HZ_MERGE_DICTIONARY d, HZ_MERGE_PARTY_LOG l WHERE d.MERGE_DICT_ID = l.MERGE_DICT_ID;

Related Objects

The documented foreign keys show two dependent child tables, both joined on MERGE_DICT_ID:

  • HZ_MERGE_PARTY_HISTORY (HZ_MERGE_PARTY_HISTORY.MERGE_DICT_ID) — captures historical merge outcomes per dictionary entry.
  • HZ_MERGE_PARTY_LOG (HZ_MERGE_PARTY_LOG.MERGE_DICT_ID) — runtime logging of party merge execution.

In practice these are complemented by the party merge concurrent program and the TCA party entities (HZ_PARTIES and associated contact, account, and location tables) whose keys the dictionary rows describe. DBA and developer queries against AR.HZ_MERGE_DICTIONARY should account for the ZD_EDITION_NAME column in 12.2 environments to avoid returning rows from inactive editions.