Search Results hz_entity_attributes_u1

Overview

The HZ_ENTITY_ATTRIBUTES table resides in the AR schema of the Oracle E-Business Suite TCA (Trading Community Architecture) registry and is deployed in both release 12.1.1 and 12.2.2. It stores the master configuration of entities and attributes that participate in the Third Party Data Integration setup, which governs how external data sources such as Dun & Bradstreet (D&B) populate the TCA registry. Each row represents one entity/attribute pairing available for third-party enrichment, together with administrative flags and standard WHO audit columns. All D&B related entities and attributes are seeded at installation, and the table is stored in the APPS_TS_SEED tablespace with a PCT Free of 10, reflecting its low-volatility, reference-data character.

From a dimensional modeling perspective, the mined relationship structure suggests classifying HZ_ENTITY_ATTRIBUTES as a hub: it is referenced by six dependent tables through the ENTITY_ATTR_ID foreign key, and it defines the canonical business identities (entity name plus attribute name) around which downstream integration rules and exceptions are organized.

Key Information Stored

The table contains 17 documented columns. The most significant are:

• ENTITY_ATTR_ID — Sequence-generated numeric (15) surrogate primary key; the target of every inbound foreign key.
• ENTITY_NAME — VARCHAR2(30) name of the entity for data source setup, drawn from the ENTITY_NAME lookup type.
• ATTRIBUTE_NAME — VARCHAR2(30) attribute identifier, related to HZ_PERSON_PROFILES lookup types.
• ATTRIBUTE_GROUP_NAME — VARCHAR2(30) grouping used to organize attributes for data source setup.
• UPDATED_FLAG — Indicates whether the attribute setup changed since the last run of the Third Party Data Integration Update (Y = updated, N = unchanged).
• CREATED_BY_MODULE — VARCHAR2(150) identifying the source application module that created the record.
• APPLICATION_ID — Foreign key to FND_APPLICATION identifying the owning application.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program request context columns.
• ZD_EDITION_NAME — Editioning column supporting online patching in 12.2.x.

Two unique indexes function as business-key candidates. HZ_ENTITY_ATTRIBUTES_U1 covers (ENTITY_ATTR_ID, ZD_EDITION_NAME) and reinforces the surrogate key, while HZ_ENTITY_ATTRIBUTES_U2 covers (ENTITY_NAME, ATTRIBUTE_NAME, ZD_EDITION_NAME), establishing the natural business key that guarantees each entity/attribute combination is defined only once. The primary key constraint is HZ_ENTITY_ATTRIBUTES_PK on ENTITY_ATTR_ID.

Common Use Cases and Queries

Typical activity centers on configuration review and dependency analysis before integration runs. A common query lists all attributes for a given entity:

SELECT entity_attr_id, entity_name, attribute_name, attribute_group_name
FROM   hz_entity_attributes
WHERE  entity_name = :p_entity_name;

Administrators identify configuration pending propagation to the integration engine by filtering on the update flag:

SELECT entity_attr_id, entity_name, attribute_name
FROM   hz_entity_attributes
WHERE  updated_flag = 'Y';

Oracle Trading Community Architecture reports and the Third Party Data Integration concurrent programs reference this table to determine which TCA columns may be overwritten by purchased or externally sourced data. Impact analysis before disabling an attribute should join the dependent rule and exception tables to confirm no active rules reference the ENTITY_ATTR_ID.

Related Objects

Six documented tables reference HZ_ENTITY_ATTRIBUTES through ENTITY_ATTR_ID, each providing a distinct layer of integration control:

• HZ_SELECT_DATA_SOURCES — Defines the data sources authorized to populate a given entity attribute.
• HZ_THIRDPARTY_RULE — Third-party processing rules applied per entity attribute.
• HZ_THIRDPARTY_EXCEPS — Exceptions to the third-party integration rules.
• HZ_USER_CREATE_RULES — User-defined rules controlling creation of attribute values.
• HZ_USER_OVERWRITE_RULES — User-defined rules controlling overwriting of existing values.
• HZ_WIN_SOURCE_EXCEPS — Source-priority exceptions governing which data source wins.

Together these objects form the configuration backbone of TCA third-party data integration and should be treated as a single logical unit during migration, cloning, and diagnostic review.