Search Results hz_user_create_rules




Overview
Explore in AI Chat

Overview

HZ_USER_CREATE_RULES is a Receivables (AR) schema table within Oracle E-Business Suite that stores user-defined data creation rules supporting Third Party Data Integration. It forms part of the Trading Community Architecture (TCA) infrastructure, which governs how customer, party, account, and contact records are created and validated across Oracle EBS. The table defines attribute-level metadata that controls whether a given entity attribute is auto-created during integration processing.

From a dimensional modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table carries descriptive rule flags and audit columns attached to a parent entity attribute definition, which is characteristic of satellite behavior rather than a hub or link. This classification is a heuristic modeling suggestion, not a physical constraint of the EBS schema.

The object is owned by the AR schema and is documented as VALID in ETRM 12.2.2. The table contains nine documented columns and is defined by the primary key HZ_USER_CREATE_RULES_PK on (RULE_ID, ENTITY_ATTR_ID).

Key Information Stored

The column set is compact and purpose-driven. The most significant fields include:

  • RULE_ID — Part of the composite primary key; identifies the creation rule record.
  • ENTITY_ATTR_ID — Part of the composite primary key and a foreign key to HZ_ENTITY_ATTRIBUTES; links the rule to a specific entity attribute definition.
  • CREATION_FLAG — The operative business flag indicating whether the associated entity attribute should be created under third party data integration.
  • ZD_EDITION_NAME — The editioning column used to support Online Patching (ADOP) in EBS 12.2.x; it participates in the unique index HZ_USER_CREATE_RULES_U1 (RULE_ID, ENTITY_ATTR_ID, ZD_EDITION_NAME).
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last modified each rule and when.

The surrogate primary key comprises RULE_ID and ENTITY_ATTR_ID. The unique index HZ_USER_CREATE_RULES_U1 extends this pair with ZD_EDITION_NAME and represents the business-key candidate for the table, reflecting the edition-aware uniqueness enforced under EBS 12.2.2 patching. In 12.1.1 the same two-column key exists without the editioning column.

Common Use Cases and Queries

This table is typically queried during TCA integration configuration, troubleshooting of third party data loads, and audits of which entity attributes are eligible for automatic creation. A representative join to the parent attribute table is:

SELECT ucr.rule_id, ucr.entity_attr_id, ucr.creation_flag, ea.attribute_name
FROM hz_user_create_rules ucr, hz_entity_attributes ea
WHERE ucr.entity_attr_id = ea.entity_attr_id;

Analysts often filter on CREATION_FLAG to list attributes enabled for creation, and join results upward to entity definitions to determine which TCA entity (party, location, contact, account) the rule affects. Audit reporting uses LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN to trace configuration changes. Under EBS 12.2.x, queries issued through the runtime (non-editioning) view must account for ZD_EDITION_NAME resolution handled by the editioning views, while direct queries against AR.HZ_USER_CREATE_RULES expose the edition column.

Related Objects

The following objects are most significant in relation to HZ_USER_CREATE_RULES:

  • HZ_ENTITY_ATTRIBUTES — Parent table referenced by HZ_USER_CREATE_RULES.ENTITY_ATTR_ID; defines the entity attribute metadata the rules govern.
  • HZ_USER_CREATE_RULES_PK — Primary key constraint on (RULE_ID, ENTITY_ATTR_ID).
  • HZ_USER_CREATE_RULES_U1 — Unique index on (RULE_ID, ENTITY_ATTR_ID, ZD_EDITION_NAME), the edition-aware business key.
  • TCA entity definition tables (HZ_ENTITIES and related attribute mappings) — Used to trace which business entity a given rule ultimately affects.
  • TCA import and integration APIs (for example, the Customer/Party import interfaces driven by HZ_ENTITY_ATTRIBUTES) — Consume creation-rule configuration when processing third party data loads.

Join paths should consistently use ENTITY_ATTR_ID to reach HZ_ENTITY_ATTRIBUTES, as this is the only documented foreign key relationship for the table.