Results for “content_source_type”

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

Overview

HZ_WIN_SOURCE_EXCEPS is a transaction-detail table owned by the AR (Receivables) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores attribute exception information recorded when data values are overwritten in a manner contrary to the Third Party Data Integration (TPDI) data source ranking. In the TPDI model, each attribute of a party record is governed by a ranked list of content sources; the highest-ranked source is normally permitted to win. When an update originates from a lower-ranked source and still overwrites the surviving value, the system preserves an exception record in this table so that the deviation from the ranking rules is auditable and reportable.

Within the Oracle Trading Community Architecture (TCA) data model, HZ_WIN_SOURCE_EXCEPS functions as an exception log keyed to both a party and a specific entity attribute. Heuristically, the FK structure (composite primary key of PARTY_ID and ENTITY_ATTR_ID, with each column resolving to a parent entity) suggests a Data Vault link classification — a relationship record connecting a party to an attribute rather than a standalone hub or descriptive satellite. This classification is a modeling suggestion; the table's own columns also carry audit and descriptive payload, so it can be treated as a link with satelitte-like attributes.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• PARTY_ID — the party (organization, person, or group) whose attribute was affected. Part of the composite primary key and an FK to HZ_PARTIES.
• ENTITY_ATTR_ID — the specific entity attribute definition involved. Part of the composite primary key and an FK to HZ_ENTITY_ATTRIBUTES.
• CONTENT_SOURCE_TYPE — identifies the content source type associated with the overwriting or winning value, supporting reconciliation against the TPDI ranking configuration.
• EXCEPTION_TYPE — categorizes the nature of the ranking violation, allowing consumers to distinguish exception classes.
• CREATED_BY, CREATION_DATE — standard WHO columns recording who created the exception row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent modification and session.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the batch or program that generated or last touched the row.

The surrogate primary key is HZ_WIN_SOURCE_EXCEPS_PK (PARTY_ID, ENTITY_ATTR_ID). A unique index, HZ_WIN_SOURCE_EXCEPS_U1, covers the same two business-key candidates, confirming that a party/attribute pair is unique within the exception set. Note that the primary key is composite and business-meaningful rather than a generated surrogate.

Common Use Cases and Queries

Typical uses include auditing TPDI merges and cleanses, diagnosing why a party attribute reflects a value from a lower-ranked source, and reporting on data-governance exceptions. A sample query lists exceptions for a party:

SELECT e.party_id, e.entity_attr_id, e.content_source_type,
       e.exception_type, e.creation_date
FROM   hz_win_source_exceps e
WHERE  e.party_id = :p_party_id
ORDER BY e.creation_date DESC;

Joining to HZ_PARTIES and HZ_ENTITY_ATTRIBUTES resolves human-readable context, and filtering by PROGRAM_ID or REQUEST_ID isolates exceptions produced by a specific batch, which is useful when investigating a Third Party Data Integration load run.

Related Objects

• HZ_PARTIES — parent of PARTY_ID; provides party name, party number, and party type.
• HZ_ENTITY_ATTRIBUTES — parent of ENTITY_ATTR_ID; defines the attribute and related metadata.
• HZ_ENTITY_ATTRIBUTES_B and HZ_ENTITY_ATTRIBUTES_TL — base and translation views for attribute definitions.
• HZ_PARTY_SITES and HZ_LOCATIONS — related party-data entities frequently involved in TPDI source ranking conflicts.
• HZ_ORG_CONTACTS / HZ_PERSON_PROFILES — other TCA entities whose attributes participate in the same ranking framework.
• TPDI concurrent programs (e.g., Third Party Data Integration imports) — generators of the REQUEST_ID/PROGRAM_ID context.

Together these relationships make HZ_WIN_SOURCE_EXCEPS a focused audit trail for TCA party-attribute data governance.