Search Results hz_imp_errors




Overview
Explore in AI Chat

Overview

HZ_IMP_ERRORS is a TCA (Trading Community Architecture) interface table owned by the AR (Receivables) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to record errors encountered during the TCA import process. When batch import programs such as the Customer Interface, Supplier Interface, or other TCA-based loaders process records, any row that fails validation, violates a uniqueness constraint, or cannot be resolved against existing reference data is written to this table with a diagnostic message rather than being silently discarded. The table therefore serves as the primary error-diagnostic repository for the TCA import framework.

From a Data Vault modeling perspective, the mined FK structure (HZ_IMP_ERRORS.BATCH_ID referencing HZ_IMP_BATCH_SUMMARY) suggests this object is satellite-leaning: it carries descriptive, non-key attributes attached to a parent batch entity rather than acting as a hub of independent business keys or a link between hubs. Analysts modeling the TCA staging layer should treat HZ_IMP_ERRORS as a dependent satellite of the import batch.

Key Information Stored

The table comprises 23 documented columns. The surrogate primary key is ERROR_ID, which uniquely identifies each error record. The principal business-key candidate for joining to the parent entity is BATCH_ID, the foreign key to HZ_IMP_BATCH_SUMMARY.

Common Use Cases and Queries

The most frequent scenario is post-import reconciliation: an administrator runs a TCA import batch, observes that fewer records loaded than were submitted, and queries HZ_IMP_ERRORS filtered by BATCH_ID to identify the rejected rows and their causes.

  • All errors for a batch: SELECT e.error_id, e.message_name, e.token1_name, e.token1_value, e.interface_table_name FROM hz_imp_errors e WHERE e.batch_id = :batch_id ORDER BY e.error_id;
  • Error counts by interface table: aggregate COUNT(*) grouped by INTERFACE_TABLE_NAME joined to BATCH_ID to see which stage failed most often.
  • Concurrent program traceability: join on REQUEST_ID to FND_CONCURRENT_REQUESTS to tie errors back to a specific run.
  • Message resolution: join MESSAGE_NAME to FND_MESSAGES_TL and substitute TOKEN values to render human-readable diagnostics in custom reports.

Related Objects

  • HZ_IMP_BATCH_SUMMARY — parent table; join on HZ_IMP_ERRORS.BATCH_ID = HZ_IMP_BATCH_SUMMARY.BATCH_ID.
  • HZ_IMP_BATCHES / TCA batch control tables — batch-level context.
  • FND_MESSAGES / FND_MESSAGES_TL — resolve MESSAGE_NAME to text.
  • FND_CONCURRENT_REQUESTS — link REQUEST_ID to the originating concurrent program.
  • FND_APPLICATION / FND_CONCURRENT_PROGRAMS — describe PROGRAM_APPLICATION_ID and PROGRAM_ID.
  • HZ_PARTIES / HZ_CUST_ACCOUNTS — the target TCA entities that failed to load.