Results for “best_time_to_contact_end”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HZ_CONTACT_POINTS is the TCA (Trading Community Architecture) hub table that stores the electronic methods of communicating with parties and party sites. It resides in the AR schema and is documented as VALID under the Receivables product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table captures structured communication channels — phone numbers, e-mail addresses, URLs, telex numbers, and EDI/EFT routing attributes — that describe how an organization reaches a customer, supplier, contact, prospect, or physical location.

The table maintains a polymorphic ownership model. Rather than holding a single dedicated foreign key to one parent, it uses an OWNER_TABLE_NAME / OWNER_TABLE_ID pair to point back to HZ_PARTIES or HZ_PARTY_SITES, with TIMEZONE_ID resolving to HZ_TIMEZONES for time-zone normalization of phone contacts. Each row is uniquely identified by the primary key HZ_CONTACT_POINTS_PK on CONTACT_POINT_ID, and the unique index HZ_CONTACT_POINTS_U1 on the same column confirms it as the business-key candidate.

Following the heuristic Data Vault classification supplied with the metadata, HZ_CONTACT_POINTS is hub-leaning: it holds a durable, uniquely identifiable business key (CONTACT_POINT_ID) and is referenced by a broad fan of downstream transactional and CRM tables. In a Data Vault model it would typically be treated as a hub, with links attaching phone/email usage in calls, sales leads, service requests, order headers, and marketing lists.

Key Information Stored

The table contains 105 documented columns, but the majority of analytical and integration value concentrates in a focused subset:

• CONTACT_POINT_ID — the surrogate primary key and the unique business-key candidate used in virtually every FK reference.
• CONTACT_POINT_TYPE — classifies the method (e.g. PHONE, EMAIL, URL, TELEX, EDI).
• OWNER_TABLE_NAME / OWNER_TABLE_ID — polymorphic reference to HZ_PARTIES or HZ_PARTY_SITES, defining which entity owns the contact point.
• PRIMARY_FLAG and PRIMARY_BY_PURPOSE — flags the preferred contact point for the owning party or purpose.
• EMAIL_ADDRESS and EMAIL_FORMAT — e-mail channel content and its format.
• PHONE_NUMBER, PHONE_AREA_CODE, PHONE_COUNTRY_CODE, PHONE_EXTENSION, RAW_PHONE_NUMBER, TRANSPOSED_PHONE_NUMBER — structured and searchable phone representations.
• TELEPHONE_TYPE, PHONE_LINE_TYPE, PHONE_PREFERRED_ORDER, PHONE_TOUCH_TONE_TYPE_FLAG — phone classification and preference attributes.
• TIME_ZONE and TIMEZONE_ID — local time-zone context for the contact.
• URL and WEB_TYPE — web address and its category.
• STATUS and ORIG_SYSTEM_REFERENCE — lifecycle status and the source system reference for imported contact points.
• DO_NOT_USE_FLAG and DO_NOT_USE_REASON — suppression controls that reporting and outreach processes must honor.
• CONTACT_POINT_PURPOSE — the business intent (e.g. billing, shipping, general).
• EDI_* columns (EDI_ID_NUMBER, EDI_TRANSACTION_HANDLING, EDI_TP_HEADER_ID, etc.) — trading-partner EDI configuration.
• EFT_* columns (EFT_USER_NUMBER, EFT_SWIFT_CODE, EFT_TRANSMISSION_PROGRAM_ID, etc.) — electronic funds transfer routing data.
• OBJECT_VERSION_NUMBER and the WHO columns (CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY) — concurrency control and audit trail.

Common Use Cases and Queries

Typical usage centers on retrieving the correct contact channel for a party or site — for customer communications, order-to-cash processing, and CRM/service activities. A common reporting pattern filters to active, primary contact points for a specific party:

• Phone lookup for a party: join HZ_CONTACT_POINTS to HZ_PARTIES on OWNER_TABLE_ID = PARTY_ID, filtering OWNER_TABLE_NAME = 'HZ_PARTIES', STATUS = 'A', and CONTACT_POINT_TYPE = 'PHONE'.
• E-mail extraction for campaigns: select EMAIL_ADDRESS where CONTACT_POINT_TYPE = 'EMAIL' and DO_NOT_USE_FLAG is null or 'N'.
• Site-level contact resolution: join to HZ_PARTY_SITES where OWNER_TABLE_NAME = 'HZ_PARTY_SITES' to obtain the location-specific phone or address channel.
• Data quality and de-duplication: query TRANSPOSED_PHONE_NUMBER and RAW_PHONE_NUMBER to identify duplicate phone numbers across owners.
• Service request and call tracing: join CONTACT_POINT_ID to CS_INCIDENTS_ALL_B.CUSTOMER_PHONE_ID, AR_CUSTOMER_CALLS_ALL.PHONE_ID, or JTF_TASK_PHONES.PHONE_ID to reconstruct which number was used on an interaction.
• EDI/EFT onboarding: select the EDI_* and EFT_* columns for trading partners being enabled for electronic transactions.

Because the table is a central TCA hub, queries frequently drive from HZ_PARTIES or HZ_PARTY_SITES outward and join on OWNER_TABLE_ID, always constraining OWNER_TABLE_NAME to disambiguate the polymorphic parent.

Related Objects

The reference topology of HZ_CONTACT_POINTS is broad, reflecting its role as a shared contact hub. The most significant related objects include:

• HZ_PARTIES — primary owner parent via OWNER_TABLE_ID (where OWNER_TABLE_NAME = 'HZ_PARTIES').
• HZ_PARTY_SITES — location-level owner parent via OWNER_TABLE_ID (where OWNER_TABLE_NAME = 'HZ_PARTY_SITES').
• HZ_TIMEZONES — resolves TIMEZONE_ID for phone time-zone context.
• AR_CUSTOMER_CALLS_ALL — references PHONE_ID and FAX_ID, linking calls to the numbers used.
• AR_CUSTOMER_CALL_TOPICS_ALL — references PHONE_ID for topic-level interaction tracking.
• CS_INCIDENTS_ALL_B — references CUSTOMER_PHONE_ID and CUSTOMER_EMAIL_ID for service incidents.
• CS_HZ_SR_CONTACT_POINTS — join through CONTACT_POINT_ID for service-request contact associations.
• AS_SALES_LEADS, AS_LEAD_CONTACTS_ALL, AS_SALES_LEAD_CONTACTS — reference phone IDs for lead and prospect channels.
• OE_HEADERS_IFACE_ALL, OE_HEADER_ACKS, OE_ORDER_HEADER_HISTORY — reference SOLD_TO_PHONE_ID across the order lifecycle.
• AMS_LIST_ENTRIES, AMS_IMP_SOURCE_LINES, JTF_TASK_PHONES, IBE_SH_QUOTE_ACCESS — marketing and task-level consumers of CONTACT_POINT_ID or PHONE_ID.

These relationships establish HZ_CONTACT_POINTS as the canonical reference for communication channels across Receivables, Service, Order Management, Sales, and Marketing, which is why it must be treated as a governed core entity in any integration or reporting design.