Search Results hz_entity_attributes




Overview
Explore in AI Chat

Overview

HZ_ENTITY_ATTRIBUTES is a Receivables (AR) schema table that stores entity and attribute metadata consumed by Oracle's Third Party Data Integration framework. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the central registry of entity-attribute pairs that govern how third-party data is selected, transformed, matched, and written into the Trading Community Architecture (TCA) model. Each row defines a discrete combination of a business entity (such as a party, account, or contact) and an attribute name, and acts as the anchor point for downstream rules and configuration that reference that specific pair.

Because multiple dependent tables — including data source selections, exception lists, and create/overwrite rules — resolve their foreign keys back to ENTITY_ATTR_ID, the table functions as a lookup or reference hub. In Data Vault terms, mining the foreign-key structure suggests treating HZ_ENTITY_ATTRIBUTES as a hub, with each dependent table representing a satellite or link that carries descriptive, rule-specific, or temporal context around the hub key.

Key Information Stored

Of the 17 documented columns, the most operationally significant are:

  • ENTITY_ATTR_ID — The surrogate primary key (HZ_ENTITY_ATTRIBUTES_PK) that uniquely identifies every entity-attribute row and is the column carried by all child foreign keys. It is also the first component of unique index HZ_ENTITY_ATTRIBUTES_U1.
  • ENTITY_NAME — The business entity being described (for example, a party or account object). Combined with ATTRIBUTE_NAME, it forms the business-key candidate captured by unique index HZ_ENTITY_ATTRIBUTES_U2.
  • ATTRIBUTE_NAME — The specific attribute that belongs to the entity; together with ENTITY_NAME it identifies the attribute in business terms.
  • ATTRIBUTE_GROUP_NAME — A grouping label used to organize related attributes for presentation and rule configuration.
  • UPDATED_FLAG — Indicates whether the attribute definition has been updated, supporting incremental processing in the integration pipeline.
  • CREATED_BY_MODULE and APPLICATION_ID — Identify the owning module and application that produced the row.
  • ZD_EDITION_NAME — The editioning column introduced in the 12.2 architecture, included in both unique indexes so that rows are version-scoped by edition.

The remaining documented columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are standard WHO/audit and concurrent-program columns that provide traceability for every insert and update.

Common Use Cases and Queries

Typical scenarios include auditing the set of entity-attribute definitions available in an instance, identifying which attributes have pending updates, and tracing which rules and data sources reference a given attribute. A representative query lists the business keys:

  • SELECT ENTITY_ATTR_ID, ENTITY_NAME, ATTRIBUTE_NAME, ATTRIBUTE_GROUP_NAME, UPDATED_FLAG FROM AR.HZ_ENTITY_ATTRIBUTES WHERE UPDATED_FLAG = 'Y';
  • To find unprocessed attributes, filter on UPDATED_FLAG and CREATION_DATE or LAST_UPDATE_DATE ranges during an integration run.
  • To determine rule coverage, join to the dependent rule tables on ENTITY_ATTR_ID (see Related Objects) and group by ENTITY_NAME and ATTRIBUTE_NAME.
  • For currency of definitions, order by LAST_UPDATE_DATE and inspect LAST_UPDATED_BY, REQUEST_ID, and PROGRAM_ID to attribute changes to a specific concurrent request.

Related Objects

Six documented tables carry ENTITY_ATTR_ID as a foreign key to HZ_ENTITY_ATTRIBUTES, making them the principal dependents:

Queries joining HZ_ENTITY_ATTRIBUTES to these tables on ENTITY_ATTR_ID provide a complete view of how each entity-attribute pair is sourced, governed, and excepted within the Third Party Data Integration flow.