Search Results hz_thirdparty_exceps_pk

Overview

HZ_THIRDPARTY_EXCEPS is a Receivables (AR) module table in the Oracle E-Business Suite TCA (Trading Community Architecture) schema. Within Oracle EBS 12.1.1 and 12.2.2, it stores exception records that override the default overwrite rules applied during Third Party Data Integration. When external data providers supply attribute values for parties, TCA normally applies standard precedence and overwrite logic to determine whether an incoming value should replace the existing party attribute. This table allows administrators to define party-specific and attribute-specific exceptions to that logic, ensuring that authoritative or protected values are preserved even when the standard rules would otherwise permit an overwrite.

From a Data Vault modeling perspective, the heuristic classification for this object is a link. The structure resolves a many-to-many association between parties and entity attributes, which is consistent with how link tables are typically modeled. This classification is offered as a modeling suggestion rather than a documented fact.

Key Information Stored

The table is documented with seven physical columns, of which the two most significant form the primary key and define the business meaning of each row.

• PARTY_ID — Identifies the specific party (person or organization) to which the exception applies. This is a foreign key to HZ_PARTIES and is part of the composite primary key.
• ENTITY_ATTR_ID — Identifies the specific entity attribute governed by the exception. This is a foreign key to HZ_ENTITY_ATTRIBUTES and is the second component of the composite primary key.
• CREATED_BY, CREATION_DATE — Standard WHO columns capturing the user and timestamp of row creation, useful for auditing when an exception was introduced.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns capturing the identity, session, and timing of the most recent modification, supporting change auditing and troubleshooting.

The surrogate/natural composite primary key is enforced by HZ_THIRDPARTY_EXCEPS_PK, comprising (PARTY_ID, ENTITY_ATTR_ID). The unique index HZ_THIRDPARTY_EXCEPS_U1 on the same column pair is a documented business-key candidate, confirming that only one exception record may exist per party per attribute.

Common Use Cases and Queries

A primary scenario is confirming which attributes are protected from overwrite for a given party during data integration runs. Queries commonly join this table to HZ_PARTIES and HZ_ENTITY_ATTRIBUTES to translate the identifiers into human-readable names.

• Listing all exceptions for a specific party:

SELECT e.party_id, e.entity_attr_id, ea.attribute_name
FROM   hz_thirdparty_exceps e,
       hz_entity_attributes ea
WHERE  e.entity_attr_id = ea.entity_attr_id
AND    e.party_id = :p_party_id;

• Auditing recently created or modified exceptions using the WHO columns:
• Verifying that no duplicate exception exists for a party/attribute combination before inserting.
• Reporting on the aggregate count of exceptions per entity attribute to identify attributes that frequently require manual protection.

These queries support data stewards who must reconcile conflicting values between an external provider and the master party record.

Related Objects

The following objects are most significant in relation to HZ_THIRDPARTY_EXCEPS, based on the documented foreign keys and TCA integration design.

• HZ_PARTIES — referenced via HZ_THIRDPARTY_EXCEPS.PARTY_ID; the master party entity.
• HZ_ENTITY_ATTRIBUTES — referenced via HZ_THIRDPARTY_EXCEPS.ENTITY_ATTR_ID; defines the attribute metadata.
• HZ_ENTITY_ATTRIBUTE_VALUES or similar attribute-value tables — hold the actual party attribute data whose overwrite behavior these exceptions govern.
• HZ_PARTY_ORIG_SYSTEMS and source/overwrite rule configuration tables — participate in the third party data integration precedence logic.
• TCA integration and party maintenance APIs — the runtime processes that consult these exception records when applying overwrite decisions.

Correct maintenance of this table is essential for organizations relying on Third Party Data Integration, as incorrect exception data can either block legitimate updates or permit unwanted overwrites of authoritative party attributes.