Search Results insert_add_party_site

Overview

ARH_DQM_TREE_HELPER is a helper package body in the Oracle E-Business Suite Receivables and Trading Community Architecture (TCA) data quality management layer. Its name and contents place it within the Data Quality Management (DQM) deduplication and matching framework introduced in the 11.5.10/12.x code line. The package provides low-level utility logic used during party, party site, contact, and contact point matching. It works exclusively against the DQM global temporary staging tables (the _GT tables) that hold candidate matches generated while a match or deduplication run is in progress, together with the base TCA entities HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, HZ_PARTY_SITES, and HZ_CONTACT_POINTS.

The header comment ($Header: ARHDQMBB.pls 120.1 ... noship $) confirms the package is a non-shipped internal implementation unit, and the ETRM classification of OTHER reinforces that it is not a public API. It is referenced by eleven other packages, indicating it is a shared building block for the DQM orchestration packages rather than an entry point invoked directly by end users.

Key Procedures and Functions

• CTXMAX — Function returning the maximum SEARCH_CONTEXT_ID currently present in HZ_MATCHED_PARTIES_GT, or zero when the table is empty. Used to establish or locate the active search context identifier for a match run.
• PARTY_IN_MATCH — Predicate that determines whether a given party already exists in the current match set.
• PARTY_SITE_IN_MATCH — Predicate that determines whether a given party site is already present in the match set for a search context.
• CONTACT_IN_MATCH — Predicate that determines whether a given contact is already present in the match set.
• CPT_IN_MATCH — Predicate that determines whether a given contact point is already present in the match set.
• INSERT_ADD_PARTY_SITE — Inserts a party site into HZ_MATCHED_PARTY_SITES_GT with a score of zero, but only when PARTY_SITE_IN_MATCH returns 'N'. This is the routine the user searched for; it ensures that a matching candidate is staged once and once only, avoiding duplicate rows in the global temporary table.
• INSERT_ADD_CONTACT — Parallel insertion routine for HZ_MATCHED_CONTACTS_GT, guarded by CONTACT_IN_MATCH.
• INSERT_ADD_CPT — Parallel insertion routine for HZ_MATCHED_CPTS_GT, guarded by CPT_IN_MATCH.
• IS_PTY_OBJECT_OF_REL — Function testing whether a party is the object of a specified relationship, checking HZ_RELATIONSHIPS for OBJECT_TABLE_NAME = 'HZ_PARTIES', the given object id, and DIRECTIONAL_FLAG = 'F'.
• IS_SITE_OF_PTY — Function testing whether a party site belongs to a given party.
• CONTACT_ID_FROM_REL_ID — Derives the contact identifier associated with a relationship.
• PARTY_OR_SITE_FROM_CPT — Resolves the owning party or party site for a contact point.
• REL_ID_BETW_PER_TO_ORG — Returns the relationship identifier between a person and an organization.
• RELATIONSHIP_TREATMENT, TREATMENT_PARTY_SITE, CPT_TREATMENT, CONTACT_TREATMENT — Treatment routines that apply the matching decision (such as whether a matched entity is treated as the same party, merged, or left distinct) for the respective entity types.

Tables Accessed

The package reads and writes the DQM global temporary tables HZ_MATCHED_PARTIES_GT, HZ_MATCHED_PARTY_SITES_GT, HZ_MATCHED_CONTACTS_GT, and HZ_MATCHED_CPTS_GT. These are session-scoped staging areas populated during a match run and consumed by the deduplication merge logic. It reads the base TCA tables HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, HZ_PARTY_SITES, and HZ_CONTACT_POINTS to resolve identities, ownership, and relationship directionality. All access is through APPS synonyms.

Usage Notes

ARH_DQM_TREE_HELPER is invoked internally by the DQM match and deduplication packages, most notably during customer and party matching from the Trading Community Manager and Receivables Customer Standard forms and from the matching concurrent programs. It is not a documented public API and should not be called directly from custom code; integrators should use the supported match APIs. Because the package relies on global temporary table contents scoped to a session or match context, callers must ensure an active search context (see CTXMAX) exists before invoking the insert routines.