Results for “user_defined_attribute_name”

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

Overview

HZ_ATTRIB_PRIMARY_SEC_V is a read-only dictionary view owned by the APPS schema in Oracle E-Business Suite, shipped under the Receivables (AR) product family and rooted in the Oracle Trading Community Architecture (TCA) data model. The view consolidates the configuration of matching attributes used by the Oracle Data Quality Management (DQM) and TCA party matching engine, presenting primary and secondary match attributes in a single, uniform result set. Rather than requiring consumers to query the two base configuration tables separately, the view applies a UNION that projects primary match attributes and secondary match attributes into one common column list, using sentinel values to distinguish the two categories. This makes the view particularly useful for reporting on, integrating with, and auditing the setup of duplicate-identification rules in EBS 12.1.1 and 12.2.2. The view is documented as VALID in ETRM, and its column set includes ATTRIBUTE_NAME, ENTITY_NAME, USER_DEFINED_ATTRIBUTE_NAME, MATCH_RULE_ID, ACTIVE_FLAG, SCORE, FILTER_FLAG, and DISPLAY_ORDER.

Underlying Base Objects

The view is defined over three documented referenced objects:

• HZ_MATCH_RULE_PRIMARY (referenced via synonym) — stores the primary match attributes configured for each match rule.
• HZ_MATCH_RULE_SECONDARY (referenced via synonym) — stores the secondary match attributes and their weighting scores.
• HZ_TRANS_ATTRIBUTES_VL (view) — the translatable attribute definition view, joined on ATTRIBUTE_ID to supply the attribute name, entity name, and user-defined attribute name.

Both branches of the UNION join the respective match-rule table to HZ_TRANS_ATTRIBUTES_VL on ATTRIBUTE_ID. In the primary branch, PRIMARY_ATTRIBUTE_ID is taken from the base table and SECONDARY_ATTRIBUTE_ID is set to the literal TO_NUMBER(-9999). In the secondary branch the reverse applies: SECONDARY_ATTRIBUTE_ID comes from the base table, PRIMARY_ATTRIBUTE_ID is set to -9999, and FILTER_FLAG is forced to NULL. Because the -9999 sentinel identifies which side of the match configuration a row belongs to, the view forms a denormalized presentation layer over the two underlying configuration tables.

Key Columns

• ENTITY_NAME — the TCA entity (for example, party, person, or organization) to which the attribute applies; this is the column most commonly used to filter the view.
• ATTRIBUTE_NAME — the seeded or system attribute name resolved from HZ_TRANS_ATTRIBUTES_VL.
• USER_DEFINED_ATTRIBUTE_NAME — the user-defined attribute name where the match attribute is customer-configured.
• MATCH_RULE_ID — the match rule to which the attribute belongs; joins to the match rule definition tables.
• ATTRIBUTE_ID — the underlying attribute identifier used for the join to HZ_TRANS_ATTRIBUTES_VL.
• PRIMARY_ATTRIBUTE_ID / SECONDARY_ATTRIBUTE_ID — mutually exclusive identifiers; the value -9999 indicates the attribute did not originate from that branch.
• SCORE — the weighting score, populated only for secondary attributes (NULL for primaries).
• ACTIVE_FLAG — indicates whether the match attribute is currently enabled.
• FILTER_FLAG — applicable only to primary attributes; null in the secondary branch.
• DISPLAY_ORDER — controls the sequencing of attributes in matching user interfaces.

Common Use Cases and Queries

Typical scenarios include auditing which attributes participate in a match rule, reporting active versus inactive match configuration, and exporting the match setup for data-quality analysis. To isolate primary attributes for a given entity, filter on the sentinel value:

• SELECT attribute_name, match_rule_id, active_flag, display_order FROM hz_attrib_primary_sec_v WHERE entity_name = 'PERSON' AND primary_attribute_id <> -9999 ORDER BY match_rule_id, display_order;
• SELECT attribute_name, match_rule_id, score, active_flag FROM hz_attrib_primary_sec_v WHERE entity_name = 'ORGANIZATION' AND secondary_attribute_id <> -9999 AND active_flag = 'Y' ORDER BY score DESC;
• SELECT match_rule_id, COUNT(*) FROM hz_attrib_primary_sec_v WHERE active_flag = 'Y' GROUP BY match_rule_id;

Because the view is a read-only projection, it should be used for reporting and integration rather than for direct DML; configuration changes belong in the base match-rule setup UI or APIs.