Results for “hz_thirdparty_rule_u1”

8 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AR.HZ_THIRDPARTY_RULE table is a seed data table within the Oracle E-Business Suite Trading Community Architecture (TCA). It stores the configuration of third-party overwrite rules used by the Third Party Integration feature. The Third Party Integration framework allows external systems to feed data into the TCA registry, and the rules held in this table govern whether data originating from a specific external source system is permitted to overwrite data that a user has already entered manually into the single source of truth record. Importantly, the rules apply only to user-entered data that had previously overwritten third-party data — that is, they arbitrate the resolution of conflicts between a source system and manual user input on an entity attribute.

The table resides in the APPS_TS_SEED tablespace, consistent with a reference or seeded configuration object rather than a high-volume transactional entity. It carries eight documented columns and is owned by the AR schema, with FND design data registered as AR.HZ_THIRDPARTY_RULE. Under the heuristic Data Vault classification derived from its foreign key structure, the object is satellite-leaning, suggesting it is best modeled as a descriptive satellite that records attribute-level state keyed to a parent entity rather than as a true hub or link. In practice it behaves as a configuration satellite describing overwrite behavior for each entity attribute, ordered by originating system.

Key Information Stored

The table's business content is compact, and the most significant columns are as follows:

  • ENTITY_ATTR_ID — a mandatory numeric (15) identifier for the entity attribute to which the rule applies. This column is documented as the primary key column of HZ_THIRDPARTY_RULE_PK and also participates in the unique index HZ_THIRDPARTY_RULE_U1.
  • ORIG_SYSTEM — a VARCHAR2(30) value naming the source system that may overwrite user-entered data. It is the second column of the unique business-key index HZ_THIRDPARTY_RULE_U1, meaning that the combination of entity attribute and originating system uniquely defines a rule.
  • OVERWRITE_FLAG — a VARCHAR2 flag that encodes the actual overwrite behavior, determining whether third-party data from the named origin system is allowed to overwrite the applicable user-entered value.

The remaining columns are the standard Oracle EBS "who" audit columns: CREATED_BY and LAST_UPDATED_BY (foreign keys to FND_USER.USER_ID), CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN (a foreign key to FND_LOGINS.LOGIN_ID). Segmenting surrogate versus business keys, the surrogate primary key is ENTITY_ATTR_ID, whereas the documented business-key candidate is the composite unique index HZ_THIRDPARTY_RULE_U1 (ENTITY_ATTR_ID, ORIG_SYSTEM).

Common Use Cases and Queries

Typical uses include auditing which source systems are permitted to overwrite manual user input for a given attribute, troubleshooting why incoming third-party data fails to update the TCA registry, and extracting configuration for compliance or environment comparison. Because the table is keyed by attribute and origin system, joins to HZ_ENTITY_ATTRIBUTES on ENTITY_ATTR_ID are the dominant pattern.

A representative query listing rules with their originating system:

SELECT ENTITY_ATTR_ID, OVERWRITE_FLAG, ORIG_SYSTEM
FROM   AR.HZ_THIRDPARTY_RULE
ORDER  BY ENTITY_ATTR_ID, ORIG_SYSTEM;

A query resolving rules to attribute descriptions joins HZ_ENTITY_ATTRIBUTES on ENTITY_ATTR_ID and filters by a specific origin system. Auditing of change history is supported by LAST_UPDATED_BY and LAST_UPDATE_DATE.

Related Objects

The documented dependency data shows that HZ_THIRDPARTY_RULE does not reference any database object, but it is referenced by the HZ_THIRDPARTY_RULE# object in the AR schema. Its principal foreign key targets HZ_ENTITY_ATTRIBUTES on ENTITY_ATTR_ID. The most significant related objects are therefore:

  • AR.HZ_ENTITY_ATTRIBUTES — joined via ENTITY_ATTR_ID; supplies the attribute definition that each rule governs.
  • AR.HZ_THIRDPARTY_RULE# — the associated dependent object documented as referencing this table.
  • FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY for audit attribution.
  • FND_LOGINS — referenced by LAST_UPDATE_LOGIN to identify the operating system login of the last updater.
  • TCA third-party integration packages and the TCA registry APIs that evaluate overwrite rules during inbound data processing.

Because the FK targeting HZ_ENTITY_ATTRIBUTES is the only documented outbound relationship, other TCA entity and source-system tables influence behavior indirectly through the integration layer rather than through direct declarative constraints.