Search Results hz_dqm_stage_log




Overview
Explore in AI Chat

Overview

HZ_DQM_STAGE_LOG is a logging table owned by the AR (Receivables) schema in Oracle E-Business Suite. Its documented purpose is to record the phases that the DQM (Data Quality Management) Staging Program passes through during execution, providing a persistent audit trail of parallel worker activity and step-level progress. Because the DQM Staging Program typically runs in a multi-threaded fashion, the table allows administrators and DBAs to monitor progression, diagnose hangs or failures, and confirm that every worker completed each phase.

The table is classified as VALID and is documented in both ETRM 12.1.1 and 12.2.2 schemas, with a documented physical schema of 13 columns in 12.2.2. Its heuristic Data Vault classification is standalone; from a modeling perspective this suggests it is best treated as a standalone logging/audit construct rather than being decomposed into a hub, link, or satellite pattern. The absence of dependent foreign keys reinforces that it is a self-contained operational log keyed by its composite primary key.

Key Information Stored

The composite primary key HZ_DQM_STAGE_LOG_PK is composed of three columns: OPERATION, WORKER_NUMBER, and STEP. Together these identify a unique phase record for a given worker within a given DQM operation.

  • OPERATION — Business key component; identifies the DQM operation or run being logged.
  • WORKER_NUMBER — Business key component; identifies the specific staging worker thread executing the phase.
  • STEP — Business key component; the named phase or step the worker is executing.
  • NUMBER_OF_WORKERS — Total worker threads participating in the operation.
  • START_FLAG — Indicates whether the step has started.
  • START_TIME — Timestamp when the step began.
  • END_FLAG — Indicates whether the step has ended.
  • END_TIME — Timestamp when the step completed.
  • LAST_UPDATE_DATE — Standard EBS audit column; last modification timestamp.
  • CREATION_DATE — Standard EBS audit column; row creation timestamp.
  • CREATED_BY — Standard EBS audit column; user or process that created the row.
  • LAST_UPDATED_BY — Standard EBS audit column; last user or process to update the row.
  • LAST_UPDATE_LOGIN — Standard EBS audit column; login associated with the last update.

No alternate unique index columns are documented beyond the composite primary key, so OPERATION, WORKER_NUMBER, and STEP serve as both the surrogate-key components and the business-key candidates.

Common Use Cases and Queries

Typical uses include monitoring a DQM staging run, identifying stalled workers, and measuring elapsed time per step. A simple progress query lists each operation and step with start and end timestamps:

  • SELECT OPERATION, WORKER_NUMBER, STEP, START_TIME, END_TIME FROM HZ_DQM_STAGE_LOG WHERE OPERATION = :op ORDER BY STEP, WORKER_NUMBER;
  • SELECT * FROM HZ_DQM_STAGE_LOG WHERE OPERATION = :op AND END_FLAG = 'N' — identifies steps not yet finished (potential hangs).
  • SELECT STEP, (END_TIME - START_TIME) FROM HZ_DQM_STAGE_LOG WHERE OPERATION = :op — reports duration per phase.
  • SELECT OPERATION, COUNT(DISTINCT WORKER_NUMBER) FROM HZ_DQM_STAGE_LOG GROUP BY OPERATION — confirms worker counts against NUMBER_OF_WORKERS.
  • Reporting on the latest run uses LAST_UPDATE_DATE ordering to isolate current activity.

Related Objects

The table is documented as standalone, with no FK-based dependents. In practice it is referenced alongside the following related AR/DQM objects:

  • HZ_DQM_STAGE_LOG itself — queried directly by monitoring scripts.
  • DQM staging program — the concurrent program that inserts and updates rows keyed by OPERATION, WORKER_NUMBER, and STEP.
  • HZ_PARTIES and related HZ staging tables — the target data being staged, though not joined by FK to this log.
  • FND_CONCURRENT_REQUESTS — associated by the concurrent request context for the staging run.
  • Standard EBS audit columns — CREATED_BY/LAST_UPDATED_BY align with FND_USER for attribution.