Search Results hz_user_overwrite_rules_u1




Overview

The AR.HZ_USER_OVERWRITE_RULES table is a reference configuration object within the Oracle E-Business Suite Trading Community Architecture (TCA) schema. It stores user overwrite rules used by Third Party Data Integration, the framework that consolidates party, party site, contact, and account records sourced from external or third-party systems. For each entity attribute, the table defines whether an end user is permitted to overwrite data residing in the single source of truth record when the originating data originates from a third-party source system.

The table resides in the APPS_TS_SEED tablespace, consistent with its role as seeded or setup-oriented configuration data rather than high-volume transactional data. Its heuristic Data Vault classification is satellite-leaning: the table primarily carries descriptive attributes (notably OVERWRITE_FLAG) tied to a composite key, which is characteristic of a satellite construct. The documented foreign key from ENTITY_ATTR_ID to HZ_ENTITY_ATTRIBUTES supports this reading, positioning the table as an attribute-level extension orbiting the entity attribute definition rather than acting as an independent hub or an intersecting link.

Key Information Stored

The documented physical schema exposes nine columns. The most significant are:

  • RULE_ID (NUMBER(15)) — the unique identifier for the overwrite rule and the leading component of the composite primary key.
  • ENTITY_ATTR_ID (NUMBER(15)) — the entity attribute identifier against which the rule is defined; this column is also the documented foreign key to HZ_ENTITY_ATTRIBUTES and the second component of the primary key.
  • ORIG_SYSTEM (VARCHAR2(30)) — the source system from which users may overwrite data, scoping the rule to a specific third-party origin.
  • OVERWRITE_FLAG (VARCHAR2) — the operative control value indicating whether the user may overwrite the corresponding data element.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing row creation and last-update provenance, with CREATED_BY and LAST_UPDATED_BY referencing FND_USER.USER_ID and LAST_UPDATE_LOGIN referencing FND_LOGINS.LOGIN_ID.

The surrogate primary key is HZ_USER_OVERWRITE_RULES_PK, defined on (RULE_ID, ENTITY_ATTR_ID). The documented unique index HZ_USER_OVERWRITE_RULES_U1 spans (RULE_ID, ENTITY_ATTR_ID, ORIG_SYSTEM), making this triple the business-key candidate that enforces uniqueness of a rule per attribute per originating system.

Common Use Cases and Queries

Typical usage centers on auditing and reporting which attributes users may override for third-party sourced data, and on validating integration behavior during data loads.

  • Listing rules for a given source system:
    SELECT r.RULE_ID, r.ENTITY_ATTR_ID, r.OVERWRITE_FLAG FROM AR.HZ_USER_OVERWRITE_RULES r WHERE r.ORIG_SYSTEM = :orig_system;
  • Joining to attribute definitions to translate ENTITY_ATTR_ID into a readable attribute name for security or governance reporting.
  • Audit trailing: filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recently modified overwrite policies.
  • Integration diagnostics: confirming whether a control is present before a user attempts to override imported third-party data.

Related Objects

  • AR.HZ_ENTITY_ATTRIBUTES — referenced via ENTITY_ATTR_ID; defines the entity attributes the rules govern.
  • AR.HZ_USER_OVERWRITE_RULES# — the underlying dependent object referenced by this table.
  • FND_USER — joined through CREATED_BY and LAST_UPDATED_BY for user identity.
  • FND_LOGINS — joined through LAST_UPDATE_LOGIN for session provenance.
  • Additional TCA objects in the HZ_ENTITY_ATTRIBUTES and Third Party Data Integration family that consume overwrite-flag decisions during party data maintenance.