Search Results hz_dqm_sync_interface




Overview
Explore in AI Chat

Overview

HZ_DQM_SYNC_INTERFACE is a transactional interface table owned by the AR (Receivables) schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores the list of entities that have been inserted or updated through the Data Quality Management (DQM) API. DQM is the framework used by Oracle's Trading Community Architecture (TCA) and by Customer Data Management to detect duplicates, apply survivorship rules, and merge party records. When the DQM API performs one of these operations, it posts a corresponding row into this interface table so that downstream or dependent entities can be re-synchronized or re-processed.

In Data Vault modeling terms, the heuristic classification for this table is link. It does not represent an independent business entity; rather, it records associations between a party and its related child records (organization contacts and party sites), together with an operation type and sync status. This makes it structurally analogous to a link table capturing relationships and events across the TCA party model, though it also carries descriptive attributes that behave satellite-like.

Key Information Stored

The table is documented with 16 columns in the 12.2.2 physical schema. The most operationally significant columns are:

  • SYNC_INTERFACE_NUM – The unique numeric identifier for each interface row, functioning as the surrogate primary key.
  • PARTY_ID – Identifies the TCA party (person or organization) that was affected by the DQM operation. This is the primary business-key candidate and the most common query filter.
  • RECORD_ID – Identifies the specific child record within the entity that was updated.
  • ENTITY – Names the TCA entity type affected (for example, a party site or organization contact), directing the consumer to the correct downstream table.
  • OPERATION – Specifies the DQM action performed (such as insert, update, or merge).
  • ORG_CONTACT_ID – Foreign key to HZ_ORG_CONTACTS; populated when the synced entity is an organization contact.
  • PARTY_SITE_ID – Foreign key to HZ_PARTY_SITES; populated when the synced entity is a party site.
  • STAGED_FLAG – Indicates whether the row has been picked up and processed by the synchronization program.
  • REALTIME_SYNC_FLAG – Indicates whether the row requires real-time synchronization versus batch processing.
  • IMPORT_OSR – Flags rows originating from bulk import or origin source reference processing.
  • ERROR_DATA – Captures error information when the synchronization of a row fails.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS Who columns providing audit history.

The principal business keys are PARTY_ID combined with ENTITY and RECORD_ID; the surrogate key is SYNC_INTERFACE_NUM.

Common Use Cases and Queries

This table is typically queried to diagnose sync failures, to monitor DQM activity, and to drive custom synchronization programs where standard processing must be extended.

  • Pending synchronization backlog: SELECT * FROM hz_dqm_sync_interface WHERE staged_flag = 'N';
  • Real-time sync monitoring: SELECT party_id, entity, operation, creation_date FROM hz_dqm_sync_interface WHERE realtime_sync_flag = 'Y' ORDER BY creation_date DESC;
  • Error investigation: SELECT sync_interface_num, party_id, error_data FROM hz_dqm_sync_interface WHERE error_data IS NOT NULL;
  • History for a specific party: filtering on party_id to trace all DQM-driven changes affecting that customer, supplier, or contact.

Reporting use cases include auditing the volume and type of DQM operations over time and validating that downstream consumers have processed every staged row.

Related Objects

The table participates in the TCA party model through documented foreign key relationships and sibling entities:

  • HZ_ORG_CONTACTS – joined via HZ_DQM_SYNC_INTERFACE.ORG_CONTACT_ID → HZ_ORG_CONTACTS; provides contact details for synced organization contacts.
  • HZ_PARTY_SITES – joined via HZ_DQM_SYNC_INTERFACE.PARTY_SITE_ID → HZ_PARTY_SITES; provides site details for synced party sites.
  • HZ_PARTIES – the parent party record referenced by PARTY_ID; the central TCA entity.
  • HZ_DQM_SYNC_INTERFACE consumers include the DQM/party synchronization concurrent programs that read the STAGED_FLAG and REALTIME_SYNC_FLAG columns.
  • HZ_LOCATIONS and HZ_CONTACT_POINTS – downstream TCA tables whose records are frequently affected when the affected entities are contacts or sites.