Search Results hz_thirdparty_rule




Overview
Explore in AI Chat

Overview

HZ_THIRDPARTY_RULE is a Receivables (AR) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores overwrite rules controlling how individual attributes are treated during Third Party Data Integration. The TCA (Trading Community Architecture) registry allows external and internal source systems to supply party, account, and contact data; this table determines whether a value arriving from a third-party source may replace an existing attribute value in the registry. The object is registered in the ETRM repository under owner AR with status VALID and is documented with a fixed structure of eight columns.

Mined from its foreign key topology, the heuristic Data Vault classification for this object is satellite-leaning. Under that modeling convention, HZ_THIRDPARTY_RULE would be treated as a child of the HZ_ENTITY_ATTRIBUTES hub, carrying descriptive and control attributes that qualify the parent entity rather than introducing a new business key of its own. This classification should be regarded as a modeling suggestion derived from the documented FK structure, not as an assertion about the physical design of the delivered table.

Key Information Stored

The table holds one row per attribute-overwrite rule, keyed and constrained as follows:

  • ENTITY_ATTR_ID — Part of the primary key HZ_THIRDPARTY_RULE_PK; the identifier of the entity attribute to which the rule applies. This column is a foreign key to HZ_ENTITY_ATTRIBUTES and is the principal join path to the TCA entity-attribute model.
  • ORIG_SYSTEM — Identifies the source system whose incoming data the rule governs. Together with ENTITY_ATTR_ID it forms the unique business-key candidate HZ_THIRDPARTY_RULE_U1 (ENTITY_ATTR_ID, ORIG_SYSTEM), meaning one rule per attribute per originating system.
  • OVERWRITE_FLAG — The operative business value: it indicates whether the incoming third-party value is permitted to overwrite the value already held in the registry for that attribute.
  • CREATED_BY, CREATION_DATE — Standard WHO columns recording the user and timestamp of row insertion.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification, its author, and the responsible login session.

The surrogate primary key is ENTITY_ATTR_ID as declared in HZ_THIRDPARTY_RULE_PK, while the business uniqueness is enforced across ENTITY_ATTR_ID and ORIG_SYSTEM through the HZ_THIRDPARTY_RULE_U1 unique index.

Common Use Cases and Queries

The primary operational use case is diagnosing why a value from an external source did not update the registry, or conversely why a value was overwritten unexpectedly. A typical diagnostic query resolves rules for a given attribute and source system:

  • SELECT r.entity_attr_id, r.orig_system, r.overwrite_flag FROM hz_thirdparty_rule r WHERE r.orig_system = :p_orig_system ORDER BY r.entity_attr_id;
  • A control-reporting query counts attributes whose incoming values are blocked from overwriting: SELECT orig_system, COUNT(*) FROM hz_thirdparty_rule WHERE overwrite_flag = 'N' GROUP BY orig_system;
  • A cross-reference query joins to the attribute definition for readable labels: SELECT a.*, r.overwrite_flag FROM hz_thirdparty_rule r, hz_entity_attributes a WHERE r.entity_attr_id = a.entity_attr_id;
  • Audit queries in the WHO columns identify when a rule was last changed and by whom, supporting change-control reviews before or after a data-loading cycle.

Because the rules are consulted whenever third-party data is imported, reporting on this table is most valuable to integration administrators and to functional owners of the TCA registry.

Related Objects

The following objects are the most significant dependencies identified in the documented relationship data:

  • HZ_ENTITY_ATTRIBUTES — referenced through HZ_THIRDPARTY_RULE.ENTITY_ATTR_ID = HZ_ENTITY_ATTRIBUTES.ENTITY_ATTR_ID; the parent entity-attribute definition table and the only documented foreign key relationship.
  • HZ_THIRDPARTY_RULE_PK — the primary key constraint on ENTITY_ATTR_ID.
  • HZ_THIRDPARTY_RULE_U1 — the unique index on (ENTITY_ATTR_ID, ORIG_SYSTEM) that enforces business-key uniqueness.
  • Third-party data integration and TCA bulk-import processes within the Receivables module, which read these rules to resolve overwrite behavior at load time.
  • Registry attribute-definition and setup screens that maintain the underlying HZ_ENTITY_ATTRIBUTES rows on which each rule depends.