Search Results hz_party_interface_errors_n1




Overview
Explore in AI Chat

Overview

The AR.HZ_PARTY_INTERFACE_ERRORS table is a staging and diagnostics object within the Oracle E-Business Suite Receivables (AR) schema that supports the party import and mapping process. It captures error messages generated while data from the HZ_PARTY_INTERFACE staging table is mapped and validated into the operational HZ (Trading Community Architecture / TCA) tables such as HZ_PARTIES, HZ_PARTY_SITES, and their related child entities. Because party imports move through the Party Interface, records that fail validation, duplicate checking, or referential integrity rules are surfaced here for investigation and correction rather than being silently discarded.

The object is documented as VALID in ETRM 12.1.1 / 12.2.2 metadata, owned by the AR schema, and physically stored in the APPS_TS_INTERFACE tablespace with a PCT Free of 10. Based on a heuristic mined from its foreign key structure, the table is classified as a standalone model — meaning it behaves more like an independent error registries than a classic hub, link, or satellite in a Data Vault design. This classification is a modeling suggestion; the table may be incorporated as a satellite of the party interface hub where a Data Vault layer is used, given its dependency on HZ_PARTY_INTERFACE via PARTY_INTERFACE_ID.

Key Information Stored

The table includes eight documented columns. The most significant are:

  • INTERFACE_ERROR_ID (NUMBER 15) — The surrogate primary key and the business-key candidate, enforced by the unique index HZ_PARTY_INTERFACE_ERRORS_U1. It uniquely identifies each error record.
  • PARTY_INTERFACE_ID (NUMBER 15) — The foreign key pointing to the HZ_PARTY_INTERFACE staging row that produced the error. This links each error back to the specific inbound party record.
  • MESSAGE_TEXT (VARCHAR2 2000) — The actual error message text describing the failure encountered during mapping, validation, or loading.
  • CREATED_BY (NUMBER 15) — Standard WHO column identifying the user who created the row.
  • CREATION_DATE (DATE) — Timestamp of row creation.
  • LAST_UPDATED_BY (NUMBER 15) — User who last modified the row.
  • LAST_UPDATE_DATE (DATE) — Timestamp of the last update.
  • LAST_UPDATE_LOGIN (NUMBER 15) — Operating system login associated with the last update (FK to FND_LOGINS.LOGIN_ID).

A nonunique index, HZ_PARTY_INTERFACE_ERRORS_N1, exists on PARTY_INTERFACE_ID to support lookups by staging record.

Common Use Cases and Queries

The primary use case is troubleshooting failed party imports. Support and implementation teams query this table after a concurrent request or interface run reports errors. A typical diagnostic query lists errors for a given staging record:

  • SELECT e.INTERFACE_ERROR_ID, e.PARTY_INTERFACE_ID, e.MESSAGE_TEXT, e.CREATION_DATE FROM AR.HZ_PARTY_INTERFACE_ERRORS e WHERE e.PARTY_INTERFACE_ID = :party_interface_id;
  • Aggregated error reporting to identify the most frequent failure messages across a batch: SELECT e.MESSAGE_TEXT, COUNT(*) FROM AR.HZ_PARTY_INTERFACE_ERRORS e GROUP BY e.MESSAGE_TEXT ORDER BY 2 DESC;
  • Joining to HZ_PARTY_INTERFACE on PARTY_INTERFACE_ID to retrieve the original staging payload alongside the error.
  • Reprocessing logic that identifies records with errors, corrects source data, and re-runs the import.

These queries support reconciliation, audit trails, and SLA tracking for TCA party data loads.

Related Objects

The table is referenced by the APPS synonym HZ_PARTY_INTERFACE_ERRORS and depends on the HZ_PARTY_INTERFACE staging table through the PARTY_INTERFACE_ID foreign key. The most significant related objects include:

  • AR.HZ_PARTY_INTERFACE — the staging table whose rows generate the errors (join on PARTY_INTERFACE_ID).
  • HZ_PARTIES — the target master party table populated during the import.
  • HZ_PARTY_SITES — receiving party site data from the interface.
  • HZ_LOCATIONS — address data validated during the load.
  • HZ_CONTACT_POINTS — contact data mapped during import.
  • FND_USER — joined via CREATED_BY and LAST_UPDATED_BY for user attribution.
  • FND_LOGINS — joined via LAST_UPDATE_LOGIN.

These relationships make AR.HZ_PARTY_INTERFACE_ERRORS an essential audit and remediation artifact for TCA party import operations.