Search Results hz_user_create_rules_u1

Overview

The AR.HZ_USER_CREATE_RULES table is a seed data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model, owned by the AR schema and registered under the FND Design Data as AR.HZ_USER_CREATE_RULES. It stores configuration rules that govern user data creation in the context of Third Party Data Integration. Specifically, for each "Other" entity defined in the Trading Community Architecture (TCA), the table determines whether an end user is permitted to manually create user-entered records. The rule is expressed through a creation flag paired with an entity attribute identifier, allowing TCA consumers to enforce consistent data governance across parties, sites, contacts, and related entities.

The table resides in the APPS_TS_SEED tablespace, characteristic of seed and reference data rather than high-volume transactional data. Heuristically, the mined relationship structure classifies this table as satellite-leaning: it carries descriptive rule attributes (the creation flag) keyed by a composite identifier that resolves to a parent entity attribute. In a Data Vault modeling sense, this suggests a satellite attached to a hub or link representing the entity attribute dimension, rather than an independent hub.

Key Information Stored

The table comprises nine documented columns. The most significant are described below.

• RULE_ID (NUMBER, 15) — Unique identifier for the creation rule. Part of the composite primary key and the unique index.
• ENTITY_ATTR_ID (NUMBER, 15) — Foreign key to HZ_ENTITY_ATTRIBUTES; identifies the entity attribute to which the rule applies. Also a constituent of the primary key.
• CREATION_FLAG (VARCHAR2) — The operative business flag indicating whether user-entered record creation is allowed for the associated entity attribute.
• ZD_EDITION_NAME (VARCHAR2, 30) — Editioning column supporting Oracle EBS 12.2 online patching (edition-based redefinition); part of the unique index.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "WHO" audit columns tracking row provenance and change history.

The surrogate/business primary key is HZ_USER_CREATE_RULES_PK (RULE_ID, ENTITY_ATTR_ID), while the business-key candidate captured by the unique index is HZ_USER_CREATE_RULES_U1 (RULE_ID, ENTITY_ATTR_ID, ZD_EDITION_NAME) — the edition column included to satisfy 12.2 editioning semantics.

Common Use Cases and Queries

This table is typically queried to audit or troubleshoot TCA data governance in Third Party Data Integration. Analysts and administrators use it to verify which entities permit manual user creation.

Retrieve all rules with their audit context:

SELECT RULE_ID, ENTITY_ATTR_ID, CREATION_FLAG,
       CREATED_BY, CREATION_DATE,
       LAST_UPDATED_BY, LAST_UPDATE_DATE, ZD_EDITION_NAME
FROM   AR.HZ_USER_CREATE_RULES;

Identify entities where user creation is disabled:

SELECT ENTITY_ATTR_ID, CREATION_FLAG
FROM   AR.HZ_USER_CREATE_RULES
WHERE  CREATION_FLAG = 'N';

Join to the entity attribute definition to resolve the entity name:

SELECT ucr.RULE_ID, ea.ENTITY_ATTR_ID, ucr.CREATION_FLAG
FROM   AR.HZ_USER_CREATE_RULES ucr,
       AR.HZ_ENTITY_ATTRIBUTES ea
WHERE  ucr.ENTITY_ATTR_ID = ea.ENTITY_ATTR_ID;

Because the data is seed-oriented, reporting scenarios emphasize configuration validation and post-upgrade/migration verification rather than transaction volume analysis.

Related Objects

The following objects are most significant in the dependency and join model:

• AR.HZ_ENTITY_ATTRIBUTES — Referenced by the foreign key ENTITY_ATTR_ID; the primary parent for rule resolution.
• AR.HZ_USER_CREATE_RULES# — The editioning view/underlying object variant that references this table in 12.2.
• FND_USER — Source of the standard WHO columns CREATED_BY and LAST_UPDATED_BY via USER_ID.
• FND_LOGINS — Source of LAST_UPDATE_LOGIN via LOGIN_ID.
• TCA / Trading Community Architecture party, site, and contact entity definitions consumed by Third Party Data Integration, which read these creation rules to enforce data entry restrictions.