Search Results cont_point_type_meaning




Overview
Explore in AI Chat

Overview

The view APPS.CS_SR_HZ_CONT_PTS_EMAILS_V is a reporting and integration object in Oracle E-Business Suite that exposes e-mail contact points belonging to parties (customers, prospects, and other party records) registered in the Trading Community Architecture (TCA) model. Its practical purpose is to present a denormalized, human-readable representation of TCA e-mail contact points by joining the base contact point records to the AR_LOOKUPS reference table so that the lookup meaning — rather than the raw lookup code — is available directly to the caller.

This design reflects a common EBS convention in which reference data stored as coded values is resolved through FND_LOOKUPS or, as in this case, AR_LOOKUPS. The view is owned by APPS and is typically consumed by Oracle Service (CS) and Service Request (SR) functionality, report definitions, and outbound integrations that must retrieve a party's primary or secondary e-mail address without re-implementing the lookup translation logic themselves. The presence of PRIMARY_FLAG and STATUS columns makes it suitable for locating the active, primary e-mail address for a contact. The column cont_point_type_meaning — the term the user searched for — is precisely the resolved meaning of the contact point type code, which is why the view is often located through that column name.

Underlying Base Objects

The ETRM documentation for this object identifies two referenced base objects: HZ_CONTACT_POINTS (documented as a synonym) and AR_LOOKUPS (documented as a view). The view is defined over the TCA contact point entity, which stores all points of contact — e-mail, phone, fax, URL, and others — against an owning entity. The filter cp.owner_table_name = 'HZ_PARTIES' restricts the result set to contact points owned by party records, excluding contact points attached to other owner tables such as organizations or locations.

A second filter, cp.contact_point_type = 'EMAIL', restricts the rows to e-mail contact points only, so the view is effectively a type-specific slice of the much broader HZ_CONTACT_POINTS table. The join to AR_LOOKUPS is an outer join on both LOOKUP_CODE and LOOKUP_TYPE = 'COMMUNICATION_TYPE', allowing rows to survive even where no matching lookup is defined. This use of outer-join syntax also confirms the view follows pre-ANSI Oracle join conventions that predate the migration to the 12.2.x data model, consistent with its continued availability across 12.1.1 and 12.2.2.

Key Columns

  • EMAIL — the e-mail address, sourced from HZ_CONTACT_POINTS.EMAIL_ADDRESS. This is the principal payload column for integrations.
  • CONT_POINT_TYPE_MEANING — the resolved meaning of the communication type lookup. Because the view filters to EMAIL records, this typically resolves to the meaning associated with the EMAIL lookup code in the COMMUNICATION_TYPE lookup type.
  • OWNER_TABLE_ID — the identifier of the owning party record, which corresponds to a HZ_PARTIES.PARTY_ID value. This is the key used to join back to party data.
  • CONTACT_POINT_ID — the unique identifier of the contact point row, useful for updates or de-duplication.
  • TIMEZONE_ID — the time zone associated with the contact point, where captured.
  • CONTACT_POINT_TYPE — the raw type code, always EMAIL in this view.
  • PRIMARY_FLAG — indicates whether the contact point is the party's primary e-mail address; used to select a single address per party.
  • STATUS — the status of the contact point, used to exclude inactive or obsolete rows.

Common Use Cases and Queries

Typical uses include retrieving the primary e-mail address for a party during service request processing, populating notification recipients in workflow or concurrent programs, and driving outbound e-mail integrations keyed on party identifier. Because CONT_POINT_TYPE_MEANING is exposed, the view is convenient for reports that must display a descriptive type rather than the EMAIL code.

A query to obtain the primary active e-mail for a party follows:

  • SELECT email, cont_point_type_meaning, contact_point_id
  • FROM apps.cs_sr_hz_cont_pts_emails_v
  • WHERE owner_table_id = :party_id
  • AND primary_flag = 'Y'
  • AND status = 'A';

To enumerate all e-mail contact points for a party, omit the primary_flag predicate. To join to party details, relate OWNER_TABLE_ID to HZ_PARTIES.PARTY_ID. Because the view carries no organization or location context, callers requiring that context must query HZ_CONTACT_POINTS directly with the appropriate OWNER_TABLE_NAME.