Search Results hz_party_interface_pk

Overview

HZ_PARTY_INTERFACE is an Oracle Receivables (AR) interface table that stores party information retrieved from an external source. It functions as a staging and import mechanism within the Oracle E-Business Suite Trading Community Architecture, allowing third-party data — such as Dun & Bradstreet business credit and firmographic information — to be loaded into the EBS environment before it is validated and consumed by the party model. The table is owned by the AR schema and is documented with 262 columns in ETRM 12.2.2, reflecting the breadth of external party data that the interface is designed to accept.

In heuristic Data Vault terms, HZ_PARTY_INTERFACE is best modeled as a staging or satellite structure. Its single-column primary key (PARTY_INTERFACE_ID) and its role as a landing zone for externally sourced attributes suggest a satellite attached to a party hub (HZ_PARTIES), rather than a true business hub or link. It carries descriptive and potentially volatile attributes keyed by a surrogate identifier, which is characteristic of satellite modeling.

Key Information Stored

The primary key of the table is PARTY_INTERFACE_ID, defined by the constraint HZ_PARTY_INTERFACE_PK and enforced through the unique index HZ_PARTY_INTERFACE_U1. This surrogate key uniquely identifies each interface row and is the join column to the error table (HZ_PARTY_INTERFACE_ERRORS). No separate business-key unique index is documented, so the surrogate identifier is the sole documented unique key.

Among the 262 columns, the following are the most significant for identification, matching, and credit assessment:

• PARTY_ID — links the interface row to an existing party in HZ_PARTIES once matched or created.
• PARTY_NAME, KNOWN_AS1 through KNOWN_AS5 — the legal name and alternate names used for party matching and de-duplication.
• DUNS_NUMBER, ENQUIRY_DUNS — the external D&B identifiers used to correlate the record with the source data provider.
• ADDRESS1 through CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — address fields for geographic validation.
• TELEPHONE_NUMBER, FAX_NUMBER, PHONE_COUNTRY_CODE — contact attributes for the party.
• PAYDEX_SCORE, PAYDEX_NORM, PAYDEX_THREE_MONTHS_AGO — credit payment behaviour indicators from the external source.
• CREDIT_SCORE, FAILURE_SCORE, GLOBAL_FAILURE_SCORE — risk scores derived from the external provider.
• CONTENT_SOURCE_TYPE, STATUS — describes the origin of the record and its processing status.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.
• REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrency context identifying the import request and program that populated the row.

Common Use Cases and Queries

The table supports bulk import and enrichment of party data. A typical query is to inspect staged rows by status before attempting a validation run:

• SELECT party_interface_id, party_name, duns_number, status FROM hz_party_interface WHERE status = 'NEW';
• SELECT pi.party_interface_id, pi.party_name, e.error_message FROM hz_party_interface pi JOIN hz_party_interface_errors e ON pi.party_interface_id = e.party_interface_id; — joins the interface to its error table to identify rejected records.
• SELECT party_name, paydex_score, credit_score FROM hz_party_interface ORDER BY credit_score DESC; — credit assessment reporting.
• SELECT COUNT(*), content_source_type FROM hz_party_interface GROUP BY content_source_type; — sourcing volume analysis.

Reporting use cases include identifying parties with high risk scores, auditing external data loads by request ID, and tracking which records have been successfully promoted into the base party tables.

Related Objects

The most significant related objects, based on documented relationships, include:

• HZ_PARTY_INTERFACE_ERRORS — the only documented foreign-key relationship; its PARTY_INTERFACE_ID references HZ_PARTY_INTERFACE, capturing validation failures for each staged row.
• HZ_PARTIES — the base party table; PARTY_ID on the interface matches the promoted party record.
• HZ_ORGANIZATION_PROFILES / HZ_PERSON_PROFILES — downstream enriched party profiles populated from validated interface data.
• HZ_PARTY_SITES and HZ_LOCATIONS — receive address attributes during promotion.
• HZ_CONTACT_POINTS — receives telephone and fax attributes.
• HZ_PARTY_IMPORT / TCA party import APIs — consume and validate interface rows.

Together these objects form the inbound pipeline through which external party intelligence is brought into the EBS trading community model.