Search Results edi_payment_method




Overview
Explore in AI Chat

Overview

HZ_PARTY_CONTACT_POINTS_V is an APPS-owned database view in Oracle E-Business Suite, classified under the Receivables (AR) product family. It exposes contact point information — telephone numbers, email addresses, URLs, telex numbers, and related communication attributes — associated with parties and their contacts. In the Oracle Trading Community Architecture (TCA) data model, contact points represent the individual communication mechanisms by which a party, party site, or contact can be reached. The view presents this data in a denormalized, report-friendly format by joining the contact point records in HZ_CONTACT_POINTS with the party identifier held in HZ_PARTIES, surfacing PARTY_NUMBER alongside the full contact point attribute set.

The view is commonly referenced by Receivables reporting, customer master extracts, collections workflows, and integration interfaces that must resolve a party's preferred means of communication. Because it is a view rather than a table, it carries no independent storage and is always executed against its underlying base objects at query time.

Underlying Base Objects

The documented metadata for ETRM 12.2.2 identifies two referenced base objects: HZ_CONTACT_POINTS (SYNONYM) and HZ_PARTIES (SYNONYM). The view text confirms this relationship through a join between alias A (HZ_CONTACT_POINTS) and alias C (HZ_PARTIES). Every column in the SELECT list other than C.PARTY_NUMBER is drawn from the contact points table, while PARTY_NUMBER is sourced from the parties table. This design allows consumers to retrieve communication details keyed by the human-readable party number rather than the internal PARTY_ID, simplifying ad hoc reporting and external integration payloads. Because synonyms are used, the view resolves to the TCA base tables through the APPS schema, consistent with standard EBS object layering.

Key Columns

Common Use Cases and Queries

The view supports customer contact verification, collections calling lists, e-invoicing/EDI setup validation, and data migration extracts. A typical query retrieving primary email addresses for a list of parties is shown below.

SELECT party_number, contact_point_id, email_address, email_format
FROM hz_party_contact_points_v
WHERE contact_point_type = 'EMAIL'
AND primary_flag = 'Y'
AND status = 'A';

A collections-oriented query returning phone details for outbound dialing follows.

SELECT party_number, phone_country_code, phone_area_code, phone_number, phone_extension,
       phone_preferred_order, best_time_to_contact_start, best_time_to_contact_end
FROM hz_party_contact_points_v
WHERE contact_point_type = 'PHONE'
AND do_not_use_flag = 'N'
AND status = 'A'
ORDER BY party_number, phone_preferred_order;

For EDI trading partner analysis, the EDI_TRANSACTION_HANDLING and EDI_ECE_TP_LOCATION_CODE columns allow filtering of parties configured for electronic document exchange. Analysts frequently restrict output by STATUS and PRIMARY_FLAG to avoid duplicating parties that hold multiple historical or secondary contact points. Because the view is not indexed in its own right, performance depends on the indexes defined on HZ_CONTACT_POINTS and HZ_PARTIES; predicates on CONTACT_POINT_ID, PARTY_NUMBER, and CONTACT_POINT_TYPE are therefore recommended.