Results for “remove_flag”

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

Overview

HZ_DUP_SET_PARTIES is a Receivables (AR) module table that records the individual parties belonging to a Duplicate Party Set within Oracle E-Business Suite. It is a child table in the Oracle Trading Community Architecture (TCA) duplicate-resolution framework, which allows data stewards and automated processes to group suspected duplicate party records, score their likelihood of being duplicates, and drive merge decisions. The table is owned by the AR schema and is marked VALID in both 12.1.1 and 12.2.2 instances, where it contains sixteen documented columns.

The table functions primarily as a resolution or decision worksheet: each row represents one party's membership in a duplicate set, carrying a computed similarity score and one or more flags indicating whether the party should be merged, retained, or removed. Under the heuristic Data Vault classification derived from the foreign key structure, this object is characterized as satellite-leaning. In modeling terms, the combination of DUP_SET_ID and DUP_PARTY_ID behaves as a descriptive attribute cluster attached to the duplicate-set/batch hub, rather than as an independent hub or link. This classification is a suggestion, not an enforced design constraint.

Key Information Stored

The table’s documented business-key candidate is defined by the unique index HZ_DUP_SET_PARTIES_U1, covering the composite of DUP_SET_ID and DUP_PARTY_ID. These two columns together identify a party's membership within a specific duplicate set and form the natural key for the row. The surrogate identifier carried on the table is DUP_PARTY_ID, and DUP_SET_ID links the row to its parent duplicate set. The business columns that drive duplicate-resolution processing include:

• SCORE — the computed similarity score used to rank how closely the party matches others in the set.
• MERGE_FLAG — indicates whether the party is designated for merge as a duplicate survivor or victim.
• NOT_DUP — marks parties explicitly excluded from duplicate consideration.
• REMOVE_FLAG — signals that the party should be removed from the duplicate set.
• MERGE_SEQ_ID — establishes the ordering sequence for merge execution.
• MERGE_BATCH_ID — the foreign key to HZ_MERGE_BATCH, tying the row to its governing merge batch.
• MERGE_BATCH_NAME — the descriptive name of the associated merge batch.
• GROUP_SET — groups parties within the duplicate set for processing or review.
• DUP_SET_BATCH_ID — links the duplicate set to a batch context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified each row and when.

Common Use Cases and Queries

Typical use cases include reviewing unresolved duplicate sets, identifying high-confidence duplicate pairs for automated merge, excluding false positives, and reporting on merge batch progress. Reporting frequently joins this table to HZ_MERGE_BATCH to reconcile batch-level counts against member-level decisions.

A representative query retrieves all parties in a duplicate set ordered by score:

SELECT d.DUP_SET_ID, d.DUP_PARTY_ID, d.SCORE, d.MERGE_FLAG, d.NOT_DUP, d.REMOVE_FLAG
FROM   AR.HZ_DUP_SET_PARTIES d
WHERE  d.DUP_SET_ID = :set_id
ORDER BY d.SCORE DESC;

A second pattern counts merge-designated parties per batch, useful for reconciling batch execution:

SELECT d.MERGE_BATCH_ID, d.MERGE_BATCH_NAME, COUNT(*) merge_count
FROM   AR.HZ_DUP_SET_PARTIES d
WHERE  d.MERGE_FLAG = 'Y'
AND    d.NOT_DUP = 'N'
GROUP BY d.MERGE_BATCH_ID, d.MERGE_BATCH_NAME;

Because the table is transaction-facing and frequently updated during merge processing, queries should be limited and indexed on the DUP_SET_ID and MERGE_BATCH_ID predicates to avoid full scans.

Related Objects

The most significant related object is the parent merge batch table referenced by the documented foreign key. Keys that join across the duplicate-resolution model include:

• HZ_MERGE_BATCH — joined on HZ_DUP_SET_PARTIES.MERGE_BATCH_ID = HZ_MERGE_BATCH.MERGE_BATCH_ID; the governing batch header for the duplicate set.
• HZ_DUP_SETS — the duplicate set definitions linked through DUP_SET_ID.
• HZ_PARTIES — the party master table resolved through DUP_PARTY_ID.
• HZ_MERGE_HISTORY — records the outcome of merges applied to parties selected from this table.
• HZ_DUP_SET_PARTIES self-reference through DUP_SET_BATCH_ID for batch-level grouping.
• HZ_PARTY_MERGE_API / HZ_MERGE_PARTY public TCA merge APIs, which consume merge-designated rows selected from this table.

These objects together form the TCA duplicate-resolution and merge pipeline, with HZ_DUP_SET_PARTIES acting as the decision layer between identified duplicate sets and executed party merges.