Search Results hz_party_interface_n2

Overview

HZ_PARTY_INTERFACE is a table in the AR (Receivables) schema of Oracle E-Business Suite, valid across release levels 12.1.1 and 12.2.2. It functions as a staging and integration surface for party (organization or person) information retrieved from an external source. As documented in the ETRM metadata, the only supported external source is Dun & Bradstreet, populated through either the online lookup method or the batch download method. The table's column definitions mirror the data dictionary published by Dun & Bradstreet's Global Data Products, while the column names follow Oracle's internal data model conventions.

Because the table stores externally sourced attributes keyed to a party rather than the party master record itself, the heuristic Data Vault classification is satellite, with PARTY_ID acting as the effective parent hub reference. This is a modeling suggestion only; the physical implementation is a conventional Oracle interface table stored in the APPS_TS_INTERFACE tablespace with PCTFREE 10.

Key Information Stored

The table contains 262 documented columns. The following are the most operationally significant:

• PARTY_INTERFACE_ID — NUMBER(15) surrogate primary key, enforced by unique index HZ_PARTY_INTERFACE_U1. This is the column referenced by the user's search term and is the single-row identity of a party interface record.
• PARTY_ID — NUMBER(15) foreign key to HZ_PARTIES, linking the staged external data to the in-system party. Served by non-unique index HZ_PARTY_INTERFACE_N1.
• GROUP_ID — NUMBER(15), the multi-org / resource group identifier, served by non-unique index HZ_PARTY_INTERFACE_N2.
• DUNS_NUMBER and ENQUIRY_DUNS — the nine-digit D&B entity identifier and the identifier actually used to perform the query (which may be the headquarters DUNS for branch locations).
• PARTY_NAME, KNOWN_AS1–KNOWN_AS5 — primary name and up to five alias names returned by D&B.
• ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — the retrieved physical address block.
• CONTENT_SOURCE_TYPE, STATUS, GDP_NAME — provenance and processing state of the interface row.
• PAYDEX_SCORE, FAILURE_SCORE, CREDIT_SCORE_CLASS — representative D&B credit appetite and risk fields.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_LOG_ID — standard concurrent program lineage columns identifying which request loaded the row.
• ORIG_SYSTEM_REFERENCE — lineage back to the originating external system key.
• Standard WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Primary usage is reviewing D&B profile enrichment before promotion into HZ_PARTIES, diagnosing credit-risk assessments, and auditing interface loads. A typical lookup by primary key:

• SELECT * FROM ar.hz_party_interface WHERE party_interface_id = :p_id;
• Fetch the latest interface row for a given party: SELECT * FROM ar.hz_party_interface WHERE party_id = :p_party_id ORDER BY creation_date DESC;
• Identify failed or unresolvable loads by joining to the error table: SELECT i.party_interface_id, e.* FROM ar.hz_party_interface i, ar.hz_party_interface_errors e WHERE i.party_interface_id = e.party_interface_id;
• Report credit exposure by DUNS: SELECT duns_number, party_name, paydex_score, failure_score FROM ar.hz_party_interface;
• Trace a concurrent load: filter on REQUEST_ID to see all parties retrieved by a single D&B batch program run.

Related Objects

• HZ_PARTY_INTERFACE_ERRORS — the only documented foreign key relationship; its PARTY_INTERFACE_ID column references HZ_PARTY_INTERFACE, capturing rejection reasons for rows that could not be applied.
• HZ_PARTIES — parent party master; HZ_PARTY_INTERFACE.PARTY_ID references it, and the interface exists to enrich or qualify that record.
• HZ_PARTY_SITES / HZ_LOCATIONS — downstream consumers of the address and DUNS attributes once promoted.
• HZ_CUST_ACCOUNTS — customer accounts that benefit from D&B-derived credit and risk attributes.
• D&B Integration Programs — the concurrent programs and PL/SQL packages that populate this table via the online or batch download methods, identified through PROGRAM_ID/PROGRAM_APPLICATION_ID.