Search Results hz_select_data_sources




Overview

HZ_SELECT_DATA_SOURCES is a Receivables (AR) module table that records the selected data sources used for Third Party Data Integration within Oracle E-Business Suite 12.1.1 and 12.2.2. It sits within the Trading Community Architecture (TCA) / HZ schema family and governs which external content sources have been enabled, ranked, and associated with a given entity attribute. Entities refer to TCA parties, organizations, persons, or locations, and this table determines where enriched content (such as third-party data provider feeds) is drawn from and how those sources are prioritized.

The table is owned by the AR schema and is reported as VALID in ETRM. Based purely on the heuristic Data Vault classification mined from its foreign-key structure, this object is satellite-leaning: its grain is defined by the composite of ENTITY_ATTR_ID and CONTENT_SOURCE_TYPE, and it depends on a parent hub-like entity (HZ_ENTITY_ATTRIBUTES). This classification is offered as a modeling suggestion rather than a documented fact, but it reflects the table's role as a descriptive, attribute-bearing detail store rather than an independent entity hub or a pure associative link.

Key Information Stored

HZ_SELECT_DATA_SOURCES contains 13 documented columns. The most significant are summarized below.

  • ENTITY_ATTR_ID — Identifier linking the row to an entry in HZ_ENTITY_ATTRIBUTES. This column participates in both the primary key and the foreign key to HZ_ENTITY_ATTRIBUTES, and is the primary parent reference of the row.
  • CONTENT_SOURCE_TYPE — Classifies the type of third-party content source being selected. Together with ENTITY_ATTR_ID it forms the primary key, meaning each entity attribute can select at most one row per content source type.
  • RANKING — Ordinal value expressing the priority order of the selected source relative to others for the same entity attribute. This supports deterministic source preference when multiple providers are available.
  • ZD_EDITION_NAME — Editioning column supporting the E-Business Suite Online Patching / Edition-Based Redefinition (EBR) model introduced in 12.2. This column appears in the unique index HZ_SELECT_DATA_SOURCES_U1.
  • Audit columnsCREATED_BY, CREATION_DATE, LAST_UPDATED_BY and LAST_UPDATE_DATE provide standard who-column audit trail.
  • Concurrent request columnsREQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and LAST_UPDATE_LOGIN identify the concurrent program and request that inserted or modified the record.

Regarding keys: the documented physical primary key is HZ_SELECT_DATA_SOURCES_PK over (ENTITY_ATTR_ID, CONTENT_SOURCE_TYPE). A separate unique index, HZ_SELECT_DATA_SOURCES_U1, spans (ENTITY_ATTR_ID, CONTENT_SOURCE_TYPE, ZD_EDITION_NAME) and is best treated as a business-key candidate, since it adds the editioning discriminator used by the 12.2 runtime.

Common Use Cases and Queries

Typical scenarios include diagnosing why a party's enrichment data is not appearing, auditing which providers are configured for an attribute, and reporting on source ranking. A representative query joins the parent attribute table to retrieve attribute context alongside the selected sources:

  • SELECT s.ENTITY_ATTR_ID, s.CONTENT_SOURCE_TYPE, s.RANKING, a.ATTRIBUTE_NAME FROM HZ_SELECT_DATA_SOURCES s, HZ_ENTITY_ATTRIBUTES a WHERE s.ENTITY_ATTR_ID = a.ENTITY_ATTR_ID ORDER BY s.ENTITY_ATTR_ID, s.RANKING;
  • Filter on CONTENT_SOURCE_TYPE to inspect a single provider type across all attributes.
  • Group by CONTENT_SOURCE_TYPE and count distinct ENTITY_ATTR_ID to measure provider coverage.
  • Join to the concurrent request columns to trace which batch or program configured the sources.

In 12.2 environments, queries should generally filter on ZD_EDITION_NAME (or rely on the editioning view) to return only the active edition's rows, avoiding duplicate results across editions.

Related Objects

  • HZ_ENTITY_ATTRIBUTES — Parent table referenced by the foreign key HZ_SELECT_DATA_SOURCES.ENTITY_ATTR_ID → HZ_ENTITY_ATTRIBUTES. This is the single documented FK and the most important join partner.
  • HZ_PARTIES / HZ_PARTY_SITES — TCA entities whose attributes are ultimately enriched by the selected data sources.
  • HZ_ENTITY_ATTRIBUTES and associated attribute configuration views — define the attribute metadata that the ENTITY_ATTR_ID points to.
  • TCA / HZ integration APIs and concurrent programs — the Third Party Data Integration processes that consume HZ_SELECT_DATA_SOURCES to resolve which external sources to call.

Because the documented relationship set is limited, the foreign key to HZ_ENTITY_ATTRIBUTES should be treated as the authoritative join path, with the remaining objects inferred from the TCA third-party data integration feature area.