Results for “hz_match_rules_vl”

50+ results




Overview
Explore in AI Chat

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

Overview

HZ_MATCH_RULES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Receivables (AR) product family and sits within the Trading Community Architecture (TCA) data model, exposing the match rule definitions that Oracle uses to identify and score potential duplicate parties, customers, and contacts. Match rules are the configurable criteria — name, address, tax identifiers, and other attributes — against which the customer data cleansing and deduplication engines compare records during a merge or duplicate identification process.

Technically, the object is a "VL" (view with language) variant. Rather than storing translatable attributes in a single table, the view joins the language-independent base table to its translation table and filters on the session language. This makes HZ_MATCH_RULES_VL the standard reporting and integration entry point for match rule data, returning one row per rule in the language of the current user session. Because it is a view, it is not directly updatable in the conventional sense; the underlying base tables must be used for DML. The view is primarily consumed by concurrent programs, the Oracle Data Librarian (deduplication) APIs, and custom reports or interfaces that need to read match rule configuration.

Underlying Base Objects

Per the documented ETRM metadata, HZ_MATCH_RULES_VL is defined over two referenced base objects, both accessed through APPS synonyms:

  • HZ_MATCH_RULES_B — the base ("B") table holding match rule definitions that are independent of language, including scoring thresholds, flags, and the match rule type.
  • HZ_MATCH_RULES_TL — the translation ("TL") table holding the language-dependent descriptive columns, RULE_NAME and DESCRIPTION.

The view definition joins the two objects on MATCH_RULE_ID and constrains HZ_MATCH_RULES_TL.LANGUAGE to USERENV('LANG'), so only translations matching the session language are returned. The join is a standard TCA master/detail pattern. Note that HZ_MATCH_RULES_B is the authoritative source for identifiers and numeric scoring values, while all human-readable text comes from the TL table.

Key Columns

  • MATCH_RULE_ID — the primary identifier of the match rule and the join key between the base and translation tables. This is the column referenced by the search term "match_rule_id".
  • RULE_NAME — the user-visible name of the rule, sourced from the translation table.
  • DESCRIPTION — the user-visible description of the rule, also from the translation table.
  • RULE_PURPOSE — indicates the purpose for which the rule is intended (for example, deduplication of parties or contacts).
  • ACTIVE_FLAG — indicates whether the rule is currently enabled.
  • MATCH_ALL_FLAG — controls whether all criteria must be satisfied for a match.
  • COMPILATION_FLAG — marks whether the rule has been compiled for use by the matching engine.
  • MATCH_SCORE, NO_OVERRIDE_SCORE, AUTO_MERGE_SCORE — numeric thresholds governing match acceptance, manual override approval, and automatic merge decisions.
  • AUTOMERGE_FLAG — indicates whether matching records may be merged automatically.
  • MATCH_RULE_TYPE — classifies the rule by matching methodology.
  • USE_CONTACT_ADDR_FLAG, USE_CONTACT_CPT_FLAG — determine whether contact address and contact point data participate in the match.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, LAST_UPDATED_BY, and OBJECT_VERSION_NUMBER provide standard who-column auditing and optimistic locking support.

Common Use Cases and Queries

Typical uses include auditing active match rules, reporting scoring thresholds to business users, and feeding rule identifiers into deduplication batch processes.

List active rules and their thresholds:

SELECT match_rule_id, rule_name, match_score,
       no_override_score, auto_merge_score
  FROM apps.hz_match_rules_vl
 WHERE active_flag = 'Y'
 ORDER BY rule_name;

Retrieve a specific rule by the searched identifier:

SELECT match_rule_id, rule_name, description, match_rule_type
  FROM apps.hz_match_rules_vl
 WHERE match_rule_id = :p_match_rule_id;

Identify rules eligible for automatic merge:

SELECT match_rule_id, rule_name, auto_merge_score
  FROM apps.hz_match_rules_vl
 WHERE automerge_flag = 'Y'
   AND compilation_flag = 'Y';

Join to the base table when language-independent attributes are required:

SELECT v.rule_name, b.match_rule_type, b.object_version_number
  FROM apps.hz_match_rules_vl v,
       apps.hz_match_rules_b  b
 WHERE v.match_rule_id = b.match_rule_id;