Results for “optimize_indexes”

8 results




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

Overview

HZ_DQM_SYNC is a public PL/SQL package in the Oracle E-Business Suite (EBS) applications schema (APPS) that supports the Data Quality Management (DQM) synchronization framework underlying the Trading Community Architecture (TCA) and Oracle Customers Online. Its central purpose is to keep the TCA "shadow" or denormalized entities in step with their master records inside the HZ_PARTIES model. The package provides procedures that propagate inserts and updates performed on core TCA entities—parties, organizations, persons, party sites, contacts, contact points, locations, relationships, and customer accounts—into the corresponding synchronization and staging interface tables.

In addition to incremental single-record synchronization, HZ_DQM_SYNC supports bulk staging for party merges and party site merges, index optimization, work-unit-driven concurrent processing, and real-time synchronization. The package is authored with AUTHID CURRENT_USER. The embedded header ($Header: ARHDQSNS.pls 120.7 2006/01/19) places the source in the AR/Receivables module family, consistent with TCA's historical roots in Oracle Receivables.

Key Procedures and Functions

The documented interface includes the following procedures, each described by purpose only (parameter lists are not reproduced):

Tables Accessed

Documented table references resolve through APPS synonyms. Core TCA tables read include HZ_PARTIES, HZ_PARTY_SITES, HZ_CONTACT_POINTS, HZ_ORG_CONTACTS, HZ_RELATIONSHIPS, and HZ_CUST_ACCOUNTS. The synchronization and working storage tables written include HZ_DQM_SYNC_INTERFACE, HZ_DQM_SYNC_INTERFACE_S, HZ_DQM_SH_SYNC_INTERFACE, HZ_DQM_SH_SYNC_INTERFACE_S, HZ_DQM_STAGE_LOG, and the global temporary structure HZ_DQM_SYNC_GT. Supporting references include FND_CONCURRENT_REQUESTS (concurrent program context), WF_EVENT_T (Workflow business events), and AD_CTX_DDL (AD context/index DDL operations).

Usage Notes

HZ_DQM_SYNC is invoked indirectly rather than by end users. TCA forms (Customers, Suppliers, Parties) and the TCA APIs trigger the single-record SYNC_* procedures after commit. Merge operations call the STAGE_*_MERGE procedures. Concurrent programs drive SYNC_WORK_UNIT, SYNC_WORK_UNIT_IMP, SYNC_INDEX_CONC, and the batch-mode paths, with progress and errors recorded in HZ_DQM_STAGE_LOG. Workflow events surfaced through WF_EVENT_T support real-time propagation. The package is referenced by 16 other packages, so customizations should call it only through documented entry points and should not modify it in place; patching or cloning it risks breaking the DQM chain across Oracle Customers Online, TCA, and downstream Receivables integrations.