Search Results p_ctx_id

Overview

ARH_DQM_CUST_HELPER is an Oracle E-Business Suite PL/SQL package body owned by APPS and classified as OTHER. It belongs to the Oracle Receivables (AR) module and, more specifically, to the Data Quality Management (DQM) infrastructure that supports customer and party deduplication, matching, and cleansing within Oracle Customers Online / Trading Community Architecture (TCA). The package name prefix "ARH_DQM" indicates that it operates on the receivables customer model (HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES) combined with the DQM matching results held in the HZ_MATCHED_* global temporary tables.

The package provides helper functions and procedures that determine whether customers, customer account roles, account sites, and party relationships already exist in a given matching context (search_context_id), and that compute or apply scoring and treatment logic for those relationships. The header revision "$Header: ARHDQMAB.pls 115.4 2002/05/31" shows that the source is a long-standing, stable component of the TCA/DQM stack that is still shipped in EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents 16 procedures and functions. The principal members include:

• IS_CUST_ROLE_REL_DQM_PTY — Returns 'Y' if a given customer account role is related to a matched party in the specified search context; otherwise 'N'. It provides the core existence check for role-to-party relationships during matching.
• IS_CUST_ACCT_IN_PTY_GT — Determines whether a customer account already appears in HZ_MATCHED_PARTIES_GT for the search context.
• IS_CUST_ROLE_IN_CT_GT — Returns 'Y' if a customer account role is already inserted into HZ_MATCHED_CONTACTS_GT; otherwise 'N'.
• IS_ACCT_SITE_IN_PS_GT, IS_AS_REL_DQM_PTY, IS_AS_REL_PS_IN_PS_GT — Site-level existence checks against HZ_MATCHED_PARTY_SITES_GT and related matched party data.
• SCORE_OF_REL_PS, SCORE_REL_PARTY — Compute or retrieve match scores for party sites and party relationships used in ranking candidate matches.
• INS_AS_IN_PS_GT, INS_CA_CAR_IN_GT — Insert account sites and customer account/role records into the appropriate HZ_MATCHED_* global temporary tables.
• FIND_AS_REL_PS, FIND_ALL_ACCOUNT_FOR_PARTY — Lookup helpers that locate related party sites and all accounts belonging to a party.
• AS_PS_TREATMENT, AC_PTY_TREATMENT, CAR_OC_TREATMENT, IS_AC_REL_PTY_IN_P_GT — Apply the post-matching "treatment" decisions (such as automatic merge, review, or discard) for account sites, account-to-party links, customer account roles with organization contacts, and account relationship parties.

Tables Accessed

The package reads and writes the standard TCA customer and matching tables through APPS synonyms. Customer data comes from HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_PARTIES, HZ_PARTY_SITES, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS and HZ_RELATIONSHIPS. Match results are staged in the global temporary tables HZ_MATCHED_PARTIES_GT, HZ_MATCHED_CONTACTS_GT, HZ_MATCHED_CPTS_GT and HZ_MATCHED_PARTY_SITES_GT. The existence-check functions query these matched tables against HZ_CUST_ACCOUNTS and HZ_CUST_ACCOUNT_ROLES, filtered by SEARCH_CONTEXT_ID, to establish whether a customer entity has already been processed.

Usage Notes

ARH_DQM_CUST_HELPER is invoked internally by the DQM matching and deduplication engine during customer matching runs rather than by end users. It is referenced by one other package in the EBS code base, which orchestrates the matching flow. Typical invocation paths include Oracle Customers Online match/merge processing and concurrent programs that populate the HZ_MATCHED_* global temporary tables and subsequently decide the treatment of matched customer records. Because the functions expose parameters such as p_ctx_id, p_cust_account_id, p_cust_account_role_id and p_status, custom code extending customer deduplication can call them to test membership of an entity within a search context; the p_status parameter in particular accepts 'ALL' or an account status value and is applied through a DECODE on NVL(car.status,'A'). Such calls should generally be confined to the matching session, since the global temporary tables hold context-specific session data.